Re: Database backup mechanism

From: Richard Huxton <dev(at)archonet(dot)com>
To: Doug Knight <dknight(at)wsi(dot)com>
Cc: RaviKumar(dot)Mandala(at)versata(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Database backup mechanism
Date: 2007-02-09 15:11:39
Message-ID: 45CC8F2B.6070405@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Doug Knight wrote:
> I would also be interested in any "creative" ways to reduce the size and
> time to backup databases/clusters. We were just having a conversation
> about this yesterday. We were mulling over things like using rsync to
> only backup files in the database directory tree that actually changed.
> Or maybe doing a selective backup of files based on modified times, etc,
> but were unsure if this would be a safe, reliable way to backup a
> reduced set of data.

Most of your virtual-layer filesystems should offer a snapshot facility
that lets the database think its writing to the files while you see a
static version. You could rsync that against an older file-level copy as
the base copy in a PITR backup.

Note - even with a snapshot facility you need to use PITR or stop the
database to get a guaranteed working copy.

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2007-02-09 15:12:03 Re: HOT for PostgreSQL 8.3
Previous Message Jan Wieck 2007-02-09 15:11:34 Re: referential Integrity and SHARE locks