Hacker News new | ask | show | jobs
by Shank 2794 days ago
> this disastrous calamity by Github really made me try out Gitlab and in the process

Every company faces problems like this. GitLab infamously lost their entire production database [0] -- and I think we can agree that's more serious. Knee-jerk reactions to incidents will leave you without any "trusted" services, because mistakes happen to everybody at some point. BitBucket has certainly had its own fair share of downtime.

[0]: https://about.gitlab.com/2017/02/10/postmortem-of-database-o...
1 comments
ikornaselur 2794 days ago
> GitLab infamously lost their entire production database

What?? The link you posted says

> Database data such as projects, issues, snippets, etc. created between January 31st 17:20 UTC and 23:30 UTC has been lost. Git repositories and Wikis were not removed as they are stored separately.

> It's hard to estimate how much data has been lost exactly, but we estimate we have lost at least 5000 projects, 5000 comments, and roughly 700 users. This only affected users of GitLab.com, self-hosted instances or GitHost instances were not affected.

How is that "their entire production database"? You make it sound so much worse than it was. While it was a horrible incident, they did not lose their whole production database.

link
PuffinBlue 2794 days ago
Technically they did, for a brief period (24 hours??) at least, they just restored it from backup.

That was the final last ditch backup too where something like 5 out of 6 of the planned backups weren't actually working and nobody realised.

So you're right, they didn't lose it, but they came pretty damn close!

link
codefined 2794 days ago
Picture of the Google Docs post on what they tried (which appears to no longer be available online) can be found:

https://femto.pw/6bsm.png

As a reference to the above poster.

link