VADP fails with vSphere5

Question

Hi,

in a vSpere5 environment using VADP (hotadd) with NetWorker 7.6.3.3 tis issue occoures:

* RHBERP01:*FULL* SnapShot created Successfully for VM 'RHBERP01'.

* RHBERP01:*FULL* Downloading VM configuration for RHBERP01.

* RHBERP01:*FULL* 83065:nsrvadp_save: The following internal error occurred: Unable to download config file: 'RHBERP01/RHBERP01.vmx', HTTP response code: 404, URL: 'https://10.10.10.65:443/folder/RHBERP01/RHBERP01.vmx?dcPath=RhB%20LLR%252fMLR%20Services&dsName=SANV05'

* RHBERP01:*FULL* 83687:nsrvadp_save: Could not download VM configuration for VM 'RHBERP01'.

* RHBERP01:*FULL* Temporary directory 'c:\mnt\RHBERP01' for VADP deleted.

I know the issue with vSphere 4/4.1 but this is vSphere5.

Thanks for feedback,

Kai

pn1lDbv3G612259 · Answer

Hi Kai,

This issue may occur when the .vmx or the .nvram files are stored on a shared datastore (that is, if the datastore is visible to more than 1 ESX host).

The ESX host holds a lock to these files when the virtual machines is powered on, so attempting to download these files from another ESX host results in failure.

Please refer this article form VMware:

http://kb.vmware.com/selfservice/microsites/search.dolanguage=en_US&cmd=displayKC&externalId=1019286

Thank you

ShivaKiran

Bebo2k · Answer

Hi Kai,

As you mentioned you have 7.6.3.3 , Have you rebooted the VADP proxy during the upgrade process to 7.6.3.3 ?

The NetWorker 7.6 SP3 release provides support for VADP with vSphere 5.0 and ships with VDDK version 5.0. If VDDK version 1.2.1 was used before and you are upgrading to NetWorker 7.6 SP3, a reboot of the VADP proxy host is required after the upgrade. Use the following steps:

1. Select the NetWorker 7.6 SP3 package for upgrading. NetWorker 7.6 SP2 will be uninstalled from the system and you will be prompted to reboot.

2. Reboot the VADP proxy host.

3. Manually install NetWorker 7.6 SP3.

Note: During this process, ensure that you do not delete the nsr folder from the Windows system.

Hope this helps you.

Thanks,

Ahmed Bahaa

kvogel1 · Answer

Hello Shivakiran, please see my detaills in the issue description: thos is not ESX4. Its ESXi5 The issue with 4.0/4.1 is well known Regards Kai

pn1lDbv3G612259 · Answer

Hi Kai,

Also try these steps:

Remove all lock files in the cache on the VADP proxy
Vmotion to another ESX host, make first copy
Ask for VMware help to restart mgmt services on the ESX host which the VM resides.

Thank you

ShivaKiran

kvogel1 · Answer

Hi Ahmend, the Proxy is a new installed 7.6.3 Client, was not updated from previous release of NetWorker. Regards Kai

Bebo2k · Answer

Hi Kai, Did you tried the NBD transport modes ? is it failing with the same error message or backing up successfully ? Thanks, Ahmed Bahaa

kvogel1 · Answer

Hi Ahmed,

the test with NBD transport mode failes with same error. I see the VM is still HW version 4 and VMFS is 3.21. Both,

VMFS and HW version of VM, was not upgraded by vSphere upgrade process. Can this be a factor?

RegardsKai

Bebo2k · Answer

Hi Kai,

Upgrade the VMFS to version 5 and Hardware version of VM to version 7 and test the backup again, It will be the same error message or will be different, and if you have more information in the logs please provide it to us as well.

Waiting your updates.

Thanks,

Ahmed Bahaa

kvogel1 · Answer

Hi, we solved the issue:  there was a special caracter in vCenter Datacenter name (/). This was the reason why proxy not was not able to browse the DataStores per https. Thanks all for your help, Kai

NetWorker

VADP fails with vSphere5

Was this post helpful?