[Bacula-users] correct strategy for mysql innodb and myisam backup
2017-01-11 16:59:04
i have been using the script at [1] but then i noticed that the
incremental backups were quite large and containing some MYD and MYI
files. so i realized these were myisam databases. i read that the best
way to backup both innodb and myisam databases was to use the mysqldump
option --lock-tables instead of --single-transaction, which is what the
script[1] is using.
therefore, i was thinking i'd update the script to use --lock-tables,
and also adjust my bacula settings so it is only backing up the output
from mysqldump and the binlog directory.
so i just wanted to check in to see if that would cover everything? or
am i missing things?
Thanks
1.
http://wiki.bacula.org/doku.php?id=application_specific_backups:mysql#using_binary_logs
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Bacula-users] correct strategy for mysql innodb and myisam backup,
scar <=
|
|
|