On Mon, Oct 15, 2007 at 05:09:02PM -0400, Ben Scott wrote: > > One is to have the database server do a dump/export/whatever to disk > file(s) before the backup runs, and then just backup those files. > Essentially a two-stage backup. Not sophisticated, but often > reliable.
This is what I do. It's slow and painful, but almost 100% reliable. My backup files are compressed raw SQL, so they can be greped, seded, perled, and restored anywhere. There's another option, if you have the right filesystem. You lock the database, take a filesystem level snapshot, unlock the DB, then back up the snapshot. That's supposed to work for Linux LVM2 and several of the commercial NAS/SAN offerings. On some systems you only need to lock the DB for a few seconds. -- Matt Brodeur RHCE [EMAIL PROTECTED] http://www.nexttime.com PGP ID: 2CFE18A3 / 9EBA 7F1E 42D1 7A43 5884 560C 73CF D615 2CFE 18A3 One difference between a man and a machine is that a machine is quiet when well oiled.
pgpWf6R0xdEmK.pgp
Description: PGP signature
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
