News for hackers. Stuff that matters.

A comment on GitHub Major Service Outage. Parent comment

Re:GitHub Major Service Outage by Filligree on Wednesday May 31, 2017 @10:31AM (#14452810)
It will take a long time before GitLab can even begin to regain my trust from their missing-backups outage.

Problems are to be expected. But as great as it is that they had multiple levels of backup, none of them worked. They hadn't even been tested.

[ Parent | on HN ]
Re:GitHub Major Service Outage by cmatija on Wednesday May 31, 2017 @10:51AM (#14452956)
We have a pretty detailed post-mortem on the timeline of events for the outage, as well as actions taken after it to prevent anything similar in the future (with links to related issues). You can check it out in https://about.gitlab.com/2017/02/10/postmortem-of-database-o...
[ Parent | on HN ]
Re:GitHub Major Service Outage by ChartsNGraffs on Wednesday May 31, 2017 @10:52AM (#14452966)
They actually gained my trust from that outage.
[ Parent | on HN ]
Re:GitHub Major Service Outage by jonknee on Wednesday May 31, 2017 @10:56AM (#14452996)
If you paid for GitLab there was no missing-backups outage...
[ Parent | on HN ]
Re:GitHub Major Service Outage by jjawssd on Wednesday May 31, 2017 @10:49AM (#14452938)
Do you have any evidence that Github does any better?
[ Parent | on HN ]
Re:GitHub Major Service Outage by Xylakant on Wednesday May 31, 2017 @10:51AM (#14452951)
They haven't lost my data so far and they had to restore the production database at least once in their history. All circumstantial, but we'll have to wait and see.
[ Parent | on HN ]
Re:GitHub Major Service Outage by foxylion on Wednesday May 31, 2017 @05:47PM (#14456197)
They did not lose that much data, only a few hours.
[ Parent | on HN ]