On Fri, Mar 26, 2010 at 1:02 PM, Michael Mueskens <[email protected]> wrote: > 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.
Or, if you're using postgres, use ampgsql. http://code.v.igoro.us/archives/50-Whats-New-in-Amanda-Postgres-Backups.html > I do see DLEs like /var/lib/mysql in my backups anyway (not added by me), so > that _is_ a problem nevertheless. That was my point - if these warnings were ignored by default, then a newbie could potentially think his backups are complete when they are not. > 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. Jean-Louis' suggestion is a good one for this case. > 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 :) I had forgotten that ampgsql makes this easily configurable already, using the STRANGE and IGNORE regexes that Jean-Louis pointed to. Dustin -- Open Source Storage Engineer http://www.zmanda.com
