Release Note

Revised on June 23, 2020

Version 4.0.6.415 (June 24, 2020)

Improved the process speed when booting a backup image on Hyper-V host on a remote computer.
Added optional function to boot a virtual machine without reflecting the changes made from the last time the virtual machine was booted by using HyperBoot.
ESXi 7.0 is now supported.

When a backup image file is selected from the destination specified by using double-byte characters, booting the image file failed.
In some system environment, unmounting the backup image failed even when the virtual machine shut down.
If [Always use the latest recovery point] option is enabled, the time stamp (date/time) for the recovery point is not correctly indicated in some cases.
When selecting ESXi host, [Find By Uuid] task logs continue to be recorded on ESXi host.
When a virtual machine continued to run on ESXi host for certain period of time, the virtual machine falls under any one of the following conditions:
- [Power off] does not work.
- Connection console cannot be not displayed.
- Behavior of Web donsole on ESXi host gets heavy, or the connection is disabled.

Enhanced the stable behavior.
Improved the console and enhanced user friendliness.
Added optional function to boot a virtual machine while [Migration] feature of vCenter is available on VMware ESXi under vCenter.
Added an option to keep the saved changes when deleting the boot settings of a backup image from the list.
You can close the console while a backup image is booted as a virtual machine.

When editing the boot settings for a virtual machine, the settings configured not to attach any disk can be saved.
When a booted virtual machine is shut down by selecting [Power-off] in this product, [Power-on] is enabled even when post-processing has not completed on hypervisor.
When a virtual machine is live, if the console is forcefully terminated and restarted, the status is not correctly indicated.
Booting up a backup image of Linux LVM which boots up from VG created on PV spanning multiple disks failed.
Booting from a backup image of Windows system in mirror-configured dynamic disks created in md format (multiple disks in one image) failed.
When booting a backup image created according to the still effective backup schedule setting configured with ActiveImage Protector Windows Edition, the schedule works on the virtual machine booted from the image.
- ActiveImage Protector service is set to [Manual] start on the booted virtual machine.
- Please remember that the backup task is executed whenever the effective schedule conditions configured with ActiveImage Protector Linux Edition are met.