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

Incrementally Updated Backup

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Incrementally Updated Backup
Date: 2006-09-19 14:09:59
Message-ID: 1158674999.2586.130.camel@holly (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Way past feature freeze, but this small change allows a powerful new
feature utilising the Restartable Recovery capability. Very useful for
very large database backups... 

Includes full documentation.

Perhaps a bit rushed, but inclusion in 8.2 would be great. (Ouch, don't
shout back, read the patch first....)

-----------------------------
Docs copied here as better explanation:

   <title>Incrementally Updated Backups</title>

   <para>
    Restartable Recovery can also be utilised to avoid the need to take
    regular complete base backups, thus improving backup performance in
    situations where the server is heavily loaded or the database is
    very large.  This concept is known as incrementally updated backups.
   </para>

   <para>
    If we take a backup of the server files after a recovery is
partially
    completed, we will be able to restart the recovery from the last
    restartpoint. This backup is now further forward along the timeline
    than the original base backup, so we can refer to it as an
incrementally
    updated backup. If we need to recover, it will be faster to recover
from 
    the incrementally updated backup than from the base backup.
   </para>

   <para>
    The <xref linkend="startup-after-recovery"> option in the
recovery.conf
    file is provided to allow the recovery to complete up to the current
last
    WAL segment, yet without starting the database. This option allows
us
    to stop the server and take a backup of the partially recovered
server
    files: this is the incrementally updated backup.
   </para>

   <para>
    We can use the incrementally updated backup concept to come up with
a
    streamlined backup schedule. For example:
  <orderedlist>
   <listitem>
    <para>
     Set up continuous archiving
    </para>
   </listitem>
   <listitem>
    <para>
     Take weekly base backup
    </para>
   </listitem>
   <listitem>
    <para>
     After 24 hours, restore base backup to another server, then run a
     partial recovery and take a backup of the latest database state to
     produce an incrmentally updated backup.
    </para>
   </listitem>
   <listitem>
    <para>
     After next 24 hours, restore the incrementally updated backup to
the
     second server, then run a partial recovery, at the end, take a
backup
     of the partially recovered files.
    </para>
   </listitem>
   <listitem>
    <para>
     Repeat previous step each day, until the end of the week.
    </para>
   </listitem>
  </orderedlist>
   </para>

   <para>
    A weekly backup need only be taken once per week, yet the same level
of
    protection is offered as if base backups were taken nightly. 
   </para>

  </sect2>

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com

Attachment: iubackup.patch
Description: text/x-patch (5.6 KB)

Responses

pgsql-hackers by date

Next:From: John MeyerDate: 2006-09-19 14:11:21
Subject: Re: vista
Previous:From: Martijn van OosterhoutDate: 2006-09-19 14:09:40
Subject: Re: vista

pgsql-patches by date

Next:From: Andrew DunstanDate: 2006-09-19 14:11:39
Subject: Re: [PATCHES] Patch for UUID datatype (beta)
Previous:From: Jim C. NasbyDate: 2006-09-19 13:53:05
Subject: Re: [PATCHES] Patch for UUID datatype (beta)

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