Im getting a error when i try to recover a *FULLVM* backup using hotadd transport mode through Proxy VADP (networker 7.6 SP2). When i power on the virtual machine after recovery, i get
"CID mismatch error: The parent virtual disk has been modified since the child was created"
error and the virtual machine doesnt power on. If i change transport mode to nbd, everything its fine.
i ve read that it could be the VDDKs libraries but im not sure how to update it.
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.
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
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.
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.
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 anotherseparate issue )
its strange , its seems that recovery process doesnt delete the snapshot used to recover.
Victor861
8 Posts
3633
0
Posted September 17th, 2012 03:00
VM recovery fails for NBDSSL and hotadd transport modes
NW132961
Recovery of a VM in NetWorker fails for the transport mode NBDSSL and for
hotadd mode for ESX 5.0 and with VC 5.0.
Workaround
Before performing the following steps, ensure that you delete any snapshots that
are active on the VM. Do not power on the VM until completing these steps.
1. Right click the VM and select Edit settings.
2. Select the virtual hard disk and select Remove but do not delete the VMDK.
Click OK.
3. Return to the Edit settings menu and select Add.
4. Choose Hard Disk and use an existing virtual disk.
5. Associate the new hard disk with the VMDK file, then click OK. For example,
use the Add disk pop-up window and add the hard disks by pointing them to
the correct VMDK file in the datastore.
6. Power on the VM.