Note: Before performing the KB resolution steps, take a backup of the existing "mm" and "res" for safe-keeping.
To make a safe-copy:
1) Make sure no backups are running, confirm and then stop the NetWorker services on the NetWorker backup server.
2) Go to the \nsr directory and make a manual copy of "mm" and "res" folders. You can place the copy outside the \nsr directory or have the 'copy' name appended for identification. This is being done so that should anything go wrong, you can replace this copy of "mm" and "res" folders back again into the original location and then bring up the services.
3) Once the copy is done, start the NetWorker services.
Impact: You are unable to deploy or remove a policy to VM via NMC
Issue: You are unable to deploy or remove a policy to VM vi NMC.
When you try to apply VBA policy to a VM it give a pop up with message "There are no Policies for this vCenter"
Environment: Networker 8.2, VBA 1.X, 1.1
Cause: The issue is caused by vcenter configured by wrong name. Check under the EBR appliance properties.
Resolution:
Bring down Networker Services
Connect to nsradmin prompt and check for the "nsr hypervisor" resource
nsradmin -d
nsrdmin> p type: nsr hypervisor;
Delete the effected hyper visor resource. You have to delete the hyper visor offline. (Always keep a backup of the res folder before making any changes to it.)
Bring up the Networker services
Manually create the hyper visor resorce.
nsradmin
nsrdmin> create type:NSR Hypervisor;name:vCenter_FQDN or ip
Once create run the following command
nsrdmin> p type: nsr hypervisor;
Update the following proerties using "update" command.
nsrdmin> update username: username
nsrdmin> update pasword: vc user password
You can change proxy to any desired machine from Networker Server.
(Note : 8.1.X Proxy has to have Windows OS installed. 8.2 can have a non windows VM.)
nsrdmin> update proxy: FQDN or IP
Once updated try to refresh the VMware view using the F5 key.
The EMC Support team can also be engaged to help you on the same in case this doesnt work. Anyway, you would have a copy of 'mm' and 'res' so any changes done can be reverted so that you can get back to your configuration that existed before performing the KB steps.
ChetanTikandar
40 Posts
1851
0
Posted June 16th, 2015 04:00
It looks like the vCenter info seems to be incorrect/corrupted/missing.
You can try the steps mentioned in the below EMC KB article and see it it helps in your case.
KB: https://support.emc.com/kb/199317
Note: Before performing the KB resolution steps, take a backup of the existing "mm" and "res" for safe-keeping.
To make a safe-copy:
1) Make sure no backups are running, confirm and then stop the NetWorker services on the NetWorker backup server.
2) Go to the \nsr directory and make a manual copy of "mm" and "res" folders. You can place the copy outside the \nsr directory or have the 'copy' name appended for identification. This is being done so that should anything go wrong, you can replace this copy of "mm" and "res" folders back again into the original location and then bring up the services.
3) Once the copy is done, start the NetWorker services.
4) perform KB steps.
Regards,
Chetan Tikandar