On 1/4/08, Michel Meyers <[EMAIL PROTECTED]> wrote: > > - I will need to stop mysql slave before and restart it after backup. I > > read the documentation but something is still not clear for me. Can I > > execute a "script on client before" and a "script on client after" and > > start the backup only "if success"? Or it's better to use a script on > > director that remotely stops the db engine? > > You can use both. It also depends on how you back up your MySQL > databases. If you just grab MySQL's files from its data directories, you > have to shut it down. Alternatively, you could dump the databases (using > mysqldump) and then back up those db dumps. The advantage of the latter > is that restores are much easier and don't depend so much on your MySQL > version etc (ie if you changed MySQL versions since the backup was > taken, a restore might be very troublesome).
You should investigate: - using LVM to store your databases on - using mysqlhotcopy and innodb hot backup to drive the backups and then backing that up - or use zmanda + LVM to back up your data with bacula pulling the backups from your DB servers to your tape You can dump as well and I suggest doing regular dumps but on large databases with many indexes restoring can take a long long time (days) so not optimal. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
