You can sleep soundly: it seems like they back _everything_ up:
> Second, the script we used provided both the "mark for deletion" capability
... (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.
> To recover from this incident, our global engineering team has implemented a
> methodical process for restoring our impacted customers.
Anyone else find it disturbing that they are able to restore data that they deleted permanently for "compliance" reasons? If this is true, how were they ever compliant? I guess data is only permanently deleted when the engineering team is following their typical, non-methodical process...
> Second, the script we used provided both the "mark for deletion" capability ... (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.
> To recover from this incident, our global engineering team has implemented a > methodical process for restoring our impacted customers.
[https://www.atlassian.com/engineering/april-2022-outage-upda...]
Anyone else find it disturbing that they are able to restore data that they deleted permanently for "compliance" reasons? If this is true, how were they ever compliant? I guess data is only permanently deleted when the engineering team is following their typical, non-methodical process...