-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
Joel Fuster wrote: > Package: backupninja > Version: 0.9.4-4 > Severity: critical > Justification: causes serious data loss > > > The mysql backup handler happily overwrites your existing sql.gz files with > empty tarballs even in situations such as: > > 1) mysqldump does not exist > 2) mysql is not running > > ...etc. This just bit me when #2 happened due to a crash in mysql which > involved corrupted data. Fortunately I have multiple snapshots of the > sql.gz files... > > It looks like this might only happen when you specify the names of the > databases you wish to back up. Also, I have only tested this using the > "mysqldump" method. This only occurs when you specify databases and you have compress=no, mysqld isn't running or mysqdump doesn't exist. This is a pretty unique combination of events! Backupninja is designed with the expectation that the backups that you are making of your databases are being backed up to another system or another disk using one of the handlers such as rdiff, duplicity, rsnap, dup, etc. It is expected that the mysqldumps that are made in your backup directory are not the end of the backup, but rather this are shipped off in the remainder of the process. Although I agree its a bad situation to be in to create a zero-byte mysql dump, I am hesitant to agree that this is causes serious data loss. Using that logic, you could claim that backupninja causes serious data loss when you delete everything from your database and then you do a backup of an empty database, or likewise. In any case, I don't like nasty backup surprises, so I've prepared a fix, and will ask the release managers to have this fix allowed into etch. Thanks, Micah -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFf5N09n4qXRzy1ioRAgBNAKCDxYYUoYa6yAhm+tIkaSfcWfo0IQCdFEuR ThX68NqpEqKfLWF63bBjhk8= =X1b+ -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
