[BETA] [HPE] VeeamCheckpoints persisting after backup job

[grberg]

Hello

Noticing that after a backup job completes successfully, the checkpoints don't get cleared on VME hosts and it is causing issues with vm migrations afterwards

current hypervisor vers: HPE VM essentials 8.0.12, did not notice if the issue was present in 8.0.11 as well

[cody.ault]

We leave a checkpoint on the virtual machines for dirty bitmap/changed block tracking purposes. You can delete the checkpoint, if necessary but your next job run might require a full scan of the virtual disks. Can you explain which type of migrations are affected and what type of storage you're using?

[grberg]

using GFS2 datastores, when i force a node failure scenario by forceful shutdown, the VM's get restarted on working nodes. However, the VM definition stays on the failed node once it is recovered, and VM reconfigure was unavailable and VM move seemed to fail after node recovery.

Initial workaround was to delete the checkpoint manually on the host that failed

I am suspecting it is due to the checkpoints being present because other VM's that have not been backed up by veeam did not display any of these issues

[EvgenyBaev]

Hello, grberg,

Would it be possible for you to provide the Morpheus logs covering the period when the issue occurred? You can find them on the Morpheus manager in the /var/log/morpheus/morpheus-ui directory.

Additionally, could you please let me know if the issue also occurs when using the "Manage Placement" feature for your VM? Or only in a node failure scenario.

In the meantime, I’ll attempt to reproduce the issue in our lab environment.