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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
