So (luckily, before a real disaster strikes), we decided to test the restore of a random VM.
We run Networker User, save set recover, select the necessary options, and initiate the restore - after 1-2 seconds, nsrvadp_recover.exe crashes, and that's the end of it. We've tried:
* different variations of shortnames/FQDNs/IPs for the vCenter server and esx host
* versions 188.8.131.52, 184.108.40.206 and 220.127.116.11 of Networker user,
* running NW user from different machines including from the proxy/server itself
same problem every time.
For info we are running 18.104.22.168 of NW Server
And 5.0.0 U3 of vCenter.
I contacted EMC Support who advised that this is a known problem with vCenter 5.0.0 U3 and we need to install 5.0.0 U2 instead. This was hugely inconvenient but we set up a new (test) vCenter server (U2) and ESX box, and tried again - it made no difference.
Right now we are pretty concerned because if we can't recover our VMs in a disaster situation we may as well pack up and go home.
Any help is appreciated, here is the info from the appcrash:
Problem Event Name: APPCRASH
Application Name: nsrvadp_recover.exe
Application Version: 22.214.171.124
Application Timestamp: 5239060c
Fault Module Name: nsrvadp_recover.exe
Fault Module Version: 126.96.36.199
Fault Module Timestamp: 5239060c
Exception Code: c0000005
Exception Offset: 000000000002e90f
OS Version: 6.0.6002.2.2.0.272.7
Locale ID: 2057
Additional Information 1: 7d97
Additional Information 2: 4e9e3e6764b18e7a39458c2911f84331
Additional Information 3: 9e14
Additional Information 4: ca4e565e198ca9e32d5eac40945ca729
Read our privacy statement:
Ok I have some more information, looks like it is struggling to create the VM in vCenter, it successfully recovers the VM metadata from tape but can't upload it...
Recovering files of client 'ken-vadp-test' from server 'ken-backup-02'.
Connecting to host 188.8.131.52:443.
Recovering to original VC system.
Recovering to original ESX host system.
libCURL SSL support is ENABLED
NetWorker install path: C:\Program Files\Legato\nsr\.
Temporary Directory for VADP created.
Temporary vmMntLoc Directory for VADP created.
VimServer is initialized
Volumes needed (all on-line):
LE0067 at \\.\Tape2
Total estimated disk space needed for recover is 83 MB.
Requesting 5 file(s), this may take a while...
Recover start time: 30/01/2014 16:19:16
Received 5 file(s) from NSR server `ken-backup-02'
Recover completion time: 30/01/2014 16:20:08
Trying to find the datacenter: Kensington ...
Trying to find the ESX host system: esxinfra3.caci.co.uk ...
Trying to find the resource pool: ...
Remapping Virtual Machine config data store from KEN-SAN-06a to KEN-SAN-06a.
Remapping Virtual Disk 'Hard disk 1' data store from KEN-SAN-06a to KEN-SAN-06a.
Upload the VM to vCenter Server.
New VM Name: KEN-VADP-TEST
Resource Pool: Resources
ESX Host: esxinfra3.caci.co.uk
Registering VM ...
Temporary directory 'C:\Program Files\Legato\nsr\tmp\1189507166' for VADP deleted.
Requesting 1 recover session(s) from server.
Please upload config files manually immediately, Will wait for 5 minsVADP:
I am going ahead with disk upload
Registering VM for 'KEN-VADP-TEST' ...
Task is -1% complete
82865:nsrvadp_recover: Failed to register the VM.
39077:nsrvadp_recover: error, The following VMware related error occured: Unable to register VM 'KEN-VADP-TEST'. Details: 'An error occurred for task 'RegisterVM_Task'. Details: The object or item referred to could not be found.'.
Restore of virtual machine failed!...
Completion time: 30/01/2014 16:25:11
Total time taken: 0 hr(s) 07 min(s) 06 sec(s)
I have the same problem only with Vcenter 5.1 U2. We had this problem after updating from Vcenter 5.1U1 to Vcenter 5.1 U2.
This mistale is here:
Faulting application name: nsrvadp_recover.exe, version: 184.108.40.206, time stamp: 0x52d906ac
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000003bf7c
Faulting process id: 0x9ac
Faulting application start time: 0x01cf1e547331e78b
Faulting application path: C:\Program Files\EMC NetWorker\nsr\bin\nsrvadp_recover.exe
Faulting module path: C:\Program Files\EMC NetWorker\nsr\bin\MSVCR100.dll
Report Id: bcb4a8cb-8a47-11e3-b343-0050568f75db
I have created ticket to EMC. I am waiting resolve problem.
Hi, I have resolved this problem. I got a three files and repalced the original files them.
Here is files:
I'd like to notice that these files are correct only for Networker 220.127.116.11
Do you have bug id? (something like NWxxxxx) That way people can check if further releases have this fix included (eg. 18.104.22.168 which is next to be released).
Contact EMC Support and request a port of the nsrvadp_recover fixes from NW155390 and NW151105, for whatever version of NW you're running.
They provided us with the files for 22.214.171.124, and now (after upgrading) we have the exact same problem in 126.96.36.199 so are currently waiting for another port.
Such a massive bug, I can't believe this sort of stuff gets past EMC's testing team.