On Tue, May 29, 2007 at 02:06:04PM -0400, Jeffrey Trimble wrote: > I'm attempting to revisit this nasty process. I'm testing again to > see if I can ever get this to work to have a suitable way for a > migration path for new versions of Postgresql. I was able to backup my > data using: > > pg_dump -Fc dspace > /dspace/backup
This produces a "custom archive" dump, "suitable for input into pg_restore". > Then I recreated the database, per Postgresql's instruction for a new > database (as if it was a new installation) > > Then following the instructions: > > psql dspace < /dspace/backup For this to work, /dspace/backup would need to be the output of 'pg_dump -Fp'. You should be able to restore this dump using something like 'pg_restore -d dspace /dspace/backup'. 'man pg_restore' and read carefully to see what other options you may need. In particular read about how pg_restore handles ownership of database objects. Please take my PG suggestions only with a grain of salt. I don't do this stuff often enough to really learn it. FWIW here's a sample from crontab on one of my production DSpace hosts, showing how I do the nightly database dump: 00 02 * * * /usr/bin/pg_dump -Ft -U tomcat -b dspace | gzip -9 > /opt/dspace/db.tar.gz (A system backup job comes along later and copies the dump to tape.) -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpxChsuACnPT.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
