VMDK2PHYS Help File
Backup a Physical Disk to a VMDK file
Restore a Physical Disk from VMDK file
Compare a Physical Disk and VMDK file
Main menu
Introduction
VDMK2TOPhys allow to transfer a virtual machine to a physical machine and vice versa
Description
VDMK2TOPhys has been designed to allow a quick switch between Virtual and Physical machine using a VMDK file as HDD container.
For example, if you have a virtual machine with Linux and you want to run the environment on a physical machine in order to improve the overall performance, you can use VMDK2PHYS to transfer the VMDK on a physical disk and boot from it in native mode. It is also possible to do the opposite, create a VMDK file from a HDD device and run it using VMware or VirtuaBox.
VDMK2TOPhys assumes that the VMDK will be copied on a Removable HDD Device (mainly USB devices). But, it is possible to transfer the VDMK on a HDD. The only condition is to be able to unmount the device in order to be able to write the physical device, sector by sector.
Drivers and Transfer issues
VDMK2TOPhys is not clever and won’t update the driver for you to take in account the new hardware environment.
Before to switch on the HDD support, you have set your environment in safe mode in order to be able to boot safely on the new HW.
For example, to switch a virtual Linux machine to a physical machine, you have first to remove vmware tools or specific drivers.
At the opposite, if you want to transfer a physical Linux machine in a virtualized environment, you have first to remove specific drivers such as NVIDIA drivers/sound card /etc….
As soon as the machine is transferred in the new virtual or physical environment, you can re-install drivers for native or virtualized VM in order to increase the overall performance ( disk/graphic/etc..)
Disk Partition and Lost data
VDMK2TOPhys proceed to a sector by sector copy on or from a physical disk. This means that the target disk will be completely erased and replaced the VMDK content. For example, if there are several partitions in the target HDD, and the VMDK contains only one partition, after the transferee, all partitions in will be erased.
Device Size compatibilities
The size of the target HDD must be at least equivalent to the VMDK size, if it is not the case, the tool will display a warring you can ignore it or not, but the result after transfer won’t be guarantee. If the VMDK is smaller, the transferee will be ok and it will be possible to enlarges the partition to the full disk or create a second portion right after the VMDK partitions. If the VMDK is bigger than the target partition, the result IS UNPREDICABLE depending sectors occupied in the VMDK. The partition table will be corrupted, but it is possible to fix the corruption using an appropriated tool such as TestDisk/Gparted/or equivalent tool.
Source Disk & All disk
The source disk selector shows all physical HDD available on the machine, again, the tool has been designed to transfer VMDK on USB/Removable devices, but some removable devices are not identified as a removable, but fixed.
To see all Hard disk on the system, you can check “All disk” check box in order to select hidden HDD. A physical HDD must be unmounted to be able to write it. So, during the writing, the tool may display an Error because it is not able to unmount the device.
For example ( Physical0 because Windows uses it. This operation not possible, except if you from boot a live CDROM).
VMDK selector:
The VMDK selector allows selecting the target or source VMDK. Don’t set the VMDK file in the Target Physical disk, otherwise, the Tool couldn’t unmounts the HDD device.
Verify
After a transfer, the tool can optionally verify if the VMDK and physical device are equivalent. Check / or uncheck this box to allow verification.
During the transfer
It is possible to cancel the transfer using the cancel button that appeared close to the progress bar, when the user cancel the transfer operation, the result of the transfer is supposed corrupted.
Backup a Physical Disk to a VMDK file
If the dialog is grayed, it is because of the system has not detected any USB HDD device. You can see all HDD disk in your system by checking “all disk” check box, but these disk may be undismountable and will cause a fails during the backup.
Then you have to select a destination for the VMDK using the edit box or the file selector.
Finaly, you must push the button to proceed the backup. You can optionally check the verify box if you want that the tool check the VMDK with the physical disk after the backup
To finalize the virtualization using vmware, you have first to create a virtual appliance , then replace the original vmdk by the vmdk you have previously backuped
Restore a Physical Disk from VMDK file
Select the source VMDK using the edit box or the file selector.
Then you have to select a destination HDD using the drop list. The droplist shows only HDD available on your system.
If the dialog is grayed, it is because of the system has not detected any USB HDD device. You can see all HDD disk in your system by checking “all disk” check box, but these disk may be undismountable and will cause a fails during the backup.
Finaly, you must push the button to proceed the Restore. You can optionally check the “verify” box if you want that the tool check the VMDK with the physical disk after the Restore
Compare a Physical Disk and VMDK file
The Compare menu allow to Compare sector by sector a VMDK file and a physical HDD. You have first to select the source VMDK.
Select the source VMDK using the edit box or the file selector.
Then you have to select a destination HDD using the drop list. The droplist shows only HDD available on your system.
If the dialog is grayed, it is because of the system has not detected any USB HDD device. You can see all HDD disk in your system by checking “all disk” check box, but these disk may be undismountable and will cause a fails during the backup.
Finaly, you must push the button to proceed the comparison. The tool will display an error message if both supports are not rigorously exact.