Hotadd recovery problem

Hi,

thanks for ur reply .

thats page helped me to solve the problem about power on the virtual machine after recovery, but problem using hotadd recovery is still there.

When i do a image level recovery using hotadd, virtual machine never power on correctly.

i have found this about VDDK libraries

"VDDK 5.0 U1 resolves the following issue:

• Snapshot consolidation failure when cleaning up after HotAdd backup.  When VMware Data Recovery (or VADP backup software) tried to clean up after HotAdd backup, snapshot delete failed as the appliance was reconfigured, and an exception was reported. The problem was caused by premature exit of the vpxa process, so vpxa did not inform backup code that HotAdd disks should be removed. Stale HotAdd disks remained, and were not recognized the next time backup software ran. This caused failure of snapshot delete, resulting in a buildup of redo logs. The solution is to wait longer for vpxa to report, and apply heuristics to clean up stale HotAdd disks if they appear. The VDDK 5.0 U1 fix also works with earlier ESX/ESXi versions and for stale redo logs left by earlier VDDK versions."

I dont know how to see my VDDKs libraries version and if i need, how to update it.

any help will be apreciated .

Víctor.

Hi Victor,

Please refer the below given link.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007969

Regards

Panwar

Hi Victor,

Please refer this article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006410

This could be of help

Thank you

ShivaKiran

thanks for reply,

buuuut it doesnt help , any ideas?

thanks.

Hi Victor,

To know the VDDK package information on:

Windows: Control panel -> add remove programs -> select the VDDK program -> "click the support information" will give you the information about the VDDK version

Redhat : Command "rpm -qa" will list all the package names

Solaris: Command "pkginfo" will give you the information

As discribed in the VDDK release notes (link " http://www.vmware.com/support/developer/vddk/VDDK-501-ReleaseNotes.html) you can determine the current package on your VM.

VDDK package and product version should be 5.0.1 not 5.0.0. 

Installable VDDK package names are VMware-vix-disklib-5.0.0-614080 instead of VMware-vix-disklib-5.0.1-614080, and the installed product version shows as 5.0.0-614080 instead of 5.0.1-614080. You can distinguish them from VDDK 5.0 packages and product version 5.0.0-427917 by looking at the build number.

Please use the links to download and extract the VDDK 5.0 U1 on your environoment and test the restore with hotadd mode.

Installer: http://www.vmware.com/support/developer/vddk/  and

https://my.vmware.com/web/vmware/details?downloadGroup=VDDK50U1&productId=242

steps: http://wingloon.com/2012/05/29/how-to-install-vmware-virtual-disk-development-kit-vddk-5-0-update-1-on-centos-5-7/

Thank you

Shivakiran

Thanks,thats was useful , but still doesnt work .

When i install networker 7.6 SP2 software in the proxy VADP, it creates a VDDK folder on /programfiles/legato/nsr/plugins/VDDK

Should i install the VDDK 5.01 on that directory?, if i install it with the default path, VDDK is intalled on /programfiles(x86)/legato/nsr/plugins/VDDK and nothing is overwritten

I tried install VDDK 5.0.1 and overwrite the libraries that networker 7.6 SP2 installed too, but also didnt work.

thanks for help!

Hi Victor,

What was the error message shown after installing the VDDK. Can you please attach the screenshots so we can take a look

Thank you

ShivaKiran

Hi Sivakiran,

apparently there isnt any error after install VDDK, but the initial problem persists.

- With the VDDK installed on Proxy VADP, i launch a restore of a VM using hotadd transport mode with Networker User, apparently the process finishes fine.

- but when i go to power on the VM, the error appears:

Using NBD transport mode, this doesnt occurs. VM power on perfectly (altough ethernet adapters appears misconfigured, but this is another separate issue )

its strange , its seems that recovery process doesnt delete the snapshot used to recover.

best regards,

Víctor.

Hi Victor,

Thank you for the above information and the screenshots.

I have researched more on this and found the following links:

How to use the VMware hotadd Transport Mode:

http://support.ca.com/cadocs/0/CA%20ARCserve%20%20Backup%20r16-ENU/Bookshelf_Files/HTML/virtmach/index.htm?toc.htm?vm_how_2_use_vmw_hotadd_transport_mode.htm

Mismatch between parent CID/Client CID

http://dales-diary.co.uk/2011/10/parent-virtual-disk-has-been-modified-error-vsphere-5/

Try to verify them and let us know the feedback.

If the issue still persists, I would suggest you to open a service request with us so we can proceed with advanced troubleshooting.

Thank you

ShivaKiran

Hi ShivaKiran,

the second link was useful, i used other laborius procedure (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007969) to get the machine power on after error.

But problem still persists so, how can i open a service request?.

Thanks for ur help man .

best regards,

Víctor.

Hi Victor,

Please open a service request by calling the helpdesk 1877 534 2867

Alternatively, you can open a Chat and a SR would be created for you from  powerlink.emc.com/support

Thank you

Shivakiran

Message was edited by: Sivakiran Ivaturi

Hi Victor,

How are you?

In case you are using v5.0 of ESXi and VC- there are some known issues wiht hotadd mode recoveries.

To avoid issues- The only workaround suggested to use NBD|SAN

More documentation-

https://support.emc.com/docu41460_NetWorker-8.0-Documentation-Portfolio.pdf

Specifically, Page 65 of VMware Integarion Guide

I will be sure to update if I find more info.

Hi Victor,

How are you?

Here is some information about NBD and hotadd transport modes:

NBD (Network Block Device): In this mode, the VADP proxy server gets the data through the ESX server. Data is read from the storage device by the ESX host and then sent over an unencrypted network channel to the VADP proxy server.
VADP will use an over-the-network protocol to access the virtual disk. Data is read from the storage device by the ESX host and then sent across an unencrypted network channel to the VADP proxy. Please note that this mode does not provide the offload capabilities of the "san" mode (since data is still transferred from the ESX host across the network). However, "nbd" does not require shared storage and also enables VADP to be run inside a virtual machine.

where as

Hotadd: This mode can be used when the VADP is used in a virtual proxy and uses ESX I/O stack to move data

More over Virtual machines having IDE virtual disks are not supported for hotadd mode. Instead, nbd mode is recommended for these.

Thank you

Shivakiran

Thanks for the info!

Meanwhile I`ll use NBD transport mode for recover my VMs.

Is there much difference in performance between NBD and HOTADD transport mode?.

thanks for help guys!,

best regards,

Víctor.