Learn how to create a Jira backup plan in Xopero ONE to configure automated protection for spaces, work items, and related data.
Creating a Jira backup plan in Xopero ONE enables administrators to define how and when Jira data is protected within the backup environment, including selecting the backup scope and configuring the schedule and retention policy.
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.
Granular backup plan focuses on individual Jira components, such as work items, spaces, and attachments, allowing you to restore specific items when needed.
The following steps demonstrate how to create a Jira granular backup plan using Xopero ONE Management Service.
Open the Backup tab (Plans > Backup) and click the + Add plan button in the top bar.
Select Jira from the list.
Select the Jira environment you want to include in the backup and how Xopero ONE will capture the Jira data:
Protect all: protects the entire Jira organization.
Select spaces: protects only selected spaces and their metadata.
Set up a name for your backup plan.
In Data to protect section, click Edit to configure the data that you want to back up. Here, you can also change the default backup agent (worker), which is directly responsible for backing up your Jira data.
Select one of the data stores assigned to your Xopero ONE instance to use as the backup storage.
Customize the scheduler and specify the retention period for your data.
Adjust the advanced settings, such as encryption, error handling, or bandwidth limits, to meet your organization's requirements.
Encryption: lets you secure your backup copy with encryption.
Compression: lets you compress and reduce copy size.
Review your configuration and click Save to create the backup plan, or Save&Run to start the first backup run immediately.
Set rules: captures data to protect based on the specified rules:
A granular Jira backup based on rules defined by the space name behaves the same way as repositories in Git-type projects. For example, the rule git will match only the space with the exact name git. To create name-based rules, you can use the following wildcards:
* represents any number of characters. For example, the rule *git* will match spaces with names such as my-git-1, git, git-100, and similar.
? represents a single character. For example, the rule git-300? will match spaces with names such as git-3001, git-3002, and git-300m.
Error handling: allows you to specify how to handle potential backup operation errors. Includes an option to skip corrupted work item attachments during backup.
Exclude Jira work items: excludes Jira work items from backup according to defined rules.
Bandwidth limit: allows you to reduce network usage and limit network speed during backup.
Backup scripts: enables configuring pre/post scripts executed during backup.
Task balancing: balances backup speed and CPU load.
Prevent system sleep: prevents your system from suspending while a backup is in progress.
Email notifications: lets you set up email notifications and its recipients.
You can deploy multiple agents and assign different agents to each backup plan.
Overview of protected Jira resources, including spaces, work items, and metadata secured by backup.
Jira protected resources define which parts of your Jira environment Xopero ONE can access, secure, and restore.
The following list includes all Jira resources covered by backup. Resources included in backup only for certain space types are marked accordingly:
CMS: data protection available only for company-managed spaces
TMS: data protection available only for team-managed spaces
Overview of the Jira backup process in Xopero ONE, including backup strategy, backup plan creation, and data protection for individual spaces.
The Jira backup process overview outlines the steps Xopero ONE takes to securely back up your Jira organization's data.
Xopero ONE is designed to protect DevOps ecosystems, including Jira.
With Xopero ONE, you can create separate backup plans for critical and non-critical spaces within the same Jira instance. Each plan can use different rotation scheme, ensuring your entire Jira environment is reliably protected.
For example, you can use the recommended Grandfather-Father-Son (GFS) rotation scheme for backup plans protecting critical spaces and metadata that change daily — or even more frequently. For unused spaces that must be retained for future reference, you can create a separate backup plan with a custom rotation scheme. This type of backup primarily serves Jira archival purposes, and with unlimited retention, copies can be stored for as long as needed — even indefinitely.
You can delete spaces from your Jira account while keeping a copy in storage, which helps bypassing Jira limits.
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 creating a backup plan, you define how Xopero ONE protects your data. For Jira, the default data protection method is granular backup.
Granular backup focuses on individual Jira components, such as work items, spaces, or attachments. In granular backup, each space is handled as an individual task — if an error occurs during execution, only the spaces that were successfully backed up will have a restorable backup available.
The granular data protection method allows you to:
*Select individual data to protect, along with a short description of the dependencies visible in the interface (includes information about object activity history, which is disabled by default because it may affect backup performance).
Xopero ONE is a multi-storage system that allows you to store your data in the cloud, locally, or in a hybrid/multi-cloud environment. You can use different storage types to replicate backups, reduce the risk of outages or disasters, and comply with the 3-2-1 backup rule — which means having at least three copies of your data on two different storage types, with at least one copy stored in the cloud.
Guide to Jira backup in Xopero ONE, including plan configuration, scheduling, and protection of spaces, work items, and related data.
Overview of the Jira backup process in Xopero ONE, including backup strategy, backup plan creation, and data protection for individual spaces.
Overview of protected Jira resources, including spaces, work items, and metadata secured by backup.
Learn how to create a Jira backup plan in Xopero ONE to configure automated protection for spaces, work items, and related data.
