On Nov 18, 2013, at 11:28 AM, Andres Freund <and...@2ndquadrant.com> wrote: > Could you detail how exactly the base backup was created? Including the > *exact* logic for copying?
0. Before any of this began, P1 was archiving WAL segments to AWS-S3. 1. pg_start_backup('', true) on P1. 2. Using rsync -av on P1, the entire $PGDATA directory was pushed from P1 to S2. 3. Once the rsync was complete, pg_stop_backup() on P1. 4. Create appropriate recovery.conf on S1. 5. Bring up PostgreSQL on S1. 6. PostgreSQL recovers normally (pulling WAL segments from WAL-E), and eventually connects to P1. > Do you have the log entries for the startup after the base backup? Sadly, not anymore. > This server is gone, right? Correct. > Could you list the *exact* steps you did to startup the cluster? 0. Before any of this began, P2 was archiving WAL segments to AWS-S3. 1. Initial (empty) data directory deleted on S2. 2. New data directory created with: /usr/lib/postgresql/9.3/bin/pg_basebackup --verbose --progress --xlog-method=stream --host=<ip> --user=repluser --pgdata=/data/9.3/main 3. Once the pg_basebackup completed, create appropriate recovery.conf on S1. 4. Bring up PostgreSQL on S2. 5. PostgreSQL recovers normally (pulling a small number of WAL segments from WAL-E), and eventually connects to P2. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers