NetWorker Module for Microsoft Hyper-v Standalone Virtual Machine Restore Fails

 In a standalone Hyper-V setup:

Restore Virtual Machine from one hyper-V server to another failed with the following error:

nsrnmmrc: 06/23/25 19:03:29.986376 nsrnmmrc-D3 expand_registry_path: input G:\VM_NAME\VM_NAME-VHHDX_ID-DISKNAME.vhdx
127955 23/06/2025 19:03:29 Failed to create directory G:\VM_NAME: No such file or directory
0 23/06/2025 19:03:29 Failed to create destination path for ' G:\VM_NAME\VM_NAME-VHHDX_ID-DISKNAME.vhdx'

nsrnmmrc: 06/23/25 19:03:30.075410 nsrnmmrc-D3 Successfully closed the recover session.
0 23/06/2025 19:03:30 Failed to complete BBB restore with error Failed to create destination path for ' G:\VM_NAME\VM_NAME-VHHDX_ID-DISKNAME.vhdx'


175686 23/06/2025 19:03:32 Restore failed with the error: Failed to complete BBB restore.
0 23/06/2025 19:03:32 Post restore files - nothing to do.
177924 23/06/2025 19:03:32 Fatal error during restoring files for Virtual Machine VS605 with savetime -- <SaveTime>.
71234 23/06/2025 19:03:37 **************************************************************


71238 23/06/2025 19:03:37 Recover completion status
50247 23/06/2025 19:03:37 Unable to restore files for VS605 with error: Failed to complete BBB restore. and error code: 0x80004005.

56473 23/06/2025 19:03:37 **************************************************************

From the NetWorker Module for Microsoft User Interface monitor tab, it shows the settings selected from the restore;

The Virtual Machine disk is added twice for the same disk.

Hyper-V virtual machine recovery options:
          Source Hyper-V Server:<Source Hyper-V Server name>
          Destination Hyper-V Server: <Destination Hyper-V Server name>
          Destination path for the Hyper-V virtual machine configuration files: <Recovery directory>
          Destination path for the virtual machine:
               VM_NAME, G:\VM_NAME\VM_NAME-VHHDX_ID-DISKNAME.vhdx = < Recovery Directory>
                VM_NAME, G:\VM_NAME\VM_NAME-VHHDX_ID-DISKNAME.vhdx = < Recovery Directory>
          Host, on which the recovery process is run: <Destination Hyper-V Server name>

This only occurs for Standalone Hyper-v Virtual Machine restore from incremental backups:

Restore of Standalone Hyper-v Virtual Machine from Full backups works fine.

Restore of Hyper-v Cluster Virtual Machines works fine.

 In a standalone Hyper-V setup:

For full backup, it shows only one vhdx entry per disk and restores from one hyper-V server to another works fine.

For incremental backup, duplicate vhdxs entries for each disk are seen, and restore from one hyper-V server to another fails. 

Checking client index using the following command:

nsrinfo -vvv -n all <Hyper-v Server Name> > c:\nsrinfo.txt

The output for the incremental backup shows the duplicate entries:

  
VSS file
  Entry type: 8
  Usage type: 0
  Flags: 0
  Component name: ABC....
  Saveset name: APPLICATIONS:\Microsoft Hyper-V\VMNAME\<VHDX_ID>
  Cover savetimes: <savetime>
  Backup Level: full
  Application Attributes: 
    *NSR_BACKUP_GENERATIONID: 1751568752;
                  ListOfVHDs: "VMNAME.vhdx,";
              NSR_RCT_BACKUP: TRUE;
           NSR_SAVESET_COUNT: 1;
           NSR_SAVESET_INDEX: 0;
      NSR_SNAPSHOT_SESSIONID: 
da_dirl->G:\VMNAME\VMNAME\Virtual Hard Disks\VMNAME.vhdx
da_dirl->G:\VMNAME\VMNAME\Virtual Hard Disks\VMNAME.vhdx
WIN ASDF v2 file `APPLICATIONS:\Microsoft Hyper-V\VMNAME\', NSR size=xxx, date=<savetime> <backup_time>, file size=0

It is a known issue and fix merged to 19.11.0.4 and 19.12.0.1. or later versions.