News for hackers. Stuff that matters.
Re:Inside the longest Atlassian outage by qiskit on Wednesday April 13, 2022 @01:01PM (#31017133)
> However, if they [restore backups], while the impacted ~400 companies would get back all their data, everyone else would lose all data committed since that point

How would they lose committed data? Even after restoring the backups can't they run the logs so that everyone is caught up?

Re:Inside the longest Atlassian outage by mh- on Wednesday April 13, 2022 @02:59PM (#31018748)
(There's a tacit assumption here that the data across tenants is commingled in tables, and that's being disputed elsewhere in the thread, but playing along..)

You wouldn't be able to do that without forcing downtime for all customers, for the duration it takes to restore the snapshot and then replay the logs. Not to mention the risks of the process failing somehow

You could narrow the window to just the "replay" portion, if you were able to stand up an extra database/infra, to switch over to when it was ready. But at some point you'd probably still have to go read only to checkpoint the logs and begin the replay.

It's of course possible to do something more complicated here and stream the changes then eventually enact a failover, but this would all be too complex and error prone to introduce in their current crisis mode. It's something I'd suggest considering when architecting their DR/BCP, but it's too late for that kind of elegance (and complexity) now.

Re:Inside the longest Atlassian outage by drjasonharrison on Wednesday April 13, 2022 @02:51PM (#31018634)
Are you assuming that they record the events in a way that can be played back?