Disaster recovery
In this article, you will learn how to recover your Jira organization using the disaster recovery option.
With Jira disaster recovery you can quickly restore your entire Jira organization after a major failure, keeping your spaces, work items, and configuration data available and consistent.
Recovery process
When restoring Jira automation rules associated with an assets schema (i.e., during a granular restore to another organization or a disaster recovery restore where the target organization already contains assets), a different assets schema may be attached to the restored rule component. This behavior is the same as when rules are manually imported through the Jira UI.
Connections to external services (i.e., Google Drive) are not restored in automation components when restoring data in disaster recovery mode or to another organization.
Get into the restore view using the following method:
Open the Jira tab (DevOps > Jira), then click the Restore button next to the organization whose backup you want to restore.
You can also use the Explore button to restore your data.
Next, select the backup plan from which you want to restore data. Click View available plans and choose one of the disaster recovery plans from the list.
Choose the backup version from all the backups that have already been performed — select the desired date and click the Restore > Disaster recovery.
Select the available destination for the restore process from the list:
If the restoration destination is a device, you must specify the recovery path. If you want to change the default worker responsible for handling the restore, make sure to do it before selecting the backup copy to restore.
If you select a device as the restoration destination, GitProtect will recover all protected Jira data included in the selected backup plan as separate, compressed (zipped) folders.
If the restoration destination is Jira, you can change the default worker in the next aside. In Restore settings, you can also choose whether you want to restore assets and users.
The disaster recovery process replaces all existing data (except users and assets) in the selected Jira instance, and the backup may not include every item stored in that environment.
Jira enforces several limitations. Atlassian limits the number of Jira backup restores per organization to 100. A restore also affects your Jira usage — the process can take some time, and during this period your Jira instance will not be accessible.
You can choose to preserve the original Jira Asset identifiers during a disaster recovery restore.
After defining all parameters, click the Restore button to begin the recovery process. You can monitor its status in the Tasks tab.
Post-recovery actions for GitProtect installed via Atlassian Marketplace
When you restore a backup to the original organization (the source organization from which it was created) using the disaster recovery method, the GitProtect.io for Jira application is removed from your Jira site and must be reinstalled afterward.
To add the GitProtect app to your Jira site again, go to Apps > Explore more apps and search for GitProtect.io for Jira. On the app page in Atlassian Marketplace, click Try it free and follow the on-screen instructions. The process is the same as when you added the app for the first time, except you do not need to provide a personal access token because GitProtect is already integrated with your Jira account.
Adding the app to your Jira site again does not modify the trial period and does not change your current subscription model.
Once the app is reinstalled, you can view your backup statistics and use all GitProtect.io for Jira app features.
Last updated