We are using two slaves this way:
- Active server moves WAL files to local directory,
doesn't care about slaves
(basically archive_command = 'mv %p /some/arch_dir/%f')
- Slaves pull WAL files via rsync
- Slaves also do full syncs every several hours (pg_start_backup / rsync /
pg_stop_backup)
-
We currently have a PITR solution in place that is facilitated via WAL
shipment. This is implemented on 13 databases, where the two primary
machines which contain the production databases and the PITR machine are
physically located in the same facility.
We now want to add a second PITR
Geoffrey wrote:
We currently have a PITR solution in place that is facilitated via WAL
shipment. This is implemented on 13 databases, where the two primary
machines which contain the production databases and the PITR machine are
physically located in the same facility.
We now want to add a
Geoffrey wrote:
Geoffrey wrote:
We currently have a PITR solution in place that is facilitated via WAL
shipment. This is implemented on 13 databases, where the two primary
machines which contain the production databases and the PITR machine
are physically located in the same facility.
We
On Sat, Nov 07, 2009 at 08:10:23AM -0500, Geoffrey wrote:
We now want to add a second PITR machine that is in a remote location.
The question is, what is the best solution for such an effort? We've
considered shipping the wal files to both locations, but the concern is
that if one fails,
