Yesterday we had a serious incident with one of our databases. We lost six hours of database data (issues, merge requests, users, comments, snippets, etc.) for GitLab.com. Git/wiki repositories and self hosted installations were not affected. Losing production data is unacceptable and in a few days we’ll post the 5 why’s of why this happened and a list of measures we will implement.
Update 6:14pm UTC: GitLab.com is back online
As of time of writing, were restoring data from a six-hour-old backup of our database. This means that any data between 5:20pm UTC and 11:25pm UTC from the database (projects, issues, merge requests, users, comments, snippets, etc.) is lost by the time GitLab.com is live again.
Git data (repositories and wikis) and self-hosted instances of GitLab are not affected.
Gratis är gott: Hantera dina e-böcker med Calibre
Calibre är ett program för att lösa, hantera och organisera dina e-böcker. Calibre is a complete e-book library manager....
0 kommentarer