04-04-2013 07:19 AM
we have updated our vSphere Enviroment to 5.1.
Now the restore of a single vm- image failed with the following error:
[Critical] From: B2BARxxx@xxx"/Test" Time: 03.04.2013 10:40:38
Virtual Machine 'VM- Test': Error restoring item \a1f9f4e3-482d-4b7f-afcb-cbxxxxxxxxx0\%2Ftest\vms\
The VM is created fine and is visible in the vCenter. After the restore failed (at the end) the vmdk and the vmx are restored, but the vmx- file does not contain any reference to the vmdk. So I must add the vmdk manually to the VM.
04-04-2013 11:40 PM
have you installed the Site Specific Patch SSPNT700_017? This will enable support for vSphere v5.1. If not, request it from support and try the restore once again.
04-05-2013 01:00 AM
in this case you may open a case... I know that there is a problem in VMware that sometimes the vonfiguration of the VM cannot be backuped as expected, as there is a open lock on the file. Maybe you have the problem too and therefor you are not able to to the complete restore.
04-05-2013 06:09 AM
Thanks Daniel. The case is open :)
Some details from me:
- start the restore of a VM- Image (with one vmdk) from DP
- the VM is created in vSphere enviroment (the VMX)
- a snapshot is created (_DP_VEPA_SNAP)
- now the restore of the VMDK begins (at this time the VMX lookes fine, the VMDK ist presented in the VMX)
- the VMDK restore is completed
- disc consolidation succeeded (vmware log)
- reconfiguration of the virtual machine completed (vmware log)
- removing Snapshot (_DP_VEPA_SNAP)
- at this time the VMDK is not presented in the VMX- File but still restored on the VMFS5- Datastore
04-05-2013 06:14 AM
this is strange... and sounds like a bug...
So please open a case and let the community know how to solve it.
05-30-2013 09:24 PM - edited 05-30-2013 11:45 PM
Did you solved this problem?
I encountered a similar problem...
Seems that problem was due to 701 patch missing
Problem still there after 701 patch was installed.
10-11-2013 01:16 AM
We also encounter the same problem, first we thought it was a SAN issue, but we fixed that, we use DP 7.01 with the latest patches and VMware 5.1 update 1 and the same issue and we are now performing a Disaster Recovery test and cannot restore any Virtual Machine. Strange though that recovering the Virtual Machines by using network works, but we have so many Virtual Machines we want to recover them by using SAN. The SAN was at first hand not setup with zoning, but at second we did set it up with zoning, but did not matter anything.
[Critical] From: VEPALIB_VMWARE@backupserver "/XXXXXX" Time: 10/10/2013 1:30:08 PM
Virtual Machine NAME: Error restoring item \a1f9f4e3-482d-4b7f-afcb-cb16babe1980\%2FXXXXXX\vm
10-11-2013 03:57 AM
I just past what I already wrote you to allow other peaople to comment...
Regarding your VM restore problem, yes, this is a known problem - for VMware. Sometimes VMware cannot release the lock for the vmx file during the backup, hence it will not be restoreable. As far as I know from the environments I configured, the problem did not occur since I installed the April patches for DP 7 and ESX 5.1 is in place. If you already are on the latest patches and still have problems with the vmx files - HP might provide a hotfix to at least display a warning or critical messages during the backup when it is not possible to backup the vmx file. I had these hotfix requested for DP 6.2 some months ago. The workaround in this specific scenario is to document the settings for the virtual machine and to manually create a new machin, restore th data partitions to a temporary directory and import the vmdk files afterwards. Another workaround will be to have a cron job directly on the ESX server to collect all vmx files for all virtual machines.
12-02-2013 01:18 AM
We also installed update 7.03, but unfortunatelly it is not working yet, we allready opened a case with HP and we are still looking with HP for a solution.
12-02-2013 03:03 AM
1. In GUI select Clients menu
2. Select your Cell Manager host in clients list
3. Right click on CM host and select "Upgrade"
4. repeat 1-3 on all your clients
12-02-2013 05:22 AM
Okay, I updated everything, no luck, same situation. Then I removed DP from Vcenter server, re-installed from Backup server, re-imported it back into the Cell Server as a Vcenter. Tried to restore it, no luck same situation.
Omnicheck -patches - host xxxxxxx says everything is DP 7.03
So, maybe I need to install DP 8?