KB ID : 115120
Products :
Published : Dec. 11, 2019
Created : Dec. 11, 2019
Last Modified : Dec. 11, 2019

Cause:

This issue might occur if the VM is not in a valid state during the backup process. It occurs due to the following reasons:

1) The cluster disk (in which the VM’s Virtual Hard Disk file located) is offline in the Cluster

2) The Scale-out FileServer role is in offline state

3) Checkpoint deletion for the VirtualMachine is taking more time

Solution:

1) Connect to cluster through FailOver Cluster Manager in any of the cluster node and check the cluster disk status (connect to cluster ->Storage -> Disks ->respective Cluster Disk ), if it is not online, change it to online and run the backup job again.

2) If the VM’s disk is located in scale-out FileServer cluster then, connect to Cluster through FailOver Cluster Manager in any cluster node and check the SOFS role state(connect to cluster ->Roles -> respective SOFS role), if it is not online, change it to online and run the backup job again.

3) Go to Hyper-V Manager and check if the checkpoint deletion is in progress for the VirtualMachine, wait until it completes and run the backup job again.

Note:If the issue still persists, contact Vembu support at vembu-support@vembu.com

edit retag flag offensive close merge delete