> From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org] > On Behalf Of Steve VanDevender > > Database systems still often seem to have this problem, though, and > doing filesystem-level backups of systems with running databases will > often get inconsistent database state.
You definitely *can't* do filesystem-level backups including databases, and expect the databases to be ok. This is because the db daemons keep the file open, and you never know precisely when it's being updated. Block level snapshots of the underlying device, provided that the db is ACID compliant, don't result in db corruption - but of course, changes after the snapshot aren't included in the snapshot. Even if you have snapshots, it's smart to do filesystem-level or other more granular backups (database backups) in addition to the snapshots - because sometimes you don't want to rollback the whole machine. You just want to restore the database, or whatever. _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
