Skip site navigation (1) Skip section navigation (2)

Re: Hard link / rsync backup strategy successful

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Greg Spiegelberg" <gspiegelberg(at)gmail(dot)com>, "Chander Ganesan" <chander(at)otg-nc(dot)com>
Cc: "[ADMIN]" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Hard link / rsync backup strategy successful
Date: 2009-07-16 21:27:45
Message-ID: 4A5F55010200002500028896@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Greg Spiegelberg <gspiegelberg(at)gmail(dot)com> wrote: 
 
> That is a recipe for a failed recovery.
 
Our warm standbys seem to disagree with you.
 
> If you must use some file system / volume trickery to get an initial
> backup
 
We don't.  Read it again.  It is *subsequent* backups where we do the
trickery, off of an earlier backup.
 
> The technique does work however if you're using the PostgreSQL PITR
> backup method, which is what I am guessing at, then you're only
> adding overhead and complexity to the process.
 
Disk space for our largest backups is down by 90%, WAN usage by about
99%.  The complexity is about a wash compared with what we were doing
before.  We have scripts to automatically do the backups, use them to
restart warm standbys, detect a successful warm standby restart from a
new backup and delete any now-expendable old backups, and copy monthly
archival copies of backups to archival storage.  All with automatic
proper handling of the related WAL files.  Compared to some of that,
this was easy.
 
-Kevin

In response to

pgsql-admin by date

Next:From: Chander GanesanDate: 2009-07-16 22:19:03
Subject: Re: Hard link / rsync backup strategy successful
Previous:From: Kevin GrittnerDate: 2009-07-16 21:20:35
Subject: Re: Hard link / rsync backup strategy successful

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group