From: | Stuart Luppescu <slu(at)ccsr(dot)uchicago(dot)edu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Dump and restore problem |
Date: | 2008-06-18 21:41:07 |
Message-ID: | 1213825267.16234.31.camel@musuko.uchicago.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello, I had a very nice system where I mirrored everything to another
machine each night, so in case of disaster, I could easily switch over
to the mirror.
The backup script uses a line like this:
pg_dump -b -F t -h $postgresql_hostname $i > "$location_backup_dir/`date
+%B-%Y`/$date_info/postgresql_database-$i-backup"
I transfer the backup files by rsync and then run this on the mirror:
pg_restore -c -U dbuser -d dbname -F t postgresql_database-db-backup
This worked fine for months until I upgraded postgres on the main
machine from 8.0.13 to 8.0.15. From then on I started getting these
messages:
pg_restore: [tar archiver] could not open TOC file for input: No such
file or directory
The funny thing is that this started when I upgraded postgres on the
main main machine a little over a week ago, but I had already upgraded
from 8.0.13 to 8.0.15 on the mirror machine back in January (and the
error happens when I try to restore the backup on the mirror).
If anyone can help, I would be very appreciative.
--
Stuart Luppescu -=- slu .at. ccsr.uchicago.edu
University of Chicago -=- CCSR
才文と智奈美の父 -=- Kernel 2.6.24-gentoo-r8
Is knowledge knowable? If not, how do we know
that?
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Clark | 2008-06-18 21:50:11 | Re: renumber table |
Previous Message | Jeff Davis | 2008-06-18 21:36:42 | Re: Database design: Temporal databases |