Symptoms

Backup appears with exceptions. The Avamar Administrator User Interface (AUI) shows the Hyper‑V backup status as Completed with Exceptions. Log entries indicating GUID mismatch avhypervvss Warning <43708>: GUID '11111-AAAA-2222-3333-444444' for target 'TESTVM' not matching with any available target(s) on the host(s) avhypervvss Warning <43709>: Target virtual machine 'TESTVM<11111-AAAA-2222-BB33-444444>' is not matching to any available targets. Please check GUID and Target name against available targets on the host(s) Skipping from backup. avhypervvss Warning <41605>: The following Virtual Machines have failed: avhypervvss Warning <41604>: [1] TESTVM<11111-AAAA-2222-BB33-444444>

Cause

GUID Mismatch When Backing Up Hyper‑V Virtual Machines The backup process reports a GUID mismatch when the identifier stored in the Avamar dataset does not correspond to the current GUID of the VM on the Hyper‑V host. The dataset retains the original VM GUID (VMID) that was captured when the VM was first added to the backup set.If the VM is re‑created, restored from a template, or its GUID is manually altered, the VM receives a new GUID.During backup, Avamar compares the stored GUID with the GUIDs of available VMs on the host. When they differ, the following warnings are generated: avhypervvss Warning <43708>: GUID '11111-AAAA-2222-3333-444444' for target 'TESTVM' not matching with any available target(s) on the host(s) avhypervvss Warning <43709>: Target virtual machine 'TESTVM<11111-AAAA-2222-BB33-444444>' is not matching to any available targets. Please check GUID and Target name against available targets on the host(s) Skipping from backup. avhypervvss Warning <41605>: The following Virtual Machines have failed: avhypervvss Warning <41604>: [1] TESTVM<11111-AAAA-2222-BB33-444444> Root cause: The stored GUID in the dataset no longer matches any VM on the host because the VM’s GUID changed after the dataset was created.

Resolution

Update the dataset to correct the VM GUID mismatch. Edit the Source Data tab in the dataset. Remove the failed VMBrowse and select that same VM back into the dataset.

Support Cases