> The issue with backing up a database live comes in when the filesystem > where the database and transaction log files are DIFFERS. You can get > into a pathological case in that instance. > > If the transaction log and database itself are both on the same > snapshotted entity (that is, the snapshot is pulled at the same instant > in time for both) what you get BETTER be restorable or your database's > transaction log facility doesn't really do what it promises to do!
Absolutely. Doing things like snapshot based backups of databases assumes you know what you're doing since it is not something which is documented as an official procedure in your typical database administrator guide. Personally, while I would use such schemes, I would always use a plain fully supported regular dump as a fallback position. I would only rely on snapshot based processes to do fancy stuff (such as near-realtime hot standby with zfs snaps + serialized incrementals). -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schul...@infidyne.com>' Key retrieval: Send an E-Mail to getpgp...@scode.org E-Mail: peter.schul...@infidyne.com Web: http://www.scode.org
pgpwtMtbjdvab.pgp
Description: PGP signature
