Re: Incremental Backup Script - Mailing list pgsql-hackers

From Gregor Zeitlinger
Subject Re: Incremental Backup Script
Date
Msg-id 5DE489C997EC984FA3DD0935879DAE1255EB21@ex09-00-z002.torexretail.de
Whole thread Raw
In response to Incremental Backup Script  ("Gregor Zeitlinger" <gregor.zeitlinger@torexretail.de>)
List pgsql-hackers
-----Original Message-----
From: Zach Bagnall [mailto:zach.bagnall@bulletinwireless.com]
Sent: Wednesday, January 04, 2006 4:42 AM
To: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Incremental Backup Script


>Gregor: can you explain how to identify the current file? I had
>implemented a backup and restore script for PITR but stumbled at this
>point. The page above does not specify how this is to be done.
I have found a way from http://archives.postgresql.org/pgsql-admin/2005-10/msg00059.php. I have not tried it, but it
seemsstraightforward. 

>I appreciate the addition of PITR - it's better than nothing (nothing
>being full dumps) in some respects. Ideally, we need to be able to dump
>deltas for a single database.
Yes, it is not a replacement for an incremental backup, especially due to the fact that WALs may be orders of magnitude
largerthan a delta. 

>In practice, restoration using the PITR
>method is awkward.
Yes, what I am planning to do:
1) drop the corrupted database
2) restore the base backup
3) replay all incremental backups (in the sense of my original mail)

Gregor Zeitlinger
LUCAS Product Development

Torex Retail Solutions GmbH

Schwedenstr. 9, D-13359 Berlin
Tel. +49 (0) 30 49901-243
Fax +49 (0) 30 49901-139
Mailto:gregor.zeitlinger@torexretail.de
http://www.torexretail.de


pgsql-hackers by date:

Previous
From: Rick Gigger
Date:
Subject: Re: Incremental Backup Script
Next
From: John DeSoi
Date:
Subject: Re: psql & readline & win32