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'.
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.'.
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 7.6.5.7, and now (after upgrading) we have the exact same problem in 8.1.0.5 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.
Do you have bug id? (something like NWxxxxx) That way people can check if further releases have this fix included (eg. 8.0.3.3 which is next to be released).
As your version is out of support, I doubt you can even obtain the fix even if it exists for your version. Getting to supported level will be first thing most likely.
greenblueyellow
1 Rookie
•
18 Posts
0
January 31st, 2014 02:00
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 194.70.42.11: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.
Initializing VimServer...
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
Datacenter: Kensington
Resource Pool: Resources
ESX Host: esxinfra3.caci.co.uk
Transport Mode:nbd
Registering VM ...
Temporary directory 'C:\Program Files\Legato\nsr\tmp\1189507166' for VADP deleted.
Requesting 1 recover session(s) from server.
C:\Program Files\Legato\nsr\tmp\1189507166\1\diskBitmap_0
C:\Program Files\Legato\nsr\tmp\1189507166\1\Disks
C:\Program Files\Legato\nsr\tmp\1189507166\1\metaFile_C
C:\Program Files\Legato\nsr\tmp\1189507166\1\reference_C
C:\Program Files\Legato\nsr\tmp\1189507166\1\vm_config.xml
VADP:
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)
ToyotaFS
2 Posts
0
February 1st, 2014 03:00
Hi,
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: 8.1.0.5, 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.
Mgrunert
10 Posts
0
February 25th, 2014 09:00
Same issue here .. whats the solution for the issue ?
ToyotaFS
2 Posts
0
February 25th, 2014 21:00
Hi, I have resolved this problem. I got a three files and repalced the original files them.
Here is files:
libvmdk.dll
nsrvadp_recover.exe
nsrvadp_save.exe
I'd like to notice that these files are correct only for Networker 8.0.3.1
ble1
4 Operator
•
14.4K Posts
0
February 26th, 2014 01:00
Indeed, one would think this stuff is addressed without unnecessary regressions... Thnx.
greenblueyellow
1 Rookie
•
18 Posts
0
February 26th, 2014 01:00
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 7.6.5.7, and now (after upgrading) we have the exact same problem in 8.1.0.5 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.
ble1
4 Operator
•
14.4K Posts
0
February 26th, 2014 01:00
Do you have bug id? (something like NWxxxxx) That way people can check if further releases have this fix included (eg. 8.0.3.3 which is next to be released).
Thierry101
2 Intern
•
326 Posts
0
March 11th, 2014 18:00
Hi folks
what's the solution for this?
please enlighten or status of this issue
thank you
Mgrunert
10 Posts
0
March 12th, 2014 00:00
I got a fix from EMC support for 8.0.4 and 8.1.5 - they solved it fine.
leo131
1 Message
0
September 30th, 2016 00:00
I have the same problem with 7.6.5.7 How would I get these fixes?
ble1
4 Operator
•
14.4K Posts
0
September 30th, 2016 10:00
As your version is out of support, I doubt you can even obtain the fix even if it exists for your version. Getting to supported level will be first thing most likely.