Please carefully read this document

Revised on October 24, 2023

This document contains information about the limitations to the use of the product.
It is recommended to read through this document thoroughly before using this product.

For system requirements, please visit System Requirements.

Precautions

• If upgraded from Versions 4.0 to 4.1, the version 4.0 differential file ( * .aix) is not migrated. When booting for the first time after upgrading, the virtual machine is booted from the recovery point specified in the configured settings.

• Backup image of Windows 7 or later must include the active partitions such as system reserved areas.

• Please refrain from performing the following operations when a virtual machine booted from a backup image on Hyper-V configured on a different host.

  • Uninstall of the product

  • Shut-down, restart, sleep the computer on which the product is installed.

  In the event that the above operation is performed, the backup image may be kept mounted as iSCSI disk on the host on which Hyper-V runs or the virtual machine may remain undeleted.
  If this occurs, manually detach the disk from iSCSI Initiator and delete the virtual machine from the hypervisor.

• If a backup image file was created with the [Separate image file for each disk] option, the booting virtual machine may include only the disk in the image corresponding to the image file type and the number assigned to the selected recovery point.
  If the image file is consolidated in a file set or a differential file is created after writable Mount Image operation, please remember the above.

• If you assign the memory exceeding the available amount on the computer on which the hypervisor runs to a virtual machine, the virtual machine may fail to boot up. If this occurs, reassign any available memory to the virtual machine and try again.

• When configuring the image boot settings while the virtual machine is attached to multiple disks, the settings will be changed so that the disks attached to the virtual machine will be set to on-line when the virtual machine boots.
  *When the settings are not properly changed and any disk remains to be off-line, please change it to on-line if necessary.

• If using a backup image of Linux system, it is recommended to enable the [Create Virtual Machine Compatible Image] option and back up the Linux system.

• To add a hypervisor on a different host, log in as (domain or built-in) administrator, a user in Domain admin group, root or other user account having the equivalent permission.

• Depending on the hypervisor, the virtual machine’s startup conditions should differ. For further details, please contact the provider of the hypervisor. For example, since Hyper-V does not support using uEFI to boot Windows Server 2008 R2 and Windows 7 x64, the virtual machine does not boot up from the backup image.

• When booting a virtual machine on Hyper-V, the [Network Adapter] will be on top in the priority [Boot Order] in the [Firmware] setting. This puts a delay in the boot process of the virtual machine. In this instance, please select [Hard Drive] for the top of the priority in Hyper-V Manager settings. Submit Ctrl+Alt+Del command and restart the virtual machine.

• When booting a backup image created according to the still effective backup schedule setting configured with ActiveImage Protector Linux Edition, the backup task is executed whenever the configured schedule conditions are satisfied. Please remember this if you boot a backup image as such while the destination is accessible.

• If failed with “Error Code -944：Mounting iSCSI target failed.” on Hyper-V configured on a different host, please try the following:

  • Select [Auto Boot] to configure the boot setting of Microsoft iSCSI Initiator Service on the computer which Hyper-V host runs on, restart the computer and try booting up the backup image by HyperBoot again.

  • Apply the latest Windows update to the computer which the Hyper-V host runs on, and retry booting up the backup image using HyperBoot.

• When using an differential backup image, even if [Do not boot up from HyperBoot Recovery Point] is enabled, the virtual machine is booted reflecting the changes made from the last time the virtual machine was running.

• Even when enabling [Change boot entry of EFI system] option, booting a virtual machine from a Linus backup image may fail.

• When migrating a virtual machine booted with [Enable Migration feature (vMotion) of vCenter] enabled, [Relocation of virtual machine] may fail in error. In this case, retry migration.

• Booting up a virtual machine may fail if using a backup image of a Linux system which multiple disks are connected.

• When enabling [Enable Migration feature (vMotion) of Hyper-V] options and booting from the backup image of Linux system, please make sure [Fixed] is selected for [Virtual Hard Disk Type]. If [Dynamic] is selected, the virtual machine may not boot up properly or the migrated system may not operate correctly.

• If using a backup image of the system volume on mirror-configured dynamic disk, only booting the system is supported. If using a backup image of the system volume on mirror-configured dynamic disk created by using HyperBack, it is recommended to boot up the virtual machine by connecting the disc including the volume on primary disk only. If booting up the virtual machine by connecting the disk including the volume on secondary disk, the differential file saving the changes may expand when synchronization of mirror-configured volumes starts after booting up the virtual machine.

• If using a backup image with data volume on mirror-configured dynamic disk, you may not be allowed to access the mirror-configured volume after the system boots up. In this case, please perform [Re-activate the volume].

Functional Limitations

• The changes made for the virtual machine settings after boot-up on hypervisor are not saved.

• Suspending operation of a booted virtual machine is not supported.

• Booting up a backup image of Linux LVM including multiple VG is not supported.

• Booting up a backup image on Oracle VirtualBox will fail if not connected to the network adapter.

• If this product is installed on Windows Server 2012 R2 and when booting a backup image as a virtual machine on Hyper-V on a different host, the connection console will not be displayed. You need to operate the virtual machine on Hyper-V on which the virtual machine was booted up.

• When adding a hypervisor, the following roles will be enabled on the host which this product runs on. After uninstalling this product, please disable the following roles if not required.

  • Hyper-V：iSCSI Target Server

  • VMware vSphere：NFS Server

• Double-byte characters cannot be used to specify the virtual machine name.

• Booting VM from backup file of LVM system backed up by using ActiveImage Protector 2022 Linux is not supported.

Others

• If installing this product in the system environment where ImageBoot is configured, ImageBoot will be automatically deleted. Please note that the settings configured for ImageBoot will not be migrated.

• Upgrading may take longer.

• Before upgrading this product, please make sure that the virtual machine is shut down. If you upgrade this product while a virtual machine is up and running, the system of the virtual machine becomes disabled or the virtual machine may be running incorrectly. In this case, please select [Power off] to shut down and restart the virtual machine (the changes made while the virtual machine was running will be lost.) If the Actiphy product is installed on the same computer, please make sure that the following feature is not running before starting to upgrade this product. Otherwise, the feature may not work properly.

  • ImageCenter：BootCheck.

• When upgraded, the proxy server’s user settings are not migrated. Upon completion of upgrading process, please recofigure the user settings.