pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Ruprecht <chris@ruprecht.org>
To: pgsql-admin@postgresql.org
Subject: Re: How to do fast, reliable backups?
Date: Sun, 7 Mar 2004 14:47:17 -0500
Message-ID: <3D0F473F-7070-11D8-ABCF-000393447280@ruprecht.org> (raw)
In-Reply-To: <200403061329.17799.silvanadimartino@tin.it>


On Saturday, Mar 6, 2004, at 08:39 US/Eastern, Silvana Di Martino wrote:
>
> Making a copy of your data directory while your server is running is
> definitely a bad idea. Forget it. Backing up the file system used by a 
> RDBMS
> usually requires to put the server off-line and flush all the 
> unwritten data
> to the disk. This cannot be done in a 24/7 environment.
>
>> What I'd like to see is a transaction aware backup which backs up 
>> indexes
>> as well as data.
>

Well, at work we're using a commercial database called Progress. It has 
a very nice backup utility which creates a backup file as follows:

All current database blocks are backed up as they are at the time the 
backup starts. Each DB block has a unique identifier. If a running 
transactions wants to write to a block which has not jet been backed 
up, the transaction is put on hold, the block is backed up and the 
transaction can then continue.

If you restore a database which contains blocks of incomplete 
transactions, these transactions are backed out when you start the DB 
server (broker).

The DB can also (not done by default) maintain an after image log which 
contains all transactions since the last backup. This log needs to be 
kept on a drive, different from the DB. In case the DB drive crashes, 
you can recover from your last backup and then roll forward the after 
image log.

Is there any slight possibility, some mechanism can make it into 
Progresql at some stage (maybe version 8)?

Best regards,
Chris

--
Chris Ruprecht
Network Grunt and Bit Pusher extraordinaíre




view thread (6+ messages)

Message-ID: <3D0F473F-7070-11D8-ABCF-000393447280@ruprecht.org>
Permalink:  ../3D0F473F-7070-11D8-ABCF-000393447280@ruprecht.org/
Also on:    postgresql.org/message-id/3D0F473F-7070-11D8-ABCF-000393447280@ruprecht.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: chris@ruprecht.org
  Subject: Re: How to do fast, reliable backups?
  In-Reply-To: <3D0F473F-7070-11D8-ABCF-000393447280@ruprecht.org>
  References: <200403061329.17799.silvanadimartino@tin.it> <3D0F473F-7070-11D8-ABCF-000393447280@ruprecht.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox