Re: Backup/disaster recovery and bandwidth (long) - Mailing list pgsql-admin

From Scott Ribe
Subject Re: Backup/disaster recovery and bandwidth (long)
Date
Msg-id 8D77E0D1-4AA7-4892-9508-58B7F21DDB18@elevated-dev.com
Whole thread Raw
In response to Backup/disaster recovery and bandwidth (long)  (Scott Whitney <scott@journyx.com>)
Responses Re: Backup/disaster recovery and bandwidth (long)  (amador alvarez <aalvarez@d2.com>)
List pgsql-admin
On Apr 25, 2012, at 10:11 AM, Scott Whitney wrote:

> I believe, then, that when I restart server #3 (the standby who is replicating), he'll say "oh, geez, I was down, let
mecatch up on all that crap that happened while I was out of the loop," he'll replay the WAL files that were written
whilehe was down, and then he'll catch back up. 
>
> Does this sound like a viable option? Or does someone have additional suggestions?

Perfectly viable. However, the WAL files must exist for this to happen. So you need to set wal_keep_segments
appropriately,or set up WAL archiving. 

Note that you could even provide a more up-to-date database for your people to work with. If the testbed is nearly up
todate, then an rsync to update it would take very little time. So you could shut down the replica, rsync, and bring
thereplica back up. 


--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice





pgsql-admin by date:

Previous
From: Scott Whitney
Date:
Subject: Re: Backup/disaster recovery and bandwidth (long)
Next
From: Steve Crawford
Date:
Subject: Re: Backup/disaster recovery and bandwidth (long)