When a backup of an individual VM is complete the VMotion lock is not removed until the whole backup session completes. This can be a serious problem on larger VMware backups containing hundreds of VMs where large amount of VMs can't be moved to different ESXi hosts for a long time.
A similar issue exist for VMotion lock and VMware Snapshot in VMware backups using HPE Recovery Manager Central (RMC). The VMotion lock and VMware snapshot is not removed until the whole backup session completes. This makes no sense since the VMware snapshot is only required for a short period of time until the 3PAR snapshot is created.
Existing Enhancement Requests:
QCCR2A75749 / Remove snapshot and unlock VMotion after snapshot set creation
QCCR2A59888 / Change the behaviour of Data Protector VMware backups about locking with VMotion
It is not necessary to lock the VM after the backup has been completed. Removing the lock early allows management actions such as VMotion while other VMs in the same job are still backed up.
For the RMC issue removing the VMware snapshot early reduces the load during snapshot consolidation on the primary storage and is therefore considered an optimal approach offering real value over a traditional VEPA backup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.