VMware backup failing with:
Error 2012/04/29 17:51:53 563 Data Plugin NVBU-SERVER-VI Failed to locate VM 'TALEND' uuid '4237a67e-7819-2f87-4b64-2145167c2626' in the VI inventory
there may be a conflict with another uuid in the inventory but initially simply recreating the job vmware job definition may resolve this issue.
If not it may be necessary to remove the existing VM if there is an existing backup of it and the restore this to file before using the vmconverter to convert this back to a vm.
As stated above, recreating the job definition may resolve this issue.
If not it may be necessary to remove the existing VM if there is an existing backup of it and the restore this to file before using the vmconverter to convert this back to a vm. :
The following is the procedure from an existing solution doc to remove and restore the image to file before converting it back to a VM image. This is to resolve any uuid conflict with another image:
----
Cause:
You cannot restore a VM-system to an esx server that already has the same VM-system running on it even if you restore to a different Datastore because they will both try to use the same uuid.
Resolution
1/ restore the Vm-system using the restore option 'Restore files from backup'
2/ put the files on to the required datastore in a directory with the same name of as you intend to call the system you want to restore.
3/ you can now use the VMware converter tool to convert this Vm-system into a format that the esx can read.
For an example of this see:
http://docs.bakbone.com/docs/NetVault_Backup_VMware_Plugin_Users_Guide_English.pdf
page 50
Recovering a Virtual Machine from a VADP Backup
--------
Or cat the vmx file and look for the following line:
scsi0:0.fileName = "converted vmdk file name"
Example:
scsi0:0.present = "true"
scsi0:0.fileName = "DC1-000001.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
This gives you the name of the VMDK file it wants. As an example the file is DC1-000001.vmdk
4/ we now need to convert these files into the correct format for esx server to read. This using the following command.
vmkfstools -i scsi0.vmdk -d thin ./new.vmdk
Example for system called DC1:
vmkfstools -i scsi0-0-DC1.vmdk -d thin ./DC1-000001.vmdk
you should see the following output:
Destination disk format: VMFS thin-provisioned
Cloning disk ' scsi0-0-DC1.vmdk'...
Clone: 100% done.
5/ Now browse the datastore from the Vsphere client, right click the .vmx file.
In this example case DC1.vmx, and select Add to inventory and follow the steps in the wizard that pops up.
6/ Power-on the new virtual system and you will asked either by pop-up message or in the summary window of the new virtual system, whether the system is "copied" or "moved".
Select the "Copied" option and ok.
Explanation:
When the VMware files are backed up they are presented to NetVault:Backup by the VMware protocol VADP, in a different format than the one they normally are on the datastore .
VADP is the VMware backup interface that must be used when backing up Vm-systems. When a normal restore takes place the conversion is done automatically but if we restore the files for any reason we have to do a manual conversion as shown here.
Also see:
