|
That is what I have been working from. There is nothing in my pg_xlog file. What I showed you is what was in the one that I saved before trying the recovery.
When I did not copy 00000001000000000000004C to
/postgresql/archive/GRIZZ, it had told me that the file was missing and recovery had failed. So I copied it and then it tells me that it is not the right size. From: Denish Patel [mailto:denish@xxxxxxxxxx]
For the reference here are the steps ... On Wed, Oct 23, 2013 at 4:44 PM, Denish Patel <denish@xxxxxxxxxx> wrote: I don't think you need to move anything out of pg_xlog to WAL archive Directory. You should remove all files from pg_xlogs directory on recovery database server too (i.e Run rm pg_xlog/* ) Please remove the 00000001000000000000004C from WAL archive directory, remove all files from pg_xlogs on recovery database and try to startup
database ? On Wed, Oct 23, 2013 at 4:35 PM, Ginepro, Raymond C <GineproR@xxxxxxxxx> wrote: Quick summary of what I did and the archive file: I shut down postgres via pg_ctl stop I renamed the existing data directory I created a new directory for the restore with the old name Unzipped and untarred the base.tar.gz file In the pg_xlog, of the renamed data directory, there is the following:
postgres@xpostgw2d:/postgresql/data/GRIZZ??/pg_xlog>ls -ltr
total 16432
-rw------- 1 postgres vfabric 305 Oct 9 14:56 00000001000000000000002B.000
00020.backup
-rw------- 1 postgres vfabric 56 Oct 9 15:01 00000002.history
-rw------- 1 postgres vfabric 8192 Oct 9 15:01 xlogtemp.3402
-rw------- 1 postgres vfabric 8192 Oct 9 15:29 RECOVERYXLOG
-rw------- 1 postgres vfabric 8192 Oct 21 14:22 00000001000000000000004F
-rw------- 1 postgres vfabric 305 Oct 21 14:22 00000001000000000000004C.000
00020.backup
-rw------- 1 postgres vfabric 16777216 Oct 21 14:30 00000001000000000000004D
-rw------- 1 postgres vfabric 8192 Oct 21 14:30 00000001000000000000004E drwx------ 2 postgres vfabric 4096 Oct 21 14:30 archive_status
I copied the 00000001000000000000004C.00000020.backup file to 00000001000000000000004C in the archive directory /postgresql/archive/GRIZZ.
The recovery.conf file has the following param:
restore_command = 'cp /postgresql/archive/GRIZZ/%f "%p"'
From: Denish Patel [mailto:denish@xxxxxxxxxx]
Thanks. Backup looks good. How's your recovery.conf look like? Can you provide 'ls -l' on archive file "00000001000000000000004C" from
your WAL directory? On Wed, Oct 23, 2013 at 3:14 PM, Ginepro, Raymond C <GineproR@xxxxxxxxx> wrote: I have created a script to run the pg_basebackup utility. The options it uses are: pg_basebackup -D $BACKUP_DIR/$TIMEINFO -F t -z -Z 9 –x where $BACKUP_DIR is set to our backup directory and $TIMEINFO is set to TIMEINFO=`date +%Y%m%d_%H%M%S`. The backup looks ok when I unzip it and untar it. As it is being created, it switches to the next WAL file and the first
one is way small. From: Denish Patel [mailto:denish@xxxxxxxxxx]
Before going into recovery discussion, I would like to learn about how did you take a backup ? Have you followed "Making A Base Backup" procedure documented in http://www.postgresql.org/docs/9.2/static/continuous-archiving.html
? On Wed, Oct 23, 2013 at 2:56 PM, Ginepro, Raymond C <GineproR@xxxxxxxxx> wrote: Good afternoon,
--
--
Denish Patel,
-- Denish Patel,
-- Denish Patel, |
