Symptoms

The NetWorker server lockbox folder was renamed in the environment, and the default directory did not contain any lockbox files. The NetWorker VMware Protection integration is being configured with the vProxy Appliance. The vProxy has been deployed, and the new NSR VMware Proxy resource is being added in the NetWorker Management Console (NMC) under the Devices tab. The appropriate details are configured and when selecting the OK option, an error message is generated: Failed to open lockbox C:\Program Files\EMC NetWorker\nsr\lockbox\[NETWORKER_SERVER]\clb.lb The /nsr/logs/daemon.raw shows: MM/DD/YYYY [NETWORKER_SERVER] nsrd NSR notice vProxy '[NSR_VMWARE_PROXY]' is now Enabled. MM/DD/YYYY [NETWORKER_SERVER] nsrd NSR info VM proxy Warning event: vProxy '[NSR_VMWARE_PROXY]' is unavailable. MM/DD/YYYY [NETWORKER_SERVER] nsrmon NSR critical Unable to retrieve vProxy '[NSR_VMWARE_PROXY]' connection information. MM/DD/YYYY [NETWORKER_SERVER] nsrd NSR error Instance UUID not found for '[NSR_VMWARE_PROXY]' vProxy.

Cause

The NetWorker server is unable to access the clb.lb lockbox file in the environment during the vProxy registration. For example, the lockbox file was moved from the default directory C:\Program Files\EMC NetWorker\nsr\lockbox\[NETWORKER_SERVER]\ to another directory.

Resolution

The NetWorker server must access the "clb.lb" lockbox file during the vProxy registration. Copy the lockbox files back to the default C:\Program Files\EMC NetWorker\nsr\lockbox\[NETWORKER_SERVER]\ directory.

Support Cases