Backup and restore
Backup
In order to backup Backbone's synchronization data, you have to backup Jira's database and the Backbone directory in Jira's home folder on the file system. This is further explained in this help article. The most important part is to backup Jira's database as this includes all the synchronization information, e.g. the relationships between synchronized issues, configuration data, and more.
If you set up your backups as described in the Jira documentation - backing up database contents as well as backing up the data
directory on the file system - no further action needs to be taken.
Restore
When restoring data as described in Atlassian's knowledge base article about restoring data, all Backbone database content and potentially Backbone data directory content will be restored as well.
However, please consider that restoring this data will restore your Backbone database content to an old state which may break synchronizations with other Jira instances. There are multiple scenarios that can occur here which are described in further detail below.
In all cases we suggest to avoid automatically starting the synchronizations again when restarting Jira. This can help to not run into troubleshooting errors that need to be cleaned up later.
Fixing issues after restore
To get issues back in sync you will need to trigger a resync for all issues in both directions. In most cases it is enough to only resync the changes that have been changed from the latest backup's timestamp until now (instead of resyncing all issues of both projects). This will update your issues and also fix the internal synchronization information and relationships of Backbone in the database. Afterwards you should be able to use Backbone as usual.
Further questions?
Your synchronization scenario is not covered or you have further questions to the information above? Please reach out to our support team or write an email to help@k15t.com and we can provide you some more individual help.