Operational Defect Database
BugZero updated this defect 51 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 2146513
Unable to boot the restored P2V virtual machine in vSphere Data Protection
Last update date:
3/29/2024
Affected products:
vSphere Data Protection
vSphere
Affected releases:
6.1
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Unable to boot restored P2V virtual machines.Backups and restores are successful, but the virtual machine does not boot or start up.The Console displays a black screen or the error: Operating system not found
Cause
This issue occurs when physical and virtuals machines have unique entries in their VMDK descriptor files that are not restored from the backup. These entries indicate where the bootable disk is and where the bios information is stored in the VMDK flat file.
Resolution
This is a known issue affecting VMware vSphere Data Protection 6.1.x.Currently, there is no resolution.To work around this issue, retrieve the missing entries from the backup files on the appliance.Note: Axionfs service must be started to browse the backed up files in the appliance. Starting an FLR operation of the affected virtual machine starts the service and access the corresponding backups. Start the FLR operation of the affected virtual machine from the another virtual machine which is backed up by VDP using the advanced login mode. Using the Restore Client in Advanced Login Mode. For more information on advanced login mode, see the Using the Restore Client in Advanced Login Mode section in the vSphere Data Protection 6.1 Administration Guide. Select the virtual machine and the backup file.Wait for few minutes to complete the mount operation.Connect to VDP appliance using SSH.Navigate to the virtdisk‐descriptor.vmdk file to get the geometry parameters: /mnt/axion/[VirtualCenterDomain]/SubDomainPath(VirtualMachines)]/VirtualMachineName/by-number/BackupNumberUsedForRestore(000000#)/VMFiles/1/virtdisk‐descriptor.vmdk For example: cat /mnt/axion/vCenter01.local/VirtualMachines/virtual_machine/by-number/0000002/VMFiles/1/virtdisk-descriptor.vmdk # comment this is an avamar backup version=1 createType="vmfs" # Extent description RW 41966880 VMFS "virtdisk-flat.vmdk" # The Disk Data Base #DDB dbb.adapterType = "lsilogic" dbb.deletable = "true" dbb.geometry.biosCylinders = "5143" dbb.geometry.biosHeads = "255" dbb.geometry.biosSectors = "32" dbb.geometry.cylinders = "5143" dbb.geometry.heads = "255" dbb.geometry.sectors = "32" dbb.longContentID = "df32c0edf60450fd85e2c86dd5ab2e96" dbb.thinProvisioned = "1" dbb.toolsVersion = "9354" dbb.uuid = "60 00 C2 9f df 19 4b b0-07 8d 5f 75 a0 6f de d4" dbb.virtualHWVersion = "4" Note: This shows the backup from the original virtual machine. Make a note of the geometry.biosX and add to the restored descriptor file. Log in to the ESXi host with the restored virtual machine using SSH and power off the restored virtual machine.Go to the datastore where restored virtual machine is power on.Open the virtdisk-descriptor.vmdk file using a text editor.Add missing bios entries (from step # 3). Note: You see the missing geometry.bios file entries. Add missing entries: vi/vmfs/volumes/DataStore/RestoredVirtualMachineName/RestoredVirtualMachineName.vmdk Save and close the virtdisk-descriptor.vmdk file.Reload the virtual machine using the ESXi command in SSH. To reload the virtual machine: Get the VMID of the restored virtual machine by running this command: vim-cmd vmsvc/getallvms Use the ID obtained from the preceding step to reload that virtual machine: vim-cmd vmsvc/reload vmid Power on the virtual machine. Note: If you are restoring a restored virtual machine and the original virtual machine still exists, retrieve the missing information from the original virtual machine or replace the descriptor file by copying it from the original virtual machine to the restored virtual machine folder. For example, /vmfs/volumes/DataStore/OriginalVirtualMachineName/OriginalVirtualMachineName.vmdk
Related Information
vSphere Data Protection で復旧した P2V 仮想マシンを起動できない在 vSphere Data Protection 中无法引导已还原的 P2V 虚拟机
