From: Merlin Moncure <mmoncure@gmail.com>
To: Michael Nolan <htfoot@gmail.com>
Cc: Richard Broersma <richard.broersma@gmail.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: [GENERAL] PITR - base backup question
Date: Wed, 27 Aug 2008 09:32:56 -0400
Message-ID: <b42b73150808270632t4823d522i42576a2e8022383c@mail.gmail.com> (raw)
In-Reply-To: <4abad0eb0808270618w785f34f1pcb2c8d9b062f2d42@mail.gmail.com>
References: <396486430808261553k6687500q19f4117b6c71ae3f@mail.gmail.com>
<b42b73150808261738j605e1bchc1935f81d695fb08@mail.gmail.com>
<396486430808261804l93855f1gf86d92541a80141@mail.gmail.com>
<b42b73150808270512y2867c937h1710512d6010d3c8@mail.gmail.com>
<4abad0eb0808270618w785f34f1pcb2c8d9b062f2d42@mail.gmail.com>
On Wed, Aug 27, 2008 at 9:18 AM, Michael Nolan <htfoot@gmail.com> wrote:
> I have what I have sometimes called a 'tepid spare' backup. Once a week I
> copy the physical files over to another system (actually to two of them) and
> every few hours I make sure the archived WAL log files are in sync (using
> rsync.)
I have a couple of comments...see below:
> 3. Shut down the Postgresql server running on the backup server, if any
> pg_ctl stop
> (Use 'ps ax' to make sure the server is stopped.)
probably pg_ctl -m fast stop or -m immediate...since we are overwriting it.
> 5. Delete the entire contents of the /disk1/postgres/data directory tree.
> MAKE ABSOLUTELY SURE YOU ARE IN THE /disk1/postgres/data directory!
>
> cd /disk1/postgres/data
> pwd
> rm -rf *
why not just rm -rf /disk1/postgres/data?
> 6. Restore the tar file for the low-level backup from the live server
>
> tar xvf /usr/local/pgsql/tardir/pg_part1.tar
>
> (This restore may take 2-3 hours)
>
> 7. Remove the PostgreSQL log file and the WAL files that were restored
> from the tar archive
I prefer to exclude WAL files from the original tar, and recreate the
folders here (being careful to chown them to postgres account). Every
little bit helps.
> 12. Go to the directory where the WAL files have been archived on
> the server and remove all files older than the file matching the
> last .backup file. The fastest way to do this is as follows:
>
> cd /usr/local/pgsql/archivedir
> ls -1 > files
This is a nice touch. With a little bash-fu you could do a find |
xargs rm and list/kill the files in one pass. In the standby setups
I've done I usually script the whole process, a prep on the main and a
startup on the standby.
merlin
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: mmoncure@gmail.com, htfoot@gmail.com, richard.broersma@gmail.com, pgsql-general@postgresql.org
Subject: Re: [GENERAL] PITR - base backup question
In-Reply-To: <b42b73150808270632t4823d522i42576a2e8022383c@mail.gmail.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