{"id":3804,"date":"2023-01-12T09:40:26","date_gmt":"2023-01-12T09:40:26","guid":{"rendered":"https:\/\/gitprotect.io\/blog\/?p=3804"},"modified":"2024-11-21T12:44:26","modified_gmt":"2024-11-21T12:44:26","slug":"jira-backup-to-s3","status":"publish","type":"post","link":"https:\/\/gitprotect.io\/blog\/jira-backup-to-s3\/","title":{"rendered":"Jira Backup to S3"},"content":{"rendered":"\n

Jira is a versatile and critical tool for more than 125,000 companies worldwide. That’s enough reason to perform Jira data with automated backup to S3 storage as part of a thoughtful strategy to protect valuable data and business continuity.<\/strong>\u00a0<\/p>\n\n\n\n\n\n\n\n

Almost any software matching Jira environment complexity is susceptible to information loss \u2013 mainly due to human errors.<\/p>\n\n\n\n

According to Verizon<\/a>, it happens in up to 85% of cases. If so, a robust plan for automated backups becomes crucial for broader data protection tactics.<\/p>\n\n\n\n\n\n

Backup options for Jira Cloud and Jira Service Management<\/h2>\n\n\n\n

Each Jira (Cloud) backup file is stored in the local file system by default. However, there are three possibilities:<\/p>\n\n\n\n

Jira Cloud backup<\/strong><\/h3>\n\n\n\n

If your firm uses Jira Cloud, Atlassian provides a built-in backup solution<\/a>. You can create a backup schedule or do it manually when storing and restoring data in Atlassian’s cloud.<\/p>\n\n\n\n

Jira Data Center (formerly Jira Server) backup<\/strong><\/h3>\n\n\n\n

In this case, you can rely on the provided backup manager to create and manage backup data. They can be stored locally or in an external service, like S3.<\/p>\n\n\n\n

Third-party apps<\/strong><\/h3>\n\n\n\n

Various applications available on Atlassian Marketplace offer advanced backup and restore features<\/a> for Jira. They can integrate with S3, supporting automation.<\/p>\n\n\n\n

Nonetheless, Atlassian recommends using the Amazon S3 solution to store backups. Especially, for the companies that manage large datasets and need to scale according to their needs.<\/p>\n\n\n\n

Additionally, Atlassian suggests transferring backups to S3 in XML file format. For improved security, you may also use native database backups.<\/p>\n\n\n\n

It’s suffice to point out that currently (2024):<\/p>\n\n\n\n

\n

Jira Cloud does not support automated backups. Currently, you can perform data-only backups (which exclude attachments, avatars, and logos) at any time. When you create a backup that includes attachments, avatars, and logos, you will need to wait 48 hours from the last time you created a backup with attachments.<\/p>\n\n\n\n

Source: Jira Software support<\/a>.<\/em><\/p>\n<\/blockquote>\n\n\n\n

7 reasons to protect Jira data in Amazon S3<\/h2>\n\n\n\n

S3 (Simple Storage Service) offers several advantages, making it a top choice for Jira backups.<\/p>\n\n\n\n

Scalability<\/strong><\/h3>\n\n\n\n

It allows you to accommodate the growing data volumes of Jira instances. No (if any) significant infrastructure changes are needed.<\/p>\n\n\n\n

Security<\/h3>\n\n\n\n

S3’s security<\/strong> is mainly based on solid SSE-S3 or SSE-KMS server-side encryption. Client-side security is also provided at rest or during data transmission.<\/p>\n\n\n\n

Durability<\/strong><\/h3>\n\n\n\n

It enhances data protection against hardware failures and other risk. The modern standard is 99.99999999999% durability.<\/p>\n\n\n\n

Cost-effectiveness<\/strong><\/h3>\n\n\n\n

The cost-effectiveness related to S3s is higher than that of the traditional backup solutions – especially for large datasets.<\/p>\n\n\n\n

Integration<\/h3>\n\n\n\n

Fast integration with various cloud services and tools makes S3 easy to incorporate into the existing IT stack.<\/p>\n\n\n\n

Security<\/h3>\n\n\n\n

Robust security features, including encryption and access control, allow S3 to protect sensitive data effectively.<\/p>\n\n\n\n

Compliance<\/h3>\n\n\n\n

Compliance<\/a> with GDPR, SOC 2, PCI DSS, FedRAMP, or HIPAA is a part of the solution.<\/p>\n\n\n\n

What S3 for Jira backup file<\/h2>\n\n\n\n

As mentioned, Atlassian recommends utilizing the Amazon S3 capabilities offered by AWS (Amazon Web Services). In recent years, however, five players have dominated the market.<\/p>\n\n\n\n

AWS S3 [H3]<\/h3>\n\n\n\n

Easily scales with your Jira instance growth. Jira tools and third-party apps usually natively support AWS S3, simplifying automation and management.<\/p>\n\n\n\n

Microsoft Azure Blob<\/h3>\n\n\n\n

It offers slightly more complex pricing tiers than AWS but is competitive for large data volumes.<\/p>\n\n\n\n

Wasabi<\/h3>\n\n\n\n

The solution is considered low-cost storage. It’s ideal for large and infrequently accessed data. The offer does not include API request fees or egress.<\/p>\n\n\n\n

Backblaze B2<\/h3>\n\n\n\n

B2 is recognized as one of the most affordable cloud storage services. It works with S3- S3-compatible APIs but may require some third-party tool(s).<\/p>\n\n\n\n

Google Cloud Storage<\/h3>\n\n\n\n

By definition, GCS is not an S3 storage. Nonetheless, it provides similar features and benefits. In the case of Jira backup, some additional apps might involve custom configurations.<\/p>\n\n\n\n

It’s natural to underline that you should go through configuration requirements to check if a given service suits your needs and fits your current and future applications.<\/p>\n\n\n\n

Jira backup to S3-compatible storage<\/h2>\n\n\n\n

After choosing your S3 provider or following Atlassian’s recommendation, you can create a connection to your Jira (Cloud) with an S3 bucket. Now, let’s do it in a step-by-step guide.<\/p>\n\n\n\n

The first thing to do is configure your S3 storage<\/a> (or reconfigure the existing one). In our case, it’s AWS S3.<\/p>\n\n\n

\n
\"Jira<\/figure><\/div>\n\n\n

Source: Atlassian support<\/a> documentation.<\/em><\/p>\n\n\n\n

Next, you can set up the backup storage in Amazon S3 via the filestore-config.xml file in Jira <localhome>. To utilize S3 as your destination for backup data, the filestore attribute in filestore-config.xml must be modified to correspond to the s3-filestore ID.<\/p>\n\n\n\n

By using S3 for avatars, you can modify filestore-config.xml to store backups as well by adding an association element for backups.<\/p>\n\n\n\n

In addition, the filestore attribute should point to that bucket if you intend to store backups in the same bucket as avatars.<\/p>\n\n\n\n

To use different buckets, create multiple <s3-filestore> elements and reference them in the respective association targets.<\/p>\n\n\n\n

For example:<\/p>\n\n\n\n

<?xml version=\"1.1\" ?>\n<filestore-config>\n  <filestores>\n    <s3-filestore id=\"avatarBucket\">\n      <config>\n        <bucket-name>jira-avatar-bucket<\/bucket-name>\n        <region>us-east-1<\/region>\n      <\/config>\n    <\/s3-filestore>\n    <s3-filestore id=\"backupBucket\">\n      <config>\n        <bucket-name>jira-backup-bucket<\/bucket-name>\n        <region>us-east-1<\/region>\n      <\/config>\n    <\/s3-filestore>\n  <\/filestores>\n  <associations>\n    <association target=\"avatars\" file-store=\"avatarBucket\" \/>\n    <association target=\"backups\" file-store=\"backupBucket\" \/>\n  <\/associations>\n<\/filestore-config><\/code><\/pre>\n\n\n\n
Source: Atlassian.com<\/a>.<\/em><\/p>\n\n\n\n
And finally, to keep backups in a Jira <sharedhome> directory, you can remove the backup association element. If Amazon S3 isn’t set up or filestore-config.xml is not found in <localhome>, Jira will default to storing backups locally.<\/p>\n\n\n\n
<?xml version=\"1.1\" ?>\n<filestore-config>\n  <filestores \/>\n  <associations \/>\n<\/filestore-config><\/code><\/pre>\n\n\n\n
Source: Atlassian.com<\/a>.<\/em><\/p>\n\n\n\n
It looks slightly different when the Jira installation operates on an IPv6-only network<\/strong>. In that case, overriding the default endpoint with the dual-stack endpoint is necessary.<\/p>\n\n\n\n
<?xml version=\"1.1\" ?>\n<filestore-config>\n  <filestores>\n    <s3-filestore id=\"backupBucket\">\n      <config>\n        <bucket-name>dualstack-bucket<\/bucket-name>\n        <region>us-east-1<\/region>\n        <endpoint-override>https:\/\/s3.dualstack.us-east-1.amazonaws.com<\/endpoint-override>\n      <\/config>\n    <\/s3-filestore>\n  <\/filestores>\n  <associations>\n    <association target=\"backups\" file-store=\"backupBucket\" \/>\n  <\/associations>\n<\/filestore-config><\/code><\/pre>\n\n\n\n
Source: Atlassian.com<\/a>.<\/em><\/p>\n\n\n\n
The above XML examples also allow you to store attachments, issue types, or any log.<\/p>\n\n\n\n
After configuring the S3 bucket, verify if it successfully stores Jira backups. In Administration<\/em> <\/strong>-> System<\/em><\/strong>, under the Backup system<\/em><\/strong>, check the bucket name and region for your backup files.<\/p>\n\n\n\n
GitProtect – A more convenient approach to the backup process<\/h2>\n\n\n\n
To sum it up, moving Jira backups from the local repository to an Amazon S3 bucket is essential to increasing data security and avoiding data loss.<\/p>\n\n\n\n
After all, integrating backup automation into your workflow is a vital step, whether you’re using Jira (Cloud) Software or Jira Service Management.<\/p>\n\n\n\n
However, there is a more secure and convenient method to control Jira backup projects utilizing AWS services. You can use the GitProtect platform.<\/p>\n\n\n\n
All-in-one Jira backup manager<\/h3>\n\n\n\n
GitProtect is a backup and recovery software designed for the DevOps ecosystem. The tool protects not only source code, but also all the related metadata, such as:<\/p>\n\n\n\n