Re: Backup/disaster recovery and bandwidth (long)
От | Scott Ribe |
---|---|
Тема | Re: Backup/disaster recovery and bandwidth (long) |
Дата | |
Msg-id | 8D77E0D1-4AA7-4892-9508-58B7F21DDB18@elevated-dev.com обсуждение исходный текст |
Ответ на | Backup/disaster recovery and bandwidth (long) (Scott Whitney <scott@journyx.com>) |
Ответы |
Re: Backup/disaster recovery and bandwidth (long)
|
Список | 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 по дате отправления: