On 12/23/21 11:19, Graham Dicker wrote:
Thank you for your reply Graham.
I don't think Bacula itself has any problems, it is only the script mysqldump
that has a problem. The script is just supposed to create a dump of the
database and (if it is successful) then Bacula goes on to first back it up and
then delete it.
I'm gonna be very blunt here. mysqldump is a piece of obsolete garbage
and nobody should be using it any more. It CANNOT, period, CORRECTLY
back up both My ISAM and InnoDB tables in the same dump. CANNOT.
(Nobody should be using the MyISAM storage engine any more either, but
that's another issue.)
Take a look at mydumper instead. It is better than mysqldump in almost
every imaginable way. It is parallelized, storage engine aware, and
immensely easier to do partial restores with (i.e a single schema or a
handful of tables). It is what mysqldump SHOULD have evolved into
fifteen years ago.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
