Avamar Plug-in for Hyper-V VSS : Hyper-V backups failing with “avtar Error : Specified source path does not exist”

Article Number: 501887 Article Version: 4 Article Type: Break Fix



Avamar Plug-in for Hyper-V VSS

Hyper-V backups may fail with errors similar to the following:

avhypervvss Error <13117>: Unable to successfully process backup workorder MOD-1490821241871#101, targets

\?Volume{abcd-1234-xxxx-xxxx-xxxxxxx}dellemcVirtual Machines12345-abcd-6789-efgh-XXXX.xml

avhypervvss Error <17120>: Failed to process federated backup workorder.

avhypervvss Error <0000>: Federated backup did not complete successfully.

_________________________________________________________________________________________________

avtar Error <7553>: Specified source path “?Volume{abcd-1234-xxxx-xxxx-xxxxxxx}dellemcVirtual Machines12345-abcd-6789-efgh-XXXX.xml” does not exist; ignored

avtar Error <7553>: Specified source path “?Volume{abcd-1234-xxxx-xxxx-xxxxxxx}dellemc}Virtual Hard DisksAvamar-vm.vhdx” does not exist; ignored

avtar Error <7553>: Specified source path “?Volume{abcd-1234-xxxx-xxxx-xxxxxxx}dellemcVirtual Hard DisksAvamar-vm-AutoRecovery.avhdx” does not exist; ignored



avtar Error <8012>: Error in path list: All paths are invalid.. Correct path list before retrying.

VMs are configured with Volume GUID instead of drive letter. This can be confirmed either via PowerShell or from the Properties page of the VM in Hyper-V Manager.

Example:

\?Volume{abcd-1234-xxxx-xxxx-xxxxxxx}dellemcVirtual Machines

The Hyper-V VSS plug-in does not support mountvol GUID paths for VM configuration. Reason being that restores would fail if the same GUID is not found (i.e. drives are replaced).

Fix the VM configuration paths to point to a drive letter, i.e. L:Virtual Machines or G:Virtual Machines.

Related:

  • No Related Posts

Leave a Reply