On Tue, Aug 27, 2013 at 6:53 PM, Thomas Ronayne <ronayne.tho...@gmail.com> wrote: > doing the same with /var/lib/pgsql -- files are just files after all else is > said and done, eh? Stop PostgreSQL on both servers, do the rsync and restart > the DBMS on both. Maybe stop Tomcat, too, but that might be overkill.
Oh, no, completely unnecessary downtime. Just do pg_dump on a running database and you'll have one nice sql file instead of database files specific to a particular postgres version. More importantly, as you noticed, you'd have to worry about hot backup - but why go through all that trouble? There is one theoretical issue - there might be an item submitted to DSpace between pg_dump finishes and rsync finishes (or vice versa), which would mean you backed up the database with the item record, but not its bitstream (or vice versa). It would affect only this item, the rest would work perfectly fine. In practice, the backup process will be a nightly cronjob that will finish pretty fast, so I wouldn't worry about it at all. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
