Solution Proposals against Backup Problem

What happened

On Monday, April 4th, 2022 PT approximately 400 Atlassian Cloud customers experienced a full outage across their Atlassian products. As of April 18th, 2022, we have now restored our customers impacted by the outage and have reached out to key contacts for each affected site.

• Communication gap.?First, there was a communication gap between the team that requested the deactivation and the team that ran the deactivation. Instead of providing the IDs of the intended app being marked for deactivation, the team provided the IDs of the entire cloud site where the apps were to be deactivated.
• Faulty script.?Second, the script we used provided both the "mark for deletion" capability used in normal day-to-day operations (where recoverability is desirable), and the "permanently delete" capability that is required to permanently remove data when required for compliance reasons. The script was executed with the wrong execution mode and the wrong list of IDs. The result was that sites for approximately 400 customers were improperly deleted.

Solution Proposal 1: Automatic Backup generation in Backup Manager

Problem Definition of CLOUD-6498 17/Apr/2013

Since we lost some data after a Confluence OnDemand upgrade but noticed the loss later than the 4 weeks, we would like to include the the Confluence backup into our local backup routines.

As I understand one has to manually create an export in the Backup Manager of JIRA and Confluence.

Status Update 16/3/2021

Automatic backup scheduling IS on our list, although not in the very first horizon, as we are looking to completely overhaul the backup/restore experience. Especially for those that have very large datasets. With that said, there will be a mechanism available to automate this yourself, until we build that functionality into the UI.

• https://community.atlassian.com/t5/Backup-Restore/gh-p/backupandrestore

Solution Proposal 2: Bash Script into Cloud Environment

The A-Team, we, could figure it out by automating the process from Atlassian product to the Azure Cloud environment for the worldwide largest copper producer.

Outcomes

• Risks are Owned, Accepted, and Mitigated.
• A strategy for the worst-case scenario is defined.
• The secure backup-restore process is determined.

Backup Architect

Sum up

There are two ways to fix this problem for now. Either you need to wait for the response for the feature ticket or you can take an action by getting in touch with me to build a POC for you.

I would be happy to any comment, contribution or message from you.

Thanks for your reading and stay safe!

Source links

https://www.atlassian.com/engineering/april-2022-outage-update

https://www.bleepingcomputer.com/news/technology/atlassian-finally-explains-the-cause-of-ongoing-cloud-outage/