Hi Frank,

Are you recovering a Windows VM or non-windows VM ? What is the NetWorker version you have on backup server ?

Are you running the NetWorker User on the VADP proxy ? If not please run the NetWorker User program from the VADP proxy.

Also after selecting Save Set Recover, select the virtual machine client from where the save set originated In the Source Client dialog box that pops up.  In the Save Sets dialog box, select the Save Set name for the full virtual machine backup client (FULLVM) and select a level FULL  backup. Note: Only level full of FULLVM save sets are supported for VM image restore.

Thanks,

Ahmed Bahaa

Make sure you are aware of the following considerations for VADP image level recovery :

- For a remote VADP proxy client, image level recovery requires the members of the VADP proxy client’s administrator group to  be part of the remote access list of the VM clients or the member should  have the “Remote access all clients” privilege.

- The user must have VMware privileges to register or create virtual machines.

- Recovery of the full virtual machine is only supported using save set recovery.

- Only level  FULL  of FULLVM save sets are su pported for VM image recovery.

- Backups made prior to NetWorker 7.6 Service Pack 2...... The VMware converter must be installed on the VADP proxy host machine if you need to recover backups made prior to NetWorker 7.6 Service Pack 2. If the VMware converter is not installed, the save set of the full virtual machine (FULLVM save set) can be recovered using a traditional NetWorker recovery.  Note: Image level recovery is only supported with VMware stand-alone converter version 3.0.3.

- A recover of the virtual machine will fail if the virtual machine already exists in the specified ESX or VC server. Also, the original virtual machine name’s folder should not exist in the datastores selected for recovery. If you do not want to delete the original VM, remove the VM from the inventory (right click the VM name in the  vCenter GUI  and select  Unregister the VM), then rename the datastore folders associated with the VM by using the Datastore window in the vCenter GUI .

Thanks,

Ahmed Bahaa

Are you recovering a Windows VM or non-windows VM ? What is the NetWorker version you have on backup server ?

-Yes ,it's a Windows VM and the Networker version is 7.6sp3

Are you running the NetWorker User on the VADP proxy ? If not please run the NetWorker User program from the VADP proxy.

-I am running the Networler User on the VADP proxy (the proxy is also the backup server)

Also after selecting Save Set Recover, select the virtual machine client from where the save set originated In the Source Client dialog box that pops up.  In the Save Sets dialog box, select the Save Set name for the full virtual machine backup client (FULLVM) and select a level FULL  backup. Note: Only level full of FULLVM save sets are supported for VM image restore.

- Yes,I do follow these steps.But it doesn't work.

- For a remote VADP proxy client, image level recovery requires the members of the VADP proxy client’s administrator group to  be part of the remote access list of the VM clients or the member should  have the “Remote access all clients” privilege.

*I run from the VADP proxy which is also the backup server.So it's not a remote proxy ,right?

- The user must have VMware privileges to register or create virtual machines.

*Which user? The windows user that I run Networker User?(My backup server and VADP proxy was Windows based)The Netwroker User even didn't ask me the vCenter to use.And my backup server/proxy's Windows was not added into any AD.

- Recovery of the full virtual machine is only supported using save set recovery.

* Yes,I used save set recovery.

- Only level  FULL  of FULLVM save sets are su pported for VM image recovery.

*Yes,I choose the FULLVM level FULL save set.

- Backups made prior to NetWorker 7.6 Service Pack 2...... The VMware converter must be installed on the VADP proxy host machine if you need to recover backups made prior to NetWorker 7.6 Service Pack 2. If the VMware converter is not installed, the save set of the full virtual machine (FULLVM save set) can be recovered using a traditional NetWorker recovery.  Note: Image level recovery is only supported with VMware stand-alone converter version 3.0.3.

*Backup was made from Networker 7.6 SP3.

- A recover of the virtual machine will fail if the virtual machine already exists in the specified ESX or VC server. Also, the original virtual machine name’s folder should not exist in the datastores selected for recovery. If you do not want to delete the original VM, remove the VM from the inventory (right click the VM name in the  vCenter GUI  and select  Unregister the VM), then rename the datastore folders associated with the VM by using the Datastore window in the vCenter GUI .

* The VM was deleted before recover.(choose delete from disk through vSphere Client)The folder was deleted too.And with command line ,the recover do create the VM ,but the VM's OS isn't bootable.

Did you ever manage to get the OS bootable ?

I have exactly the same problem with vsphere5 and vadp restore.  The server restore is working without any error, but the server can not start, the harddisk is not readable.

I mounted the vmdk to another server as an extra disk, but that server couldn't read the pariition either.  In my case it was W2K3 server. I am a bit stumped by this.

best regards,

Andres

The restore failure is because of the OS langurage uesd of backup server.And also cli restore is not supported while vCenter running on an non-English OS.

After I reinstall the Networker I can use Networker User to restore the image now.

But, when I choose the SAN as the transform mode the VM restored is still unbootable.

If I choose NBD as the transform mode the VM restored is bootable. I have compare the two vmx file and they are the same.

Hi,

I can confirm that a restore with NBD transport is working without any problem.  I am a happy man :-)

Thank you for the valuable tip!

Andres

Hi,

I have the same error

but my storage node and networker server is  in English and networker console and user too. i try to restore with NBD and SAN but have the same error.

i can boot the vm.

Did you have a idea ?

I found the solution in my case

when you restore vm in parrametre restoration

Transport mode in the object NDB it is mandatory to uppercase.   NDB lowercase don't work !!!

Hi Jacob,

This is weired , We have it already with san lowercase and works fine, we didnt try the nbd , but i dont think this is the solution, i didnt find any related articles or similar issues like that in the case-sensitive of the transport mode field, I believe there is another root cause of the issue but has not been recognized while troubleshooting (may be i am wrong ). Anyway, Is there any other changes you have implement before that ? What is the application information attributes configured ?

Thanks,

Ahmed Bahaa

Hi Frankliu

I have the same issuewith NW 8. have you found the solution?

Thanks

HR

Hi,

I  reinstall the Networker server without language package,and rename all the VM into English.Than I can backup the VM .

But I can only restore in NBD mode.That project was closed ,so I don't know whether SAN mode will work.

I've just run into the same Problem here. Networker 8.0.1, ESX 5.1. Backup is fine. Recovered image wont boot. Transport mode is san.

on proxy start diskpart and check the vm volumes (disks) are not set to readonly

DISKPART> select disk xx

DISKPART> detail disk

look for "Read-Only" - it has to be "No"

vddk library will not report errors when using san mode and it is likely the writing on the disk does not happen due to "readonly" set to "yes".

I have found such disks. They are also shown as unavailable, offline (obsolete path). How can i fix this?

Plus, Backups are restored (when writing to other LUNs) and appear in vCenter, but do not boot. How can this be caused by offline disks?