Prior to version 3.0, Structure used to store data separately from JIRA data and it was not included in the general System Backup. That called for a separate backup strategy. With version 3.0 and later, this matter is simplified.
Structure data is backed up along with JIRA data when you make full system backup.
However, Structure can back up and restore its data separately. This allows you to roll back Structure-related changes without affecting other JIRA data and generally safeguards your structures.
The following backup strategy is sufficient in most cases.
Option 1. Automatic XML Backup + Export Directory Backup
This strategy involves two processes:
- Automatic Structure Maintenance lets you automatically create full hot backups of the Structure data once a day. The backups are stored in the
exportdirectory under JIRA home.
- Periodic file-level backup of the
exportdirectory (or the whole JIRA home) to a different storage device increases the safety of the backups. This part should be configured manually by the server administrator.
This is the recommended strategy.
When you install Structure, automatic daily backups are enabled by default. You only need to make sure that backup files that will appear in the
export directory are stored safely.
Option 2. Manual / API-Triggered XML Backup
You can manually back up structure through Structure Backup menu.
If automatic Structure maintenance does not suit you and you have resources to develop your own mini-plugin for backup strategy, you can automatically back up Structure data through the Structure API (use
Restoring from XML Backup
See Restoring Structure from Backup for instructions.
Incremental and Differential Backups
As Structure database is typically not large, full backup is recommended.
Structure XML backup/restore does not support incremental backup, but you can use your operating system tools for incremental or differential backup of the files in