On Mon, Sep 28, 2015 at 8:48 AM, CS DBA <cs_dba@consistentstate.com> wrote:
> All;
>
> We have a 3 node replication setup:
>
> Master (node1) --> Cascading Replication Node (node2) --> Downstream
> Standby node (node3)
>
> We will be deploying WAL archiving from the master for PITR backups and
> we'll use the staged WAL files in the recovery.conf files in case the
> standbys need to revert to log shipping.
>
> Question: whats the best way to ensure consistency of WAL archiving in the
> case of changes (failover, etc)? can we setup the cascade node to archive
> wals only if it's the master? is this a case where we should deploy repmgr?
Look up WAL-E. It's works really well. We tried using OmniPITR and
it's buggy and doesn't seem to get fixed very quickly (if at all).
