Re: Issue with rsync based incremental backup : postgres: startup process waiting for 0000000100000001000000D2 - Mailing list pgsql-general

From Michael Nolan
Subject Re: Issue with rsync based incremental backup : postgres: startup process waiting for 0000000100000001000000D2
Date
Msg-id CAOzAquK_abvcmBGwPW2MbpNtVseAmUrF-Zvxv0EJZJcQ54CHiA@mail.gmail.com
Whole thread Raw
In response to Issue with rsync based incremental backup : postgres: startup process waiting for 0000000100000001000000D2  (Samba <saasira@gmail.com>)
Responses Re: Issue with rsync based incremental backup : postgres: startup process waiting for 0000000100000001000000D2
List pgsql-general


On Thu, May 3, 2012 at 11:49 AM, Samba <saasira@gmail.com> wrote:
Hi,

Please advise me if what i'm doing is makes sense and is an accepted mechanism for taking backups or if there is any other procedure that i can emplpoy to avoid unnecessarily archiving gigabytes of WAL logs which may be growing many times the size of the actual data directory.

Thanks and Regards,
Samba


The problem is that rsync isn't copying all the xlog files created during the time the rsync is taking place, which is why it is complaining that there are files missing.

There may be other logical flaws with your process as well.

Something similar to the steps given in "Starting Replication with only a Quick Master Restart" as laid out in the wiki tutorial on binary replication might give you a way to make this work.  (You probably won't need the restart of the master, since you're not actually setting up replication, so you won't be changing the postgresql.conf file on your master.)

This uses a two-step process.  First you copy all the files EXCEPT the ones on pg_xlog, then you copy those files, so you have a complete set.

See http://wiki.postgresql.org/wiki/Binary_Replication_Tutorial
--
Mike Nolan

pgsql-general by date:

Previous
From: "Gauthier, Dave"
Date:
Subject: privs drop after alter table
Next
From: Josh Kupershmidt
Date:
Subject: Re: privs drop after alter table