NovaBACKUP BE v19.x and newer
You back up various HyperV VMs using Virtual Dashboard (VD).
The backup of one VM fails, but all other VMs are saved.
Check the Windows Event Viewer for the HyperV role on the HyperV host.
Open Windows Event Viewer.
Browse to the HyperV VMMS event log:
"Applications and Services Logs" => "Microsoft" => Windows" => "Hyper-V-VMMS" => "Admin"
"Applications and Services Logs" => "Microsoft" => "Windows" => "Hyper-V-VMMS" => "Storage"
These event displays only exist on a server with an installed HyperV role.
In most cases, they indicate that the HyperV Manager cannot provide a checkpoint for this VM that is not to be backed up. The reason for this is usually to be found within the affected VM. The shadow copy function must also run cleanly within the VM. There may not be enough storage space available within the VM for shadow copies, or other processes within the VM prevent the creation of a shadow copy (= checkpoint).
Without a checkpoint, NovaBACKUP cannot back up a VM.
Please fix the cause of the VSS malfunction.
You can also send these event notifications to NovaStor support by email to firstname.lastname@example.org
Save these Windows event reports by right clicking on them:
Right mouse click on event log => "Save all events as...". => Assign name "HyperVAdmin" or "HyperVStorage", select format ".evtx" => Display information for these languages, select German.
The shadow copies must function correctly on the Hyper-V host AND within the affected VM. Please check the Windows event logs "Application" and "System" on the Hyper-V host AND within the VM for error messages regarding the shadow copies (source: VSS). If necessary, correct the cause of these error messages.
Also check whether HyperV Integration Tools or VMware Tools are installed and up to date.