You can migrate a Jira instance with a running Backbone synchronization to another server.
These steps can result in data loss
If you want 1-to-1 help with migrating your Backbone synchronizations, please reach out to the K15t support team.
Please test this method thoroughly on a test system before on your production system.
- Stop all your Backbone synchronizations. This step is important to avoid that Backbone synchronizations are automatically started again as soon as you start your Jira server.
- Perform a 'standard' Jira migration. Backbone stores its data in the Jira database and on the file system of your Jira instance. You can find the data under the path Jira-Home/data/backbone-issue-sync. Please copy all folders and files from Backbone's folder to the new Jira home location of your Jira instance.
- After migration, start Jira and go to the global list of Backbone synchronizations under Administration > Manage add-ons/apps > Synchronizations. Then update the URLs of all Backbone synchronizations.
- Start the synchronizations again.
Good to know
If you perform migrations automatically or copy/clone your Jira instances on a regular basis, you can also use a system property to avoid that Backbone automatically starts all synchronizations after restarting Jira.