A final update: I still have the same display issue with our production server while on its clone there is no display issue: the protection group created by the CLI command would show up immediately in the workflow. My further tests showed that on the production Networker server, once the scheduled backup action was executed according to the scheduler, the protection group will appear in the workflow as well, but not before the action execution. I can’t explain why. Anyway, this is just a display issue as the protection group is in fact assigned to the workflow by the CLI commands. As per the second question about how to check if a protection has not been assigned to a workflow yet, I didn’t get any answer from DELL/EMC support. So far I use a stupid work-around to avoid going through all the workflows to check: a dedicated empty Policy and Workflow was set up. I try to assign the protection group to this dedicated policy/workflow, if it succeeds, that means the group has not been assigned to other workflow yet. Otherwise it has been assigned already. Then I remove the group from this special policy/workflow. You might wonder why I don’t try to assign directly the group to its final destination policy/workflow. This is because my script will create the policy/workflow later. I don’t want to create the policy/workflow first and then realize the group is not an available one. I will close this threat by marking this update as the solution. Thanks everyone for your help.
I am testing some Powershell scripts with ‘nsradmin’ command to create Policy/Workflow/Action configurations. I have two issues about protection group management. Maybe I should use a different CLI command? Any help is appreciated. Thanks
Two questions about scripting ‘nsradmin’ to manage Protection groups