From: Vladimir Rusinov <vladimir@greenmice.info>
To: Shilpa Sudhakar <ssudhakar@internode.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL archiving
Date: Fri, 22 Feb 2008 10:35:05 +0300
Message-ID: <f6fdfb550802212335q2579120ah5f521d12d49ae36b@mail.gmail.com> (raw)
In-Reply-To: <47BE07ED.1070802@internode.com.au>
References: <47BE07ED.1070802@internode.com.au>
On 2/22/08, Shilpa Sudhakar <ssudhakar@internode.com.au> wrote:
>
> I am new to postgres and have been slowly learning the concepts.
>
> Regarding WAL archiving, we first take a base backup and then save all
> the wal logs for PITR.
Not exactly.
1. adjust acrhive_command to save wal's to backup dir
2. execute SELECT pg_start_backup('lable')
3. copy database files
4. execute SELECT pg_stop_backup()
Both the base backup and wal logs are stored in another disk.
>
> Since the wal logs keep increasing, do we take the base backup every now
> and then so that we can delete the old log files?
Yes, but do not delete old files until the new backup was successfully
finished.
How often do we take a base filesystem backup keeping in mind that our
> systems are 24 x 7.
It depends on your diskspace & load.
Any suggestions are appreciated.
Read the manual. It's pretty good & explains almost everything.
--
Vladimir Rusinov
Voronezh, Russia
UNIX Admin @ Murano Software
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: vladimir@greenmice.info, ssudhakar@internode.com.au
Subject: Re: WAL archiving
In-Reply-To: <f6fdfb550802212335q2579120ah5f521d12d49ae36b@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