Jira Backup Process Overview

Xopero ONE is built for Jira protection too. To be sure that all of your Jira environment is reliably protected make sure to back up all projects. The best practice is to create a backup plan for critical projects that change on the daily basis (or even more frequently) for example using recommended Grandfather-Father-Son (GFS) rotation scheme and another backup plan for unused projects that you need to keep for any future reference. This kind of backup is required more for Jira archive goals and due to unlimited retention, you can store your copies for as long as you need – even infinitely. Moreover, you can even delete those projects from your Jira account and keep the copy on storage to bypass Jira limits.

Backup type

Incremental and differential backups save your storage space. Your backup software should include only changed blocks of your Jira data since the last copy to reduce the backup size on your storage, speed up backup and limit bandwidth. Moreover, in the perfect scenario, you should be able to define different retention and performance schemes for every type of copy (full, incremental, and differential).

Adding multiple storage instances

Use different types of storages to replicate backups between storages, eliminate any outage or disaster risk and meet the 3-2-1 backup rule. It says that you should have at least 3 copies on 2 different storage instances with at least 1 in the cloud.

Xopero ONE is a multi-storage system. It allows you to store your data:

  1. in the cloud (Xopero ONE Cloud, AWS S3, Wasabi Cloud, Backblaze B2, Google Cloud Storage, Azure Blob Storage, and any public cloud compatible with S3),

  2. locally (NFS, CIFS, SMB network shares, local disk resources),

  3. in hybrid environment/multi-cloud

Create a dedicated Jira user

The best practice for big, enterprise users is to create a dedicated Jira user account that will be connected to Jira backup software and responsible only for backup purposes (ie. backup@companyname.com). It is due to security reasons. It means that this user should have access only to the projects it aims to protect.

Last updated