Hi,
Thanks for the quick response.
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!
Please note that this happened to me (and I tested again) with
compress=yes. I refer to
-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:
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
3 matches
Mail list logo