We managed to resolve this in the end, so in the event that anyone is seeing the same issue, follow the below:
Cause: The virtual machine that was protected by the VMware Protection Policy has been deleted from the vCenter inventory. The NetWorker nsrdb database stores the virtual machine by UUID and performs a lookup of the virtual machine at the start of the backup workflow.
Resolution: This behaviour is by design. The nsrpolicy command line utility can be used to update the group that's assigned to the failing policy:
nsrpolicy group update vmware -g *GROUP_NAME* -O "UUID"
Thank you for sharing this. It was annoying me for a while that our VM backup policy was failing but I couldn't see which VM had failed. This works perfectly.
Gwyn92
1 Rookie
•
5 Posts
4
August 24th, 2017 01:00
Hi again,
We managed to resolve this in the end, so in the event that anyone is seeing the same issue, follow the below:
Cause: The virtual machine that was protected by the VMware Protection Policy has been deleted from the vCenter inventory. The NetWorker nsrdb database stores the virtual machine by UUID and performs a lookup of the virtual machine at the start of the backup workflow.
Resolution: This behaviour is by design. The nsrpolicy command line utility can be used to update the group that's assigned to the failing policy:
nsrpolicy group update vmware -g *GROUP_NAME* -O "UUID"
Thanks.
Ben.
BonezAU1
5 Posts
0
March 19th, 2018 19:00
Thank you for sharing this. It was annoying me for a while that our VM backup policy was failing but I couldn't see which VM had failed. This works perfectly.