nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BCP solution options on Atlassian cloud

Mit Tolia

Hi All - we are working on an Atlassian cloud migration and wanted to explore how others in the community have approached in designing a Business Continuity Plan - BCP solution, once the move to cloud has happened

Am aware that Atlassian does offer a DR mechanism in place where if the cloud site goes down, there is a fallback mechanism so that site is up & running.

What are the other options to leverage & consider, to ensure that the business critical data from the cloud is always accessible - via backups? via excel/csv exports? some other custom solution?

Accepted answers

All comments

Petter Gonçalves

Hello @Mit Tolia

Thank you for reaching out.

As you mentioned, Atlassian indeed has a DR mechanism that keeps all customer's data safe and restorable at any time, however, this mechanism can only be triggered for outages or issues on the Atlassian application side.

In other words, we can not trigger this mechanism for specific sites when the root cause of the data loss is on the customer side. E.g:

Issues or pages deleted by users
Manual reset of Atlassian site by the organization admin
Deleted components by an application user in general (Projects, Workflows, etc)

We provide the following methods to prevent or restore the data for those scenarios:

1 - Granular permission levels:

These settings allow the organization admin to prevent users that are unfamiliar with the Jira structure from accidentally deleting data.

Besides the administration levels (Organization and product admins), you can also restrict specific users from deleting Jira issues or Confluence pages in a granular way.

2 - Allow the generation and restore of application backup from the client side:

Both Jira and Confluence provide a tool that you can use to properly export data to an XML file containing all the site details, which can be imported back to an Atlassian site at any time. This tool is very useful to create daily backups for wide-open Atlassian instances that allow access to a big number of individuals, where the risk of accidental data deletion might be high.

You can check the links below for more information:

Create a site backup - Confluence

Create a site backup - Jira

For now, neither of the backup tools mentioned above can be automatically scheduled directly from the application, however, you can easily build an external script to do that.

3 - The CSV and JSON options

Finally, you can use CSV and JSON exports to properly backup your data. The problem with this approach is that some features and components are not included in those backups, while others are not supported. E.g:

Issue History
Some team-managed project details (Jira)
Some application links

Let us know if you have any questions.

Ed Letifov _TechTime - New Zealand_

@Petter Gonçalves

As far as I am aware currently it's impossible to import Confluence data as a whole site from the backup that the same Confluence allows you to make, you can only import individual spaces.

As such suggesting this as a viable option for backup is *extremely* misleading.

Sanket Parlikar _Revyz_

Hello @Mit Tolia

As one of the BCP strategies, you may want to look at 3rd party app for backup and restore of Atlassian Cloud apps. Revyz offers data protection for Jira Software Cloud with Confluence Cloud on roadmap.

Mit Tolia

Thanks @Petter Gonçalves & @Ed Letifov _TechTime - New Zealand_ for sharing your perspectives and some options to consider.

I'd agree as that was going to be my follow-on question from this response to understand if there are any known constraints to be aware of, especially when one tries to restore the backup - Jira & Confluence.

We are working in an environment which is highly regulated, hence need to clearly articulate some of these aspects to make an informed decision

Mit Tolia

Thanks @Sanket Parlikar {Revyz} - I suspect we will start to look at 3rd party solutions in greater detail at some point in time, but, with any 3rd party apps there would need to be a thorough due diligence to ensure all the security & compliance elements are covered off with any options we consider - that in itself will be a lengthy and time consuming exercise, hence first exploring what can be achieved by & around the Atlassian core functionality

Danny Grenzowski _Rewind_

Hey @Mit Tolia, my team at Rewind built an automated backup and restore solution for Jira Cloud for DR purposes. It's hosted on a separate, secure cloud too, so that in the case of a Jira outage your backups are still accessible.

Try it free for 7 days on the Atlassian Marketplace:

https://marketplace.atlassian.com/apps/1226389/

Saralie S.

@Sanket Parlikar {Revyz} Please review our guidelines for Marketplace and Solution Partners , specifically:

Identify yourself as a partner: Make sure the user is aware you are affiliated with a partner company; for example, by placing the name of your company in your user name in {curly brackets} or -dashes-

Please disclose your association to the marketplace app you've linked and update your profile!

Petter Gonçalves

Hey @Ed Letifov _TechTime - New Zealand_

Thank you for your feedback and sorry if my last message was not clear, however, I kindly disagree with your last statement. Please, allow me to go a little deeper into your statement so we can confirm we are on the same page:

As far as I am aware currently it's impossible to import Confluence data as a whole site from the backup that the same Confluence allows you to make, you can only import individual spaces.

Actually, the backup from Confluence containing all the spaces can be fully imported to other Confluence sites. The limitation you mentioned only applies if the destination site also has Jira under the same Organization - We even have a public feature request to fix this limitation:

Provide functionality to import Confluence Cloud site when Atlassian Cloud site has Jira

Considering the fact above, I don't see this limitation as a blocker as it can be avoided with simple steps. Allow me to provide some scenarios:

A space or page was deleted and needs to be restored:

Having the full site backup, you can fix that by following the steps below:

Sign-up for a new Confluence Cloud site - free trial
Import your backup to the new site
Export the deleted space and import it back to your original Confluence site

The Confluence site was deleted, together with all of your Confluence spaces

Having the full site backup, you can fix that by following the steps below:

Sign-up for a new Confluence site - free trial
Import your backup to the new site
Optionally, transfer the product/site to your original organization, so your Confluence site can be under the same organization as your Jira site

P.S: Another limitation that can happen here would be if the backup file exceeds 200 MB (Not considering attachments). Although you must have a giant environment to achieve this limit, you can also work around this limitation by importing your site to a data center instance instead of Cloud and using the Cloud migration assistant to run the import to Cloud, which does not have the limit of 200 MB.
We recommend exporting a backup to Server as well to ensure this workaround can be implemented.

As such suggesting this as a viable option for backup is *extremely* misleading.

I believe that exporting the site's full backup within a time range is not only viable but the best option to ensure your Confluence data is secure, as it can be imported at any time to a Confluence site and have its data properly restored.

Please, let me know if you have a different opinion.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud