My Sys Admin installed Veeam Agent on the target Linux/MySQL server. I had to create a veeam account in the MySQL database to allow him to log into the MySQL instance. The Veeam for Linux application logged into the MySQL server, flushed and locked the MyISAM tables, took the snapshot, and then unlocked the MyISAM tables. However, Veeam for Linux did not touch the InnoDB tables (the newer standard). Does anyone know if the InnoDB tables need to be flushed before taking a backup snapshot or not. Veeam backup snapshots each logical volume when doing a full VM server backup to include the logical volume that contains the data directory (/var/lib/mysql). I am wondering if I now have a consistent backup or not in regard to the InnoDB tables.
My Sys Admin installed Veeam Agent on the target Linux/MySQL server. I had to create a veeam account in the MySQL database to allow him to log into the MySQL instance. The Veeam for Linux application logged into the MySQL server, flushed and locked the MyISAM tables, took the snapshot, and then unlocked the MyISAM tables. However, Veeam for Linux did not touch the InnoDB tables (the newer standard). Does anyone know if the InnoDB tables need to be flushed before taking a backup snapshot or not. Veeam backup snapshots each logical volume when doing a full VM server backup to include the logical volume that contains the data directory (/var/lib/mysql). I am wondering if I now have a consistent backup or not in regard to the InnoDB tables.
Interesting to see the Linux window showing MySQL. Looks like as you mentioned scripts are the way.
My Sys Admin installed Veeam Agent on the target Linux/MySQL server. I had to create a veeam account in the MySQL database to allow him to log into the MySQL instance. The Veeam for Linux application logged into the MySQL server, flushed and locked the MyISAM tables, took the snapshot, and then unlocked the MyISAM tables. However, Veeam for Linux did not touch the InnoDB tables (the newer standard). Does anyone know if the InnoDB tables need to be flushed before taking a backup snapshot or not. Veeam backup snapshots each logical volume when doing a full VM server backup to include the logical volume that contains the data directory (/var/lib/mysql). I am wondering if I now have a consistent backup or not in regard to the InnoDB tables.
ShaneFurlongwrote:
My Sys Admin installed Veeam Agent on the target Linux/MySQL server. I had to create a veeam account in the MySQL database to allow him to log into the MySQL instance. The Veeam for Linux application logged into the MySQL server, flushed and locked the MyISAM tables, took the snapshot, and then unlocked the MyISAM tables. However, Veeam for Linux did not touch the InnoDB tables (the newer standard). Does anyone know if the InnoDB tables need to be flushed before taking a backup snapshot or not. Veeam backup snapshots each logical volume when doing a full VM server backup to include the logical volume that contains the data directory (/var/lib/mysql). I am wondering if I now have a consistent backup or not in regard to the InnoDB tables.