Symptoms

Azure VM backups are completing successfully from NetWorker; however, Azure VM backups are missing from the NetWorker Web User Interface (NWUI) in the Recovery and Save sets tab. After setting a time range, client type: Azure, selecting the Azure subscription, and clicking search save sets, either of the following conditions appears: Save sets window returns: No Client/Volume filter selected OR No Backups/Clones available for the applied filters!Save sets window returns save sets, but specific backups from dates where backups are available are missing Azure VM backups are succeeding, but there are `psuedo_saveset` backup failures observed during backup workflows. If all backup workflows are failing on psuedo_saveset, no VM backups are displayed in NWUI.If some backup workflows are failing on psuedo_saveset, the backups where psuedo_saveset failed are not displayed in NWUI.

Cause

At the end of an Azure VM backup workflow, a backup of `psuedo_saveset` is performed. The backup action log shows: 08/28/25 21:37:26 The save job for the save set 'pseudo_saveset' on the host 'azure-nve.local' has been completed. 08/28/25 21:37:26 azure-nve.local:pseudo_saveset succeeded. 08/28/25 21:37:26 azure-nve.local:pseudo_saveset Save has closed the session on the host 'azure-nve.local'. The `psuedo_saveset` backup creates a save set called 'Azure'. azure-nve:~ # mminfo -avot -r "savetime(20),sumflags,ssid,name" | grep 'Azure' ... 08/28/25 21:37:23 cb 4189127764 Azure 08/28/25 21:47:36 cb 4172351160 Azure The 'Azure' save set contains information about the backups completed during the workflow, for example: azure-nve:~ # mminfo -S -q ssid=4189127764 ssid=4189127764 savetime=08/28/25 21:37:23 (1756431443) azure-nve.local:Azure ... *VM_LIST: "DD-PERF:perf-ddperf-client-osl-longrun-0", "DD-PERF:perf-ddperf-client-osl-longrun-1", "DD-PERF:perf-ddperf-client-osl-longrun-2"; group: Test2/Test2/backup/Azure_Test2; saveset features: CLIENT_SAVETIME; Clone #1: cloneid=1756431444 time=08/28/25 21:37:24 retent=09/28/25 flags= frag@ 0 volid= 6488398 file/rec= 0/0 rn=0 last=08/28/25 The following mminfo command shows the Save Set ID (SSID) long-name for the save set: azure-nve:~ # mminfo -q ssid=4189127764 -r "ssid(55)" f30d35b7-00000006-f9b10454-68b10454-00080d00-a2f1743a The 'Azure' save set is what is used to show the VM save sets from a specific Save Time in NWUI: NetWorker is working as designed. If `psuedo_saveset` fails to backup and the 'Azure' save set is not created, the workflow's backups cannot be displayed in NWUI, even if individual VM backups completed successfully.

Resolution

Workaround: It is not possible to recover the save sets from NWUI. Recover the Azure VM using the nsrazure_recover command to recover a specific VM save set. The NetWorker Azure VM Snapshot Integration Guide provides information about this procedure. Manuals & Documents It is also documented in KB: NetWorker: How to perform Azure VM Snapshot restore from Command-Line CLI does not rely on the 'Azure' save set to present backups from a specific Save Time. From the CLI, you can specify the exact VM backup from SSID in the recover command. Resolution: If `psuedo_saveset` failure is a persistent problem, this must be resolved to prevent issues during data recovery. `psuedo_saveset` can fail for various reasons: Timeout failures: NetWorker: Azure VM backup workflow fails at the end of the backup on pseudo_savesetNetWorker server parallelism: NetWorker: Azure VM Snapshot Backups Failing "current save session has exceeded NetWorker server's parallelism" The psuedo_saveset failures must be investigated and resolved.

Support Cases