Operational Defect Database
BugZero found this defect 2098 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2709
Backing Up Hyper-V Guest Cluster Based on VHD Set
Last update date:
5/26/2022
Affected products:
Veeam Backup & Replication
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
VHD Set is a new shared Virtual Disk model for guest clusters in Windows Server 2016. VHD Set files can be included in application-consistent checkpoints and backed up, but there are some limitations.
Cause
Please make sure the following requirements are met: Each guest VM should have the cluster feature installed. All members of the guest cluster should be online. VHD Set shouldn't be used as Cluster Shared Volume (CSV) The folder on CSV containing VHD Set files should have sufficient permissions. Note: See how to configure missing permission in the Event 19100 section below. The guest operating system should be Windows 2016 or later. All VHD Set files must reside on CSV or SMB shares. Microsoft supports legacy shared VHDX on Windows 2016, but this feature cannot be used as a workaround because it cannot be included in application-consistent checkpoints, therefore, Veeam doesn't support backup of such disks on Windows Server 2016. If your VMs reside on a CSV, ensure the ConfigStoreRootPath cluster parameter is defined. Otherwise, the backup job might fail on checkpoint creation with one of the errors listed below.
Solution
Error code: 32768 - Failed to create checkpoint on collection 'Hyper-V Collection' This issue occurs because Windows can't query the cluster service inside the guest VM. To fix this issue, ensure that the cluster feature is installed on all guest VMs and the cluster service is running. Error code: 32770 - Active-active access is not supported for the shared VHDX in VM group This issue occurs because the VHDS disk is used as a Cluster Shared Volume (CSV), which cannot be used for creating checkpoints. To fix this issue, you need to use each disk as a shared disk instead of a Cluster Shared Volume. You can do this by using the "Remove from Cluster Shared Volume" option in the cluster manager GUI. Error code: 32775 - More than one VM claimed to be the owner of shared VHDX in VM group 'Hyper-V Collection' This issue occurs because the shared drive was offline in the guest cluster. To fix this issue, make sure that all shared drives in the cluster that are part of the backup are online. Error Event 19100 - Hyper-V-VMMS 19100 'BackupVM' background disk merge failed to complete: General access denied error (0x80070005) This issue occurs because of a permission issue. To fix this issue, the folder that holds the VHDS files and their snapshot files must be modified to give the VMMS process additional permissions. To do this, follow these steps: Determine the GUIDS of all VMs that use the folder. To do this, start PowerShell as administrator, and then run the following command:
More Information
Related Articles: Veeam KB2194: ConfigStoreRootPath Cluster Parameter Is Not Defined
