All pages
Powered by GitBook
1 of 4

Loading...

Loading...

Loading...

Loading...

Recovery

Process overview
Granular recovery
Disaster recovery
Cover
Cover
Cover

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

Due to Atlassian API changes that took effect on March 30, 2026, the disaster recovery backup and restore functionalities are no longer available. To ensure continued protection of your Jira data, please switch to the granular backup plan. Data previously protected with disaster recovery backups can still be restored using the disaster recovery or granular recovery option.

When restoring Jira automation rules associated with an assets schema (i.e., during a granular restore to another organization or a disaster recovery 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.

1

Get into the restore view using the following method:

  1. 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.

2

Next, select the disaster recovery backup plan from which you want to restore data.

3

Choose the backup version from all the backups that have already been performed — select the desired date and click Restore > Disaster recovery.

4

Select the available destination for the restore process from the list.

  1. 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.

  1. If the restoration destination is Jira, you can change the default worker in the next aside. In

5

After defining all parameters, click the Restore button to begin the recovery process. You can monitor its status in the Tasks tab.

Restore settings
, you can also choose whether you want to restore assets and users.

If you select a device as the restoration destination, Xopero ONE will recover all protected Jira data included in the selected backup plan as separate, compressed (zipped) folders.

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.

Granular recovery

In this article, you will learn how to recover your Jira organization data using the granular restore option.

Jira granular recovery enables you to restore selected Jira items such as work items, attachments, or configuration elements, giving you precise control over what is brought back without affecting the rest of your space data.


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 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.

1

Get into the restore view using the following method:

  1. 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.

2

Next, select the backup plan from which you want to restore data.

3

Choose the backup version from all the backups that have already been performed — select the desired date and click the Restore button.

4

Select the available destination for the restore process from the list.

5

In the next aside, choose the resources you want to include (restore option) and click Next. Then, select data to restore and click Proceed.

6

In the next aside, specify the restoration path and directory (where applicable). In Default worker section, choose the agent that will be responsible for performing the restoration.

7

In Restore settings you can set a custom name for the space that will be created during the restore process. You can also decide if you want to restore automation rules, their owners, etc. Visible options will vary depending on the restoration type.

8

When restoring spaces, you can preserve the original work item keys by enabling the Restore required global resources option and then enabling Restore original work item keys to a custom field.

9

After defining all parameters, click the Restore button to begin the recovery process. You can monitor its status in the Tasks tab.

If you are restoring data from a disaster recovery backup copy, you must also select the restoration method.

Please note that when you recover Jira data to a device, the amount of data available for recovery will be limited—certain Jira components and metadata are only supported when restoring directly to a Jira instance.

Original work item keys are mapped to the GitProtect_Original Key custom field.

Process overview

This article describes Jira recovery process in Xopero ONE.

In Xopero ONE, you can restore your Jira data using granular recovery.


Recovery methods

Granular recovery

Jira granular recovery in Xopero ONE lets you restore selected Jira data without performing a full environment rollback. Instead of recovering everything, you can choose specific spaces, work items, attachments, and other items that were deleted or changed. This makes the recovery process faster, reduces process disruption, and avoids overwriting healthy data.

Granular recovery is ideal when only a small portion of information needs to be restored — it provides more control and precision than a full disaster recovery. It’s especially useful when:

  1. Space-level recovery:

A space-level restore in Xopero ONE is a type of recovery that focuses on a single Jira space. It allows you to restore all elements within that specific space—such as work items, boards, and configurations—without affecting other spaces in your Jira instance. It's useful when only part of your Jira environment is corrupted, deleted, or needs to be rolled back, letting you recover just the affected area while leaving the rest of the organization intact.

Jira disaster recovery feature is a full environment restore that brings Jira instance back to a functional state after a major incident, such as data corruption, ransomware, or widespread loss. Instead of restoring individual items, disaster recovery reinstates all protected data and configuration from the selected backup, returning the environment to its previous state.


Xopero ONE allows you to restore your Jira organization in two ways:

  1. To a local device — restore the Jira organization to a selected device with the Xopero ONE agent (worker) installed. This option lets you keep Jira backups locally (e.g., for archiving) or manually import them into your Jira organization.

  2. To Jira organization — automatically import the Jira backups to the original, or new Jira organization.

Granular recovery types include:

Disaster recovery

Due to Atlassian API changes that took effect on March 30, 2026, the disaster recovery backup and restore functionalities are no longer available. To ensure continued protection of your Jira data, please switch to the granular backup plan. Data previously protected with disaster recovery backups can still be restored using the disaster recovery or granular recovery option.

Restore destination

The maximum number of restore operations allowed within a single Jira instance is 100. Any attempt to exceed this limit cannot be processed due to Jira API constraints. This limitation is not documented in Atlassian’s official resources but was identified during practical restore testing and operational observations on our side.