NetWorker: nsrazure_recover fails "Target VM must already exist for a single disk recovery."

• The nsrazure_recover command is used to recover an Azure VM from NetWorker command-line: NetWorker: How to perform Azure VM Snapshot restore from Command-Line
• The recovery fails with the following error:

azure-nve:~ # nsrazure_recover -S 4154256312 -N 'Azure' -R 'NW-PERF' -A 'networkerstorageaccount' -V 'Test-VM' -E 'NW-PERF:vnet' -T 'subnet'
207830:nsrazure_recover: Response Code: 404 Response Data: {"error":{"code":"ResourceNotFound","message":"The Resource 'Microsoft.Compute/virtualMachines/Test-VM' under resource group 'NW-PERF' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"}}

207974:nsrazure_recover: Target VM must already exist for a single disk recovery.

The Save Set ID (SSID) specified in the nsrazure_recover command is for a DataDisk, not an OsDisk. The VM specified with -V VM_NAME is for a new VM, not an existing VM.

azure-nve:~ # mminfo -avot
volume        type   client           date     time         size ssid      fl   lvl name
….
azure_nve.local.dddefault.003 Data Domain azure-nve.local 08/13/25 15:47:03 31 GB 4171033528 cb full NW-PERF:azure-ubuntu:azure-ubuntu_OsDisk_1_cf93159d6205414baa8593901a918d3a
azure_nve.local.dddefault.003 Data Domain azure-nve.local 08/13/25 15:47:04 33 GB 4154256312 cb full NW-PERF:azure-ubuntu:azure-ubuntu_DataDisk_0

It is not possible to do a DataDisk recovery to a new VM. An existing VM must be specified.

This is expected functionality.

• Option One: To recover the data disk only, specify -V Existing_VM in the nsrazure_recover command.
• Option Two: To recover the VM to a new VM, specify an SSID for the VMs OsDisk:

azure-nve:~ # mminfo -avot
volume        type   client           date     time         size ssid      fl   lvl name
….
azure_nve.local.dddefault.003 Data Domain azure-nve.local 08/13/25 15:47:03 31 GB 4171033528 cb full NW-PERF:azure-ubuntu:azure-ubuntu_OsDisk_1_cf93159d6205414baa8593901a918d3a
azure_nve.local.dddefault.003 Data Domain azure-nve.local 08/13/25 15:47:04 33 GB 4154256312 cb full NW-PERF:azure-ubuntu:azure-ubuntu_DataDisk_0

azure-nve:~ # nsrazure_recover -S 4171033528 -N 'Azure' -R 'NW-PERF' -A 'networkerstorageaccount' -V 'TestVM' -E 'DD-PERF:vnet' -T 'subnet'
Using 'vnet' vnet from resource group 'NW-PERF'.
Target VM 'NW-PERF:TestVM' does not exist and will be recreated.
Restoring OS disk 'azure-ubuntu_OsDisk_1_cf93159d6205414baa8593901a918d3a'.
Using 'networkerstorageaccount' storage account from resource group 'NW-PERF'.
… 

In some scenarios, a disk may show as "OsDisk_JobID_TimeStamp" for example:

azure-nve:~ # mminfo -avot
volume        type   client           date     time         size ssid      fl   lvl name
….
azure_nve.local.dddefault.003 Data Domain azure-nve.local 08/13/25 15:47:03 31 GB 4171033528 cb full NW-PERF:azure-ubuntu:azure-ubuntu_OsDisk_0_17143_1751393058

This disk suggests it was created from a previous restore attempt. During a nsrazure_recover, it is treated as a DataDisk, not an OsDisk. During the nsrazure_recover, you must specify the SSID of an OS disk that is not appended with a JobId_TimeStamp:

azure-nve:~ # mminfo -avot
volume        type   client           date     time         size ssid      fl   lvl name
….
azure_nve.local.dddefault.003 Data Domain azure-nve.local 08/13/25 15:47:03 31 GB 4171033528 cb full NW-PERF:azure-ubuntu:azure-ubuntu_OsDisk_1_cf93159d6205414baa8593901a918d3a