Please read this document carefully

October 21, 2025

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.

• Before starting the ReZoom It! wizard, please make sure to use the backup image file that meets the following conditions:

  • Supported Products
    • ActiveImage Protector 2016/2018 for Hyper-V Enterprise
    • ActiveImage Protector 2022
  • Backup entirely including the following
    • System volume (disk)
      To back up stand-alone Hyper-V host
    • The volume (disk) that includes the configuration file of the virtual machine and virtual hard disk file, and the created snapshot.
      

• The ReZoom It! feature does not support the use of an image file created by HyperBack or Cold Backup.

• Restoring to an earlier version of a Hyper-V host than the backup source host version is not supported. Restoring to a Hyper-V host of the same or later version is supported.

• Restoring a selected virtual machine from backup image file from Windows Server 2008 (Hyper-V 1.0) is not supported. Windows Server 2008 (Hyper-V 1.0) is also not supported as a restore target.

• Restoring of virtual machines can be performed even if the processors of the backup source Hyper-V host and restore target Hyper-V host are of different manufacturers.

• The restore of a virtual machine, in which a differential virtual hard disk file created by using Hyper-V Manager is connected to, is not supported.

• It is recommended to use this feature in an environment where sufficient memory is available other than the main memory used for the live VM.

• ReZoom It! does not support a Linux guest virtual machine.

• ReZoom does not support a VM restored by using ReZoom (its recovery point becomes invalid).

• Cancel ReZoom task is not supported.

• ReZooming VMs in saved status is not supported.

• When a ReZoom task fails in error for some reason, please delete the VM ReZoomed from the target Hyper-V host and the files created in the ReZoom destination and folders. Then try again.

• When the VM of which the recovery point is grayed out, the ReZoom task fails due to missing ReZoom execution file, etc.
  When using a backup file created by enabling [Designate a separate image file set per disk] option with ActiveImage Protector, VM created on a disk other than Disk 0 cannot be selected as recovery target. When backing up by selecting multiple disks for backup source, you are recommended to disable the option.

• Please note when you restoring a VM with an ISO file connected to its virtual DVD drive, the VM together with the configured settings will be restored. Booting the VM will fail if the ISO file is not located in the same path as the backup source. After the recovery process completes, when the settings configured for the virtual DVD drive are corrected to the appropriate settings, the VM will become bootable.

• ActiveImage Protector Version 3.0.4 or earlier does not support the backup image files created by using Version 7.6.0 or later.

• You are not allowed to restore the same virtual machine simultaneously on multiple Hyper-V hosts.

• The backup files created by using ActiveImage Protector 2016/2018 for Hyper-V Enterprise is displayed in ReZoom It’ Setting window but incorrect value is indicated for the disk size.

• When applying a checkpoint to a VM restored with ReZoom and Secure Boot is enabled, the system may fail to boot up. In this case, please select a template other than [Microsoft Windows] in VM secure boot setting and then select [Microsoft Windows] again.

• When restoring to Hyper-V host other than the backup source, the VM with enabled TPM does not boot up. The VM becomes bootable by disabling TPM.

• When a VM name includes double-byte characters, restoring the VM will fail.

• Before restoring to Hyper-V host on a different computer, please configure firewall settings to allow [File and Printer Sharing]. If the firewall settings are configured via Group Policy, go to [Network] - [Network Connection] - [Windows Firewall] and enable [Allow inbound file and printer sharing exception].