Hello everyone,
We ran into a problem yesterday. My colleague was live migrating one of our virtual machines from one host to another (2 physical hosts with both using local ZFS based storage). Without thinking about disabling the backup (using Veeam Backup & Replication) my colleague just started the migration. Unfortunately the backup started while the virtual machine was being migrated. To my surprise we did not receive any error message in Veeam Backup & Replication, but the live migration failed and the virtual machine crashed and was no longer reachable. We tried shutting down the virtual machine and powering it off, but neither of the options was working. Eventually I checked Veeam and noticed that it was just hanging on the job, not showing any error message or progress information or whatsoever. After I cancelled the backup, the virtual machine was still not responding at all, but I was able to forcefully shut it down and start it again. The virtual machine worked just fine after.
I know this is probably not the best case and the backup should've been disabled, but perhaps it's a good idea to add better error handling if something like this occurs and just cancel or pause the action or lock the virtual machine from changes being made, instead of receiving a hard crash?
The error message we received can be seen in the screenshot below. After we restarted the migration everything finished successfully without any problems.
We ran into a problem yesterday. My colleague was live migrating one of our virtual machines from one host to another (2 physical hosts with both using local ZFS based storage). Without thinking about disabling the backup (using Veeam Backup & Replication) my colleague just started the migration. Unfortunately the backup started while the virtual machine was being migrated. To my surprise we did not receive any error message in Veeam Backup & Replication, but the live migration failed and the virtual machine crashed and was no longer reachable. We tried shutting down the virtual machine and powering it off, but neither of the options was working. Eventually I checked Veeam and noticed that it was just hanging on the job, not showing any error message or progress information or whatsoever. After I cancelled the backup, the virtual machine was still not responding at all, but I was able to forcefully shut it down and start it again. The virtual machine worked just fine after.
I know this is probably not the best case and the backup should've been disabled, but perhaps it's a good idea to add better error handling if something like this occurs and just cancel or pause the action or lock the virtual machine from changes being made, instead of receiving a hard crash?
The error message we received can be seen in the screenshot below. After we restarted the migration everything finished successfully without any problems.