Please carefully read this document

Revised on April 22, 2020

This document contains information about the limitations to the use of the product and special attentions to pay.
You are recommended to read through this document before using this product.

For system requirements, please visit System Requirements.

Precautions to observe

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

• Please refrain from performing the following operations while a virtual machine booted from a backup image is up and running on hypervisor.
  • Uninstallation of the product
  • Shut-down, restart, sleep the computer on which the product is installed.

  In the event that you perform the above operation, the backup image may be kept mounted as iSCSI disk on the host on which hypervisor runs or the virtual machine may remain undeleted.
  If you get this problem, please manually detach the disk from iSCSI Initiator and delete the virtual machine from hypervisor.

• If you use a backup image file created by enabling [Separate image file for each disk] option, the virtual machine to boot 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. In this case please reassign available memory amount to the virtual machine, and try again.

• If disabling [Automatically open the connection console upon VM boot-up] on VMware Workstation Pro/Player and booting up an image, when the connection console is opened by a user, the console may be opened but connected to the booted system. In this case, please edit the boot setting and enable this option.

• If no optical drive is present on the computer on which hypervisor runs, when booting up a backup image on VMware Workstation Pro/Player, you will get the following messages.

  The specified device is not present on the host. Connection to the virtual device ide1：0 was not established. Do you want to try establishing the connection to the virtual device whenever the virtual machine is powered on?

  Select [Yes] or [No] to proceed with the further operation.
  *You will get this message whenever a backup image boots up.

• 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 when the virtual machine boots up will be set to on-line.
  *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, you are recommended to enable [Create Virtual Machine Compatible Image] option and back up the Linux system.

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

• When using a backup image of a system on mirror-configured dynamic volumes created by using HyperBack, you are recommended to attach the disk including the primary volume and boot up the virtual machine. If the disk including the secondary volume is attached, when resynchronization of the mirror-configured volumes starts up after the virtual machine boots up, the size of the differential file including the changes will be bloated.

• 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 of the system as such.

• When booting a virtual machine on Hyper-V, since [Network Adapter] will come to the upper most in [Boot Order] in [Firmware] setting, it takes long to boot up the virtual machine. In this case, please select [Hard Drive] for the upper most in Hyper-V Manager, 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 host on remote computer, 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 Windows latest Update to the computer which Hyper-V host runs on, and try booting up the backup image by HyperBoot again.
• When using an differential backup image, even if [Do not boot up from HyperBoot Recovery Point] option is enabled, the virtual machine is booted reflecting the changes made from the last time the virtual machine was running.

Functional Limitations

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

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

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

• Please make sure [Automatically open the connection console upon VM boot-up] option is enabled on VMware Workstation Player.

• Booting up a backup image on VMware Workstation Pro/Player or Oracle VirtualBox will fail if not connected to 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 remote computer, 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.

Others

• After uninstallation of the product, iSCSI Server may remain undeleted. If NetJapan product using this program is not installed on your computer, please manually uninstall the product.

• 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 keep running in incorrect condition after upgrading this product. 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 NetJapan 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.

  • ActiveImage Protector：BootCheck, HyperRestore, HyperStandby, File Recovery in HyperAgent, iSCSI Target Server
  • ImageCenter：BootCheck.