2 Intern
•
69 Posts
0
2740
October 16th, 2020 14:00
nsrpolicy - did something change in ver 19.3?
Occasionally, a VM that was deleted from vCenter (but which wasn't removed from a Networker group) would result in a backup "failure".
I have previously used this command to eliminate this error (that's not really an error):
nsrpolicy group update vmware -g -O
But, when I just ran this command, it comes back with this message:
195173:nsrpolicy: No items to add or delete.
The syntax of this command is:
nsrpolicy group update
--group_name -g
[--comment -c ]
[--server -s ]
[--debug -D ]
[--help -h]
Additional parameters to be specified for 'vmware' type are:
nsrpolicy group update vmware
[--vcenter_name, -V vCenter name]
[--add_vmware_clnt_list, -o ex. /MyFolder, /DC/host/vm]
[--del_vmware_clnt_list, -O ex. /MyFolder, /DC/host/vm]
[--backup_optimization, -z capacity | performance]
[--help -h]
(I'm pretty sure I had the group name and UUID correct when I ran the command)
Did something change in Networker 19.3? Do I have the wrong command syntax?
0 events found
jokrr
1 Message
1
October 20th, 2020 23:00
Yes, the nsrpolicy command changed in 19.3
Found a KB about it, Knowledge Base Article: 000545650
Workaround is to temporarly add a vm to the group, then edit again and remove it to force a refresh.
However this haven't worked 100% in the past for me
CrashCart
2 Intern
•
69 Posts
0
October 22nd, 2020 08:00
That did the trick. Thank you.
Makes me wonder, if this method (add a vm to the affected group, save, then remove that just-added vm, and save again) would have worked in previous versions.
AS89
1 Message
0
July 5th, 2021 03:00
Execute below cmd first
nsrlogin -u (user id) -P (nmc port number) -H (nmc hostname)
It will ask your NMC password
Then execute the command
nsrpolicy group update vmware -g -O
barry_beckers
393 Posts
0
July 25th, 2021 10:00
As those kind of failures are peculiar in the sense that it causes a workflow to fail without actually stating a vm, except the uuid in the messages.
Nw19.5 is supposed to address that, stating the name also, I believe by using information from earlier backups.
Up until know I edited the protection group via nmc (I believe opening it up and clicking ok was enough, but mostly I deselected one vm and added it again afterwards), but doing so via nsrpolicy is even better as one might even be able to script that based on the error...