Unsolved

This post is more than 5 years old

16 Posts

1817

May 13th, 2014 00:00

VADP restore of VMs fail

Hi,

Our networker version is: 7.6.5.2 Build 1187.

When we do VADP restores it fails, you can see the detailed restore message below. Any idea whats going wrong?

Recovering files of client 'SRV1' from server 'nwbackup'.

Connecting to host vc1.TEST.NET:443.

53365:nsrvadp_recover: NSR server `nwbackup': busy

71740:nsrvadp_recover: Waiting 30 seconds then retrying

C:\Program Files\EMC NetWorker\nsr\tmp\3060145203\1\diskBitmap_0

C:\Program Files\EMC NetWorker\nsr\tmp\3060145203\1\Disks

C:\Program Files\EMC NetWorker\nsr\tmp\3060145203\1\metaFile_C

C:\Program Files\EMC NetWorker\nsr\tmp\3060145203\1\reference_C

C:\Program Files\EMC NetWorker\nsr\tmp\3060145203\1\vm_config.xml

Making directory: [esx1-ds2] SRV1

Recovering to original VC system.

Recovering to remote/new ESX host system.

libCURL SSL support is ENABLED

NetWorker install path: C:\Program Files\EMC NetWorker\nsr\.

Temporary Directory for VADP created.

Temporary vmMntLoc Directory for VADP created.

Initializing VimServer...

VimServer is initialized

Volumes needed (all on-line):

VMBACKUP-026 at /dev/rmt/9cbn

Total estimated disk space needed for recover is 87 MB.

Requesting 5 file(s), this may take a while...

Received 5 file(s) from NSR server `nwbackup'

Recover completion time: 5/12/2014 9:38:05 PM

Trying to find the datacenter: DC ...

Trying to find the ESX host system: esx1.TEST.NET ...

Trying to find the resource pool:  ...

Remapping Virtual Machine config data store from esx2-ds2 to esx1-ds2.

Remapping Virtual Disk 'Hard disk 1' data store from esx2-ds2 to esx1-ds2.

Upload the VM to vCenter Server.

New VM Name:   SRV1

Datacenter:    DC

Resource Pool: Resources

ESX Host:      esx1.TEST.NET

Transport Mode:nbd

Registering VM ...

Registering VM for 'SRV1' ...

Task is -1% complete

Task is -1% complete

Reconfiguring VM for 'vm-1744' ...

Task is -1% complete

Task is 100% complete

Task is -1% complete

Deleting snapshot for 'snapshot-1745' ...

Task is -1% complete

Task is -1% complete

53365:nsrvadp_recover: NSR server `nwbackup': busy

71739:nsrvadp_recover: Warning: Required volume VMBACKUP-026's status is near-line

71740:nsrvadp_recover: Waiting 30 seconds then retrying

53365:nsrvadp_recover: NSR server `nwbackup': busy

71739:nsrvadp_recover: Warning: Required volume VMBACKUP-026's status is near-line

71740:nsrvadp_recover: Waiting 30 seconds then retrying

53365:nsrvadp_recover: NSR server `nwbackup': busy

71739:nsrvadp_recover: Warning: Required volume VMBACKUP-026's status is near-line

71740:nsrvadp_recover: Waiting 30 seconds then retrying

53365:nsrvadp_recover: NSR server `nwbackup': busy

71739:nsrvadp_recover: Warning: Required volume VMBACKUP-026's status is near-line

71740:nsrvadp_recover: Waiting 30 seconds then retrying

Total estimated disk space needed for recover is 40 GB.

openVddkHandle() successful for disk number 2000 Using 'nbd' as the transport mode for VirtualDisk_2000.

Disk handler for disk 2000 opened successfully

C disk handle open success

.....................................

..

Warning top extent index reached maximum extent count

............................................................................................83342:nsrvadp_recover: Error writing to VMDK: 8192 bytes written instead of 131072 bytes.Warning top extent index reached maximum extent count

Received 242584 matching file(s) from NSR server `nwbackup'

Recover errors with 1 file(s)

Recover completion time: 5/12/2014 10:33:50 PM

Temporary directory 'C:\Program Files\EMC NetWorker\nsr\tmp\3060145203' for VADP deleted.

83342:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 131072 bytes.3:nsrvadp_recover: cannot write to C:\Windows\System32\config\SOFTWARE{00c56cd9-b9b1-11e3-9000-0050569f3297}.TMContainer00000000000000000002.regtrans-ms: No such file or directory

16294:nsrvadp_recover: Encountered an error recovering C:\Windows\System32\config\SOFTWARE{00c56cd9-b9b1-11e3-9000-0050569f3297}.TMContainer00000000000000000002.regtrans-ms

53363:nsrvadp_recover: Recover of rsid 474056 failed: Error receiving files from NSR server `nwbackup'

73724:nsrvadp_recover: One or more recover threads failed to exit successfully

Failed to recover files: Parent recover thread exited with errors

Restore of virtual machine failed!...

Completion time: 5/12/2014 10:34:05 PM

Total time taken: 1 hr(s) 02 min(s) 37 sec(s)

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

May 13th, 2014 04:00

268 Posts

May 13th, 2014 04:00

Looks like known issue (NW147315). I think its better to contact support for more help.

Refer to below link for more information,

http://support.emc.com/kb/171971

Regards,

Prajith

16 Posts

May 13th, 2014 07:00

Our build(7.6.5.2 Build 1187) contains the fix I think.

NW147315 - VADP: Full VM recover fails: Error writing to VMDK: 0 bytes written instead of n bytes.

- esg134832: http://solutions.emc.com/emcsolutionview.asp?id=esg134832

16 Posts

May 14th, 2014 00:00

I don't understand the extend problem, Why it is effecting us, what should we do?

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

May 14th, 2014 02:00

Are you VMware admin?  If not, please pass it to VMware admin so he can check out if you reached limit of extents.

16 Posts

May 14th, 2014 03:00

We upgraded the networker user client on VADP proxy and now we can restore successfully. But it still gives warnings in first post.

0 events found

No Events found!

Top