OT: GitLab data loss postmortem
From: Rich J <rjoralist3_at_society.servebeer.com>
Date: Wed, 08 Feb 2017 09:26:23 -0600
Message-ID: <11412af982b196d6076cec6c5e97387a_at_society.servebeer.com>
Hey all,
Date: Wed, 08 Feb 2017 09:26:23 -0600
Message-ID: <11412af982b196d6076cec6c5e97387a_at_society.servebeer.com>
Hey all,
A good short read about a potential RGE* for any DBA:
https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/
The key seems to be on the Third Incident where "After a second or two he notices he ran it on db1.cluster.gitlab.com, instead of db2.cluster.gitlab.com.", coupled with "So in other words, out of five backup/replication techniques deployed none are working reliably or set up in the first place."
Bummer.
Rich
- RGE = Résumé Generating Event
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Feb 08 2017 - 16:26:23 CET