Case # 02035663
We are making backups of MySQL database, previously we didn't added any pre-freeze/post-thaw scripts, but we noticed during a crash, you are not guaranteed to have a consistent MySQL "backup".
This way we wanted to implement pre-freeze and post-thaw scripts.
For MySQL replication, we just stop the MySQL service before the snapshot and start it again after.
But for the master database, we just want to "lock the tables". We've followed the below blog ( https://www.virtuallifestyle.nl/2013/03/back-up-mysql-on-linux-without-stopping-services-or-dumping-the-database/
) and I must say, the scripts are working perfect.
Only we have one side note that we get "Timed out waiting for pre-freeze script to finish execution" in Veeam, even when I clearly configure an exit code.
We've opened a cased, and they informed us to increase the time-out, but I'm sure this is not the issue, as the script only takes 5-10 seconds.
So the backup is like this:
* Start pre-freeze event /Start Script A
* Script A starts a new script in the background script B
* Script A is finished withing 5-10 seconds.
* Script A sends "exit 0"
* VM Snapshot *Start Post-Thaw script
* This will stop Script B (exit 0) What Script B actually does, is keep a lock on the mysql databases, until the vm snapshot has been taken, to have a consistent mysql database backup. So actually the pre-freeze event should stop after the exit of script A.
The script runs, and locks the tables, but seems Veeam doesn't see the exit code? Or is it waiting on the background script (Script B).
I just want to check if any of you experienced the same, but doesn't need to be linked to mysql.
If you need more info just let me know.