On Mar 26, 2010, at 1:32 PM, Greg Smith wrote:
> Bryan Murphy wrote:
>> The one thing you should be aware of is that when you fail over, your spare
>> has no spares. I have not found a way around this problem yet. So, when
>> you fail over, there is a window where you have no backups while you're
>> building the new spares. This can be pretty nerve wracking if your database
>> is like ours and it takes 3-6 hours to bring a new spare online from scratch.
>
> If there's another server around, you can have your archive_command on the
> master ship to two systems, then use the second one as a way to jump-start
> this whole process. After fail-over, just start shipping from the new
> primary to that 3rd server, now the replacement standby, and sync any files
> it doesn't have. Then switch it into recovery. Much faster than doing a new
> base backup from the standby on larger systems.
How is it possible to use the archive_command to ship to different ones?
archive_command = 'rsync -a %p
postg...@192.168.x.x:/usr/local/pgsql/walfiles/%f </dev/null'
archive_timeout = 120 # force a logfile segment switch after this
I suppose you can put multiple commands there then?
Also, 2 minutes - is this reasonable for a heavy write database?
Thank you
Ogden
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
