From: Scott Whitney <swhitney@journyx.com>
To: 'Bruce Momjian' <bruce@momjian.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Using rsync for base backups for PITR
Date: Wed, 10 Oct 2007 11:46:02 -0500
Message-ID: <20071010164227.7D89F3F2710@mail.int.journyx.com> (raw)
In-Reply-To: <200710101639.l9AGdRr01651@momjian.us>
In the same way that you don't have a valid archive while the tar is
running, no? In either case, I have to archive the WAL segments used during
the file system backup, right?
Is rsync a supported method for a warm standby server? Specifically, I'm
thinking about:
http://www.taygeta.com/ha-postgresql.html
-----Original Message-----
From: Bruce Momjian [mailto:bruce@momjian.us]
Sent: Oct 10, 2007 11:39 AM
To: Scott Whitney
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Using rsync for base backups for PITR
Scott Whitney wrote:
> I'm reading conflicting information on this. Is this a supported
technique?
>
> start_backup
> rsync the initial base backup
> stop_backup
>
> Then, periodically,
> start_backup
> rsync again
> stop_backup
>
> It's my opinion that this wouuld significantly cut down the 30GB base
backup
> I'll need to take for each PITR.
Uh, well, yes, that will work, but you don't have a valid archive
_while_ the rsync is happening. I think that would be a problem if
there was a failure during the rsync update.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: swhitney@journyx.com, bruce@momjian.us
Subject: Re: Using rsync for base backups for PITR
In-Reply-To: <20071010164227.7D89F3F2710@mail.int.journyx.com>
* 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