Overview of Atlassian backups
We’re rolling out a new backup and restore experience for a limited number of customers on the Enterprise plan through an open beta program.
Backup and restore isn’t available in the Atlassian Government environment.
Atlassian Cloud backup and restore allows you to seamlessly back up data for your Jira and Confluence apps from admin.atlassian.com. You can run backups once, or schedule them daily or weekly. You can choose to store backups in an Atlassian-owned storage or in your organization’s Amazon S3 storage.
Benefits of data backup and restore
Backup and restore processes have several benefits that help ensure the safety and integrity of data. These benefits include:
Data protection: Backups protect your data by creating a copy that can be restored in case of a data loss event. This could be due to accidental deletion, hardware failure, software corruption, or a security breach.
Regulatory compliance: Many industries have regulations requiring companies to maintain certain records for a specific period. Regular backups help meet these regulatory compliance requirements.
Who can use the backup and restore solution?
You need to have organization admin and app admin permissions to backup and restore data.
Data retention
You can choose to store backups in an Atlassian-owned storage or your organization’s Amazon S3 storage. You can’t download files and attachments because we store only references to the files and not the actual files. This reduces the time to take backups.
Data retention in the Atlassian storage
Each backup is stored in the Atlassian storage for 14 days and expires on the 15th day. You can't restore expired backups.
For instance, if you set up a daily backup on the first of the month, you will have 14 backups on the 14th. The backup that was set up on the 1st will expire on the 15th.
Data retention in your Amazon S3 storage
You can restore backups within 30 days of creating them.
Recovery Point Objective and Recovery Time Objective
In backup and restore, Recovery Time Objective (RTO) means the maximum amount of time a system or its data can be unavailable after something goes wrong before it must be restored. This means that if the RTO is 12 hours, it will take a maximum of 12 hours to recover in case of a disaster.
Recovery Point Objective (RPO) is the amount of data measured in time that an organization can afford to lose if something goes wrong. A smaller RPO means more frequent backups and less data loss, while a larger RPO means fewer backups and more data loss.
The RPO and RTO depend on the size of the backups.
Jira
RTO for data size up to 60 GB and attachment size up to 3.5 TB | 12 hours |
|---|---|
RTO for data size more than 60 GB and attachment size more than 3.5 TB | More than 12 hours. Contact our support team to help you restore. |
RPO for data size up to 240 GB and attachment size up to 12 TB | 24 hours |
RPO for data size more than 240 GB and attachment size more than 12 TB | More than 24 hours. Daily backup isn’t available. |
Confluence
RTO for backup size up to 30 GB and attachment size up to 12 TB | 12 hours |
|---|---|
RTO for backup size more than 30 GB and more than 12 TB | More than 12 hours |
RPO for data size up to 120 GB and attachment size up to 12 TB | 24 hours |
RPO for data size more than 120 GB and attachment size more than 12 TB | More than 24 hours |
Was this helpful?