Start a Conversation

Unsolved

This post is more than 5 years old

1896

January 13th, 2011 08:00

NW 7.6.1.2: VCB backups errors "Unable to find NSR Hypervisor resource for VC/ESX server"

Hello,

after migration to NW 7.6.1.2 (from 7.5.3) I have a serious issue with VCB backups.

I have followed the docs generated by the NPG for both the server migration to 7.6.1.2 and for VCB configuration (VBC procy and VM clients).

The backup server runs on a Windows 2003 R2 SP2 32bit box. The VCB proxy (also storage node) on a Windows 2003 R2 SP2 64bit box.

VC/ESX are at version 4.0 update2. VC is on a Windows 2003 R2 SP2 32bit VM.

The client configuration for the VCB proxy has been done with the following parameters.

Application information:

VCB_HOST=myVC

VCB_BACKUPROOT=G:\\vcbmount
VCB_TRANSPORT_MODE=san
VCB_VM_LOOKUP_METHOD=ipaddr
VCB_PREEXISTING_MOUNTPOINT=delete
VCB_PREEXISTING_SNAPSHOT=delete

When I run a backup of a virtual machine I have this:

* MyVM:*FULL* 1 retry attempted

* MyVM:*FULL* Initializing VCB Configuration..

* MyVM:*FULL* 71715:nsrvcb_save: Unable to find NSR Hypervisor resource for VC/ESX server myVC for client MyVM

* MyVM:*FULL* Unable to configure the VCB parameters..

I have re-configured the NSR hypervisor resource as mentioned in the NPG and I have this error when I run the discovery:

Starting Auto Discovery Process for MyVC

Monitoring Auto Discovery for MyVC
Auto Discovery for MyVC failed
NSR hypervisor resource 'MyVC' not found


Monitoring Auto Discovery Completed

And this is what is logged on daemon.raw:

78839 13/01/2011 17:07:27  nsrtask [MyVC] 68099 1294934847 0 0 2 2904 2572 0 MyVC nsrvim 31 Exiting '%s', process %d on %s. 3 20 6 nsrvim 1 4 2572 12 27 MyVC
78832 13/01/2011 17:07:27  nsrtask [MyVC] Task result: NSR hypervisor resource 'MyVC' not found
78833 13/01/2011 17:07:27  nsrtask [MyVC] Updating task resource
78835 13/01/2011 17:07:27  nsrtask [MyVC] Exiting 'nsrtask', process 11516 on macon.conext.europa.eu

Thanks for reading,

Vito

736 Posts

January 14th, 2011 07:00

Hi,

Have a look through the admin guide to be sure that you have configured the hypervisor resource correctly: page 521.  Also be sure that the Virtual Center client resource was configured in NetWorker with the name myVC.  Check name resolution too between all the relevant machines - auto-discovery errors are very often name resolution related.

-Bobby

No Events found!

Top