Because the data is not stored with the VHDX/VMDK, it size will never exceed a few megabytes. The data for the disk is retrieved from the Macrium Image File by the Macrium Virtual Disk Provider filter driver as required. The first VHDX/VMDK file is incomplete and only contains enough information to describe the disk layout and a signature to mark it as a Macrium viBoot VHDX/VMDK. When creating a new Hyper-V or VirtualBox virtual machine, Macrium viBoot will create two Microsoft Virtual Hard Disk (.VHDX) or VirtualBox (.VMDK) files respectively for each of the disks described within the selected Macrium Image file. The type of virtual machine to create is automatically detected by viBoot based on the virtualization software installed on the host. Macrium viBoot is now built upon new technology that allows it to instantly present a Macrium Reflect image file as a Microsoft Virtual Disk (.VHDX) or VirtualBox/VMWare (.vmdk) file. At an enterprise level, you could recover an entire network environment in minutes. Macrium viBoot enables you, to instantly create, start and manage Microsoft Hyper-V and VirtualBox virtual machines using one or more Macrium Reflect image files as the basis of the virtual machine storage sub-system.Īt a minimum, viBoot enables you to boot into the images you have made using Macrium Reflect, for validation purposes, or to retrieve data from old applications stored on a bootable image.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |