Summary

What is HyperBoot™?

HyperBoot™ bypasses the lengthy, resource intensive, and cumbersome physical to virtual conversion process and boots directly from the backup file. Changes made while running virtual machines from backups are saved as differential files which updates the backup to it’s most current state. HyperBoot™ makes the backup useful as a “Spare Wheel” while repairing or upgrading hardware, testing software changes, or testing upgrades prior to deployment.

 

 

	Boot backup files as a VM in as little as 2 minutes Be DisasterReady and boot from any point-in-time backup image (full or incremental) as a virtual machine in minutes, providing an alternative availability solution to bridge the gap between disaster and recovery. Eliminate business downtime caused by lengthy physical to virtual conversions or restore processes.
	As a “spare wheel” to run servers temporarily HyperBoot™ can be used as a “spare wheel” to run servers temporarily in the event of failure or while hardware is repaired or upgraded.
	Virtual Disk Emulator enabling emulation of a backup image HyperBoot provides Virtual Disk Emulator enabling emulation of a backup image as a virtual disk in VHDX or VMDK format. The emulated virtual disk is hardly distinguishable from the original virtual disk on hypervisor, so that hypervisor’s storage migration features including Hyper-V Live Migration, vCenter vMotion, etc., are fully supported. While the virtual machine booted by HyperBoot is running, the emulated virtual disk may be migrated to the “real” virtual disk and used as the restored virtual machine.
	Supports Hyper-V, VMware and VirtualBox Boots backup files from any hypervisor environment as a virtual machine using Oracle VirtualBox, VMware WorkStation, VMware ESXi, VMware Player, and Microsoft Hyper-V.
	“Recovery on boot” Use VMware vMotion Live Migration to effect “recovery on boot” of a HyperBoot™ virtual machine to a hypervisor in a production environment.
	Free and included with ActiveImage Protector™ HyperBoot™ is entirely free-of-charge and is included with the ActiveImage Protector™ trial and full software solution.

 

 

System Requirements

Hardware

Before using the hypervisor on the local computer, please make sure that the system requirements for the hypervisor are met.

Main Memory：
1024MB or more

 

Hard Disk：
1.2GB or more of available disk space is required.

Please make sure that sufficient disk space is available, since the changes made after booting up an image are saved in install folder by default.

 

Internet Connection

Required to check for an update available.
If you use a proxy server for internet access, select [HyperBoot Setting] and configure the proxy setting.

 

Operating System

To install the product

Desktop OS：
Windows 10 (64 bit) *Supports Windows 10 only when using hypervisor configured on local host.

 

Server OS：
Windows Server 2012 R2 or later

 

To boot up backup image files

OS supported to back up by using ActiveImage Protector.
*Hyper-V and ESXi are supported to boot Linux system image.

 

Supported Hypervisor

Microsoft Hyper-V：Windows Server 2012 R2 or later

VMware vSphere ESXi：Version 6.5, 6.7, 7.0
*The free license version of ESXi host is not supported.

VMware Workstation Pro：Version 14, 15

VMware Workstation Player：Version 14, 15

Oracle VirtualBox：Version 5, 6