Process overview
Learn more about the backup process for Jira.
General information
Xopero ONE is designed to protect DevOps ecosystems, including Jira.
To ensure your entire Jira environment is reliably backed up, make sure to include all repositories along with their related metadata — the best practice is to create a backup plan for critical repositories and metadata that change daily (or even more frequently), for example, using the recommended Grandfather-Father-Son (GFS) rotation scheme.
Additionally, create a separate backup plan for unused repositories that you need to keep for future reference. This type of backup primarily serves Jira archival purposes, and with unlimited retention, you can store your copies for as long as needed — even indefinitely.
You can also delete repositories from your Jira account while keeping a copy in storage, which helps bypass Jira limits.
Backup type
Incremental and differential backups help save storage space. Your backup software should include only the blocks of Jira data that have changed since the last backup, reducing storage usage, speeding up the process, and limiting bandwidth. Ideally, you should be able to define different retention and performance settings for each type of backup (full, incremental, and differential), which Xopero ONE supports.
Adding multiple storage instances
Use different types of storage to replicate backups, minimize 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).
Xopero ONE is a multi-storage system that allows you to store your data:
Last updated