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.
At 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. At an enterprise level, you could recover an entire network environment in minutes.
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. The type of virtual machine to create is automatically detected by viBoot based on the virtualization software installed on the host.
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 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. The data for the disk is retrieved from the Macrium Image File by the Macrium Virtual Disk Provider filter driver as required. Because the data is not stored with the VHDX/VMDK, it size will never exceed a few megabytes. The second VHDX/VMDK file is a standard differencing disk that will receive any modifications made to during the lifetime of the virtual machine.
As with any differencing difference file (VHDX or VMDK), this file can grow dramatically in size, depending on the usage of the virtual machine.
These disk files (VHDX or VMDK) are stored in the designated Macrium viBoot repository and remain open until the Macrium viBoot virtual machine is deleted from within viBoot.
Note: The default location for the viBoot Microsoft Hyper-V VHDX files is C:\ProgramData\Macrium\viBoot. This is configurable from within the Macrium viBoot UI.
Both VHDX and VMDK files related to VirtualBox VMs are stored under C:\ProgramData\Macrium\viBoot\VirtualBox
Note: viBoot only supports Microsoft’s Hyper-V and VirtualBox running on a minimum of Windows 8.0 or Windows Server 2012.
Switching between Hyper-V and VirtualBox
viBoot can be switched between Hyper-V and VirtualBox mode using the ‘Tools’ menu:
Note: VirtualBox less than v6.1.4 cannot be run on Windows where Microsoft Hyper-V service is running.
Microsoft Hyper-V feature must be disabled for VirtualBox 6.0.xx to function. Please run "bcdedit /set hypervisorlaunchtype off" after disabling Hyper-V feature from "Turn Windows features on or off"
Macrium viBoot will be restarted after changing Hypervisor mode. This doesn’t affect the state of existing VMs, whether they are running or not:
If VirtualBox v6.1.4 (or later) is installed alongside Microsoft Hyper-V, VMs will not run with optimum performance.
See the VirtualBox Change Log for more information on this.
The current hypervisor type is shown in the application title bar:
Booting an image directly from Macrium Reflect
An image that contains the Windows System and Boot partition(s) can be directly booted from the 'Restore' view in Macrium Reflect.
|MBR - Master Boot Record||Boot partition: This may be the same partition as drive 'C:' but is likely to be a separate small (100 to 300 MB) partition named the Microsoft System Reserved partition or MSR. |
Windows partition: This is the partition that contains the Windows OS and will be drive C:
|UEFI - Unified Extensible Firmware Interface||UEFI System Partition: A small FAT32 formatted partition that doesn't have a drive letter.|
Windows partition: This is the partition that contains the Windows OS and will be drive C:
If an image contains the partitions required for booting then the image will show an active 'viBoot' Icon:
Otherwise the icon will be disabled:
To boot an image directly with viBoot.
- Click the 'Existing Backups' tab.
- Select the bootable image.
Click the 'viBoot' icon.
Note: If viBoot cannot run on your Windows installation then you will receive an error message indicating the reason(s):
- If viBoot can launch, the viBoot Hyper-V/VirtualBox settings dialog will start.
- Make any changes to the VM properties and click 'Finish'
The VM will now start and boot directly into Windows.
Starting the viBoot create Virtual Machine Wizard from Macrium Reflect.
Take the 'Restore' > 'Launch Macrium viBoot' menu option
Or, click the 'Launch Macrium viBoot' task link on the Existing Backups tab.
This will start the viBoot Virtual Machine User Interface.
Launching viBoot as a standalone application
viBoot is installed by default during the standard Macrium Reflect installation and can be started using the installed shortcut:
The Macrium viBoot main window allows you to see at a glance, which Macrium Reflect image files you have mounted (2), and which virtual machines are connected to those drives (1).
The “Virtual Machines” view (1), displays the name of the viBoot created virtual machine, the current state of the virtual machine (Off, Running, etc) and the current CPU usage of the virtual machine. Selecting a Hyper-V virtual machine in the “Virtual Machines” view (1) will update the “Mounted Images” view (2) to list the Macrium Reflect images that are being referenced by the virtual machine.
The “Mounted Images” view (2), displays the path of the image file(s) used to create the virtual drive(s), the physical drive number assigned to the drive by Windows, the partition type of the drive (MBR or GPT) and the drive capacity.
The "Log" view (3), shows a record of the actions taken by viBoot.
Macrium viBoot can only monitor the state of virtual machines and drives while it is running. Clicking the Windows close button will close viBoot.
Main Window Commands
Macrium viBoot menu:
|Menu Item||Sub Menu Item||Description|
|Virtual Machine||Connect||Connect to a virtual machine.|
|Backup...||Backup a powered off virtual machine.|
|New...||Displays the viBoot Wizard which allows you to create a new virtual machine.|
|Edit...||Allows you to modify existing virtual machine settings such as adding additional mrimg into the VM.|
|Delete...||Deletes the currently selected virtual machine and allows you to backup any changes to the data that have been made.|
|Start||Starts the currently selected virtual machine.|
|Shut down||Shuts down the currently selected virtual machine.|
|Turn off||Turns off the currently selected virtual machine.|
|Pause||Pauses the currently selected virtual machine.|
|Reset||Resets the currently selected virtual machine.|
|Exit||Exit the Macrium viBoot application.|
|Tools||Show Log||Toggles the display of the Log window.|
Configure the virtual machine repository folder, and logging options.
|Refresh||Instructs viBoot to refresh it's view of the virtual machines and mounted images.|
|Hypervisor||Allows you to choose between Hyper-V or VirtualBox Hypervisor when both are available.|
|Help||Contents...||Displays this help content.|
|About Macrium viBoot...||Displays the viBoot version and copyright notice.|
You can right-click on the virtual machine pane to display the "Virtual Machine" menu as a context menu.
Macrium viBoot toolbar:
|New - Displays the viBoot Wizard which allows you to create a new virtual machine.|
|Edit - Displays the viBoot Wizard which allows you to modify existing virtual machine settings.|
|Deletes the currently selected virtual machine and allows you to backup any changes to the data that have been made.|
|Backup a powered off virtual machine.|
|Refresh the list virtual machines and states.|
|Options - Configure the virtual machine repository folder, and logging options.|
|Help - Displays this help content.|
Macrium viBoot Wizard
The Macrium viBoot Wizard will configure and start a Microsoft Hyper-V virtual machine from one or more Macrium Reflect image files.
The "Welcome" page provides a brief introduction and explains some of the limitations of virtualization.
Select Image Files allows you to add one or more Macrium Reflect image files to be used for the virtual machine.
For VirtualBox VM
If creating new VirtualBox VM, below dialog box will show "VirtualBox VM Settings" to select VirtualBox VM settings instead of Hyper-V VM settings.
The first boot-able disk will be marked as the boot disk. If there are multiple disks that are boot-able, these can be set to be the boot disk by selecting the disk and clicking the "Set as Boot" button.
Hyper-V or VirtualBox VM Settings allows you to configure the virtual machine. The RAM and CPU are limited to match the host computer. If the number of processors is set to "Automatic", viBoot will interrogate the Windows settings from the image files to set the correct number of processors. A Virtual Switch of "<None>" ensures that the new virtual machine is not connected to the network. "Automatically power on the virtual machine after creation" checkbox is selected by default. By unchecking, user can just create a virtual machine without starting it.
Delete Virtual Machine
Virtual machines can be deleted from viBoot when the virtual machine is turned off. When the virtual machine is deleted from viBoot the virtual drives will be dismounted and the virtual machine removed from Hyper-V. Prior to deletion viBoot allows the virtual machine to be backed up.
If a viBoot virtual machine is deleted from Hyper-V, the virtual drives will still be mounted. viBoot will list a virtual machine called "Unassigned Virtual Disks" that can be deleted to dismount the virtual drives.
Note: When you delete a virtual machine the Macrium Reflect images used to create the virtual machine are not deleted.
The “Options” button on the Macrium viBoot main toolbar, will display the “Options” dialog box. From here you can modify some of the behavior of Macrium viBoot.
The “Virtual Machine Repository” specifies the folder that Macrium viBoot will use to store Virtual Machine configurations and the virtual machine drive cache. ViBoot will move existing virtual machine configurations and associated files to the new location if it was changed after creating virtual machines.
Macrium viBoot writes a log of actions taken by the application. This file is saved to "%LOCALAPPDATA%\Temp\Macrium". The log file is configured by the following options:
Log level - Controls type of information written to the log file:
Maximum number of files - Number of log files to keep before purging. A value of zero will disable this check.
Days to keep - Log files older than the specified number will be purged. A value of zero will disable this check.
Maximum log file size(MB) - Maximum file size for the log file, before a new log file is created. A value of zero will disable this check.
Macrium viBoot demonstration video