Hacker News Reader

Comment by Rantenki | Hacker News Reader

I've repeatedly asked Atlassian if:

1. They can confirm that they have backups of our data (about a thousand stories, substantial confluence, opsgenie history, and three service desks).

2. Will our integrations, configuration, and customizations also be recovered, or will we need to rebuild those once our data is recovered?

I have received no response, and no human is even willing to acknowledge those questions. The service desk staff ignore them as if I never asked. Repeatedly.

Also, I've been asking around, and haven't been able to find a single story from somebody that can confirm that they were down, who has had their data recovered.

View on HN

I was down, my instance is fully restored right now.

1. They do, every 25 hours, via snapshot. I have spoked to their team since the incident and that same thing is in this article. 2. Yes, they recover all of it. Some things have had issues, external mailboxes attached to service management projects, some attachment rendering slowness. Filters needing to be overlayed into our instance again, but otherwise it is running fine again.

Not sure what to tell you other than they are fixing life saving companies first, then the rest. That is what they have told us.

Thank you for responding here. Even a single successful restoration, anecdotal as it is, makes me feel a lot better about the situation. I was honestly wondering if Atlassian was just pushing the date out to soften the eventual backlash when they had to announce data loss.

Life saving Jira tickets?

FWIW Jira and Confluence and used in life sciences firms, though they are rarely more useful than Google Docs. Self hosting in this context was the norm but that is changing.

There is a thing that I dont understand, from their blog/report [1]

If the script was used in "permanently delete" mode, which is intended for compliance... how do you restore?

Is it the only explanation... if the deletion is non-compliant?

> 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.

[1] https://www.atlassian.com/engineering/april-2022-outage-upda...

Under GDPR you don't need to scrub your backups, just your working data:

https://www.itgovernance.eu/blog/en/the-gdpr-how-the-right-t....

Update: My instance was recovered over this weekend (Apr 16). We've verified that integrations (webhooks, jira integrations) are working, and no data was lost that we can see (nobody works overnight, so our last change was at the end of the working day, which matched our recollection).

Reply on news.ycombinator.com