On Mon, Jan 08, 2007 at 10:43:42AM +0000, Brian Candler wrote:
> Consider a database application - mysql or oracle or whatever. At some point
> in time, it decides to write some updates to tables 1, 2 and 3, and index
> files X, Y and Z.
[...]
> If you happen to take a snapshot of the filesystem at the point where some
> of these writes have been requested but others have not, then the image you
> restore will be in an inconsistent state.
If that is the case, your database application isn't worth the diskspace
it's occupying. (Assuming, of course, that the filesystem snapshot is
atomic.) A good database application is specifically designed to handle this,
and there are backup strategies which explicitly take advantage of this.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
