Re: Interesting post-mortem on a near disaster with git

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Interesting post-mortem on a near disaster with git
Date: 2013-03-24 18:22:42
Message-ID: 514F4472.9000807@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/24/2013 05:08 PM, Martijn van Oosterhout wrote:
> On Sun, Mar 24, 2013 at 11:52:17AM -0400, Tom Lane wrote:
>> Over the weekend, KDE came within a gnat's eyelash of losing *all*
>> their authoritative git repos, despite having seemingly-extensive
>> redundancy. Read about it here:
>> http://jefferai.org/2013/03/24/too-perfect-a-mirror/
>>
>> We should think about protecting our own repo a bit better, especially
>> after the recent unpleasantness with a bogus forced update. The idea
>> of having clones that are deliberately a day or two behind seems
>> attractive ...
>
> I think the lesson here is that a mirror is not a backup. RAID, ZFS,
> and version control are all not backups.
>
> Taking a tarball of the entire repository and storing it on a different
> machine would solve just about any problem you can think of in this
> area.

fwiw - the sysadmin team has file-level backups of all pginfra hosts
(two backups/day, one per day for a week and a full per week for 4 weeks
of history).

Stefan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-03-24 19:10:55 Re: patch to add \watch to psql
Previous Message Ants Aasma 2013-03-24 18:07:24 Re: Page replacement algorithm in buffer cache