The NetWorker VMware Protection integration is configured with the vProxy Appliance. The NetWorker Management Console (NMC) Monitoring tab shows a VMware Policy backup workflow in a failed status with no virtual machines showing as failed.
Figure 1: Workflow completion status shows as failed but all VMs in the workflow show successful.
The Backup detail
Action Message shows a failed backup in the Final Summary section, but the Backup details "Failed" section does not show a virtual machine.
Figure 2: The backup action messages show "X Failed Backups."
The backup action log shows that some virtual machines were skipped during the execution.
MM/DD/YYYY HH:MM:SS Action backup vmware-vproxy 'backup' has initialized as 'vproxysave job' with job id 2149387
...
MM/DD/YYYY HH:MM:SS Skipping [VM_NAME] VM from the backup: Virtual Machine connection state is disconnected.
MM/DD/YYYY HH:MM:SS Skipping [VM_NAME] VM from the backup: Virtual Machine connection state is disconnected.
...
MM/DD/YYYY HH:MM:SS Final Summary of VMs:
MM/DD/YYYY HH:MM:SS 0 canceled backups
MM/DD/YYYY HH:MM:SS 2 failed backups
MM/DD/YYYY HH:MM:SS 2 successful backups
MM/DD/YYYY HH:MM:SS 0 waiting backups
MM/DD/YYYY HH:MM:SS 0 running backups
MM/DD/YYYY HH:MM:SS 2 savesets output to next action
MM/DD/YYYY HH:MM:SS Action has finished with failures.
MM/DD/YYYY HH:MM:SS Action backup vmware-vproxy 'backup' with job id 2149387 is exiting with status 'failed', exit code 1
The protected virtual machine is in a disconnected state in the vCenter inventory. The VMware vSphere web client shows:
Figure 3: VMs which reported as failed in the backup log show as (disconnected) in vSphere.
The behavior is by design when a protected virtual machine is disconnected in the vCenter inventory. The failure message informs that some of the protected virtual machines backups did not run during the workflow execution.
Once the virtual machine-disconnected state is resolved in the vCenter inventory, the virtual machine backups continue to run.