-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dustin J. Mitchell schrieb: > Amdump's exit statuses are here, by the way: > http://wiki.zmanda.com/man/amdump.8.html > > We've kept the strange messages as a distinct error because they *can* > represent data loss. For example, if your accounts_receivable.db is > marked as STRANGE in every backup since the dawn of time, then you > don't actually have a backup of your accounts receivable! In general, > the right way to make spurious "file changed as we read it" errors go > away is exclude lists.
Well ok, we don't have to talk about backing up running databases, the best way in my opinion to do a db-backup is to dump the databases (e.g. mysqldump) and then backup these dumps via amanda. I do see DLEs like /var/lib/mysql in my backups anyway (not added by me), so that _is_ a problem nevertheless. The other problem I see are logfiles, and those I'd like to be able to backup (in a non-total-consistent way, I agree) with no error_output. > > Michael, Amanda-3.1 has a much simpler implementation of amreport, so > it wouldn't be too difficult to hack it to ignore STRANGE messages. > I'm not sure I'd want to merge such a hack, but I'm open to > persuasion! > I don't want to persuade you to anything :), but maybe it could be possible (via amanda.conf or in dumptype-definition) to configure it in runtime, so that one could differentiate between "wanted" and suspicious file changes? I don't know how difficult that is to implement, though, but I'd be happy to discuss this further :) Michael - -- Michael Müskens Rule #18: It's better to seek forgiveness than ask permission. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkus9scACgkQWjIj1fb8pFs1rgCgvCFMnX5pkuSsnlgFcn1lkDJP kysAnRabYoJezXDx4G9mA20uj50uIQbL =lmfx -----END PGP SIGNATURE-----
