Please carefully read this document
Revised on Decenber x, 2023
This document contains information about the limitations and precautions on the use of the product.
It is highly recommended to read through this document thoroughly before installing ImageCenter.
For system requirements, please visit System Requirements.
Overview
-
Backup image files created by using ActiveImage Protector 2022 or earlier are supported.
-
Backup image files created by using vmGuardian are not supported.
- The following option settings are recommended if the replication options have been configured in ActiveImage Protector Linux v4.5.1:
- Allow Consolidation at this replication target: OFF
- Policy - Only replicate new image files to this target: ON
-
If the login credentials were changed using the [Change Credential] menu, a system restart is required for the changes to be applied.
-
Using [Add image folder] creates an invisible image managing folder in the added image storage folder. The image managing folder can be removed by deleting the image folder in the image list or by deleting the image folder by selecting [Agent Settings] -> [Image Folder]. Do not manually delete the image folder.
-
The iSCSI target server’s feature has to be disabled while uninstalling the product. Please make sure iSCSI initiator is disconnected before starting uninstallation of the product.
-
When upgrading from Version 4, the log information created in Version 4 will be purged.
- If accessing image folder added when upgrading to this version fails, it may take longer process time.
Dashboard
-
A consolidated Image set may not be selected if the consolidated image set and the image files are located in the same folder. If so, please move the consolidated image files to a different folder.
-
Double-clicking the [Run Now] button to start a scheduled task causes an error.
-
Reducing the size of the console window may cause misalignment of the displayed items.
-
Selecting Log ID in the [Task Log] tab before a sub-folder is created, returns a “-551” error. If this issue is encountered, browse “log” folder located under Install folder. When selecting a backup image file of multiple virtual machines created by using HyperBack, only one source information is displayed in source tab.
-
When ImageCenter is configured on local computer on which Actiphy StorageServer is set up and also on other dedicated computer, image file management format for Actiphy StorageServer’s bucket is different for both ImageCenter. As a result, when the bucket is selected as the target for both ImageCenter tasks, the bucket may not be properly under “external management”.
Create / Edit Task
-
After closing the dialog box that’s displayed when creation of a schedule ends with an error, the [Cancel] and [Back] buttons in the wizard become disabled. If this occurs, click the [x] button located in the upper right corner of the window to close the wizard.
-
When editing the replication target settings, a new Amazon S3 compatible storage provider cannot be added.
Verify
-
If Verify task is executed concurrently with another task (Replication task, Consolidation task), Verify task is always prioritized to execute first.
-
When both Actiphy StorageServer’s bucket and backup destination folder are specified for ImageCenter task, [Quick] is disabled from the wizard launched by selecting [Create New] in upper side of the console window. Select a backup destination folder from the image list to launch the wizard and [Quick] is enabled.
-
ActiveImage Protector Version 5.0.2 or earlier does not support the backup image files created by using ActiveImage Protector Version 7.0.2 or later. Quick Verify task fails in error -440.
Replication
-
If WebDAV is selected for a Replication target, the percentage of the completed processes remains unchanged from the start to the end of replication of the files. If multiple files are selected as the Replication source, then the progress bar makes gains for the percentage of processed images out of the total images only upon completion of the Replication task.
-
If WebDAV is selected for a Replication target, the Pause/Resume task option is disabled.
-
If a Replication task already exists and you right-click on an image in the list, the [Create Replication Task] in the context menu may not be grayed out.
-
When the [Keep target item same with source] option is enabled, the replication target is synchronized with the replication source according to the schedule of the replication tasks.
-
In the system environment with 8GB or more memory, network throttle does not work.
-
While configuring the replication target setting and Amazon S3 is selected, a bucket cannot be created.
-
Only east-2 region of object storage of Amazon S3 compatible storage “NIFCLOUD” is supported.
Consolidation
-
If cancelling a running consolidation task, the cancellation result of the task is not displayed on the console.
-
Please do not run consolidation task for the backup images created by enabling [Split image into xx MB files] option and directed to Actiphy StorageServer Version 1.0.0. When this option is enabled and consolication task is performed for the incremental backup files saved in Actiphy StorageServer, the consolidated backup image file, even though the file size exceeds the predefined threshold, is not split into “xx MB files” but gets corrupted. When Verify task is executed for every backup image files, the Verify task fails in error upon completion of the consolidation process.
BootCheck
-
Please configure the firewall setting to allow File and printer sharing and Windows Management Interface (WMI) when using Hyper-V on a remote host.
-
When using Hyper-V on remote host, iSCSI target server’s feature is enabled on the local host on which this product is running. Upon completion of the uninstall process, please disable iSCSI target server’s feature, if not required.
-
When the product is installed on Windows Desktop OS, BootCheck using Hyper-V on local host only is supported. BootCheck using Hyper-V on remote host is not supported.
-
The system requirements (OS, Boot Type, etc.) for the BootCheck feature conform to the requirements of the Microsoft Hyper-V host. Ex: Since Hyper-V does not support using uEFI to boot Windows Server 2008 R2 and Windows 7 x64, BootCheck will not work in these situations.
-
BootCheck supports image files taken of Windows XP/2003 or later created by using ActiveImage Protector for Windows Edition. BootCheck does not support the image files created by using ActiveImage Protector for Linux Edition.
-
BootCheck does not support image files taken of Windows 7 or later that do not include the active partition such as system reserved area.
-
BootCheck does not support image files created for the system of which the boot and system partitions are configured on separate disks.
-
If a reboot or shutdown occurs during the BootCheck process, the virtual machine created for BootCheck will have the status “Saving completed” when the system boots up. You will need to manually delete this VM. BootCheck does not support image files of a system configured on a dynamic volume is not supported.
-
Execution of a single BootCheck task requires 2GB of available memory space on the hypervisor. If sufficient available memory space cannot be allocated to the task execution, the BootCheck task goes into standby mode.
-
Even when the [If the BootCheck task failed for the latest image, try the previously created image] option is enabled, this feature does not work if the result of the BootCheck task was “Warning”.。
-
Executing BootCheck for the same image created by AIP and processed by multiple instances in ImageCenter from the same target host is not supported.
-
The information of the image file of multiple virtual machines created by using HyperBack is not correctly displayed in the Image Information tab of the wizard.
-
With E-Mail Notification enabled and the BootCheck task does not complete within the specified time-out period, you will receive an e-mail notification.
-
When time-out occurs and BootCheck for 32-bit OS using Hyper-V on remote computer fails, please uninstall [Actiphy Boot Check Option] (or [ActiveImage Protector Boot Check Options] from the remote computer on which Hyper-V is running, and try again.
Remote Connection
-
Connection only to a Version 5.0.0 or later agent can be established.
-
If the credentials are changed to communicate with a remote host after the connection to the remote computer is established, go to [Add New Agent] in the Agent List pane and re-establish the connection to the remote computer.
-
If an unintentional disconnection to a remote agent occurs, such as restart of remote host, etc., the displayed information in the console is not automatically refreshed. If performing an operation needed to obtain updated information from the connected agent, the disconnected agent returns a “-571 error”.
-
When a connected target is changed, the displayed items may be duplicated. If this occurs, restart the console.
Others
-
Displayed information may not be refreshed. If this occurs, restart the console.
-
If connection to an agent fails to establish, or too many images are listed, it may take time to display the information.
-
If the ImageCenter console is started in low resolution environment, the console may not be displayed in proper size.
-
When ImageCenter is started, IME may be disabled. There may be instances that by displaying the language bar, the issue resolves itself.
-
If only the console is installed and then the console is restarted after a connection with a remote computer is established, a window is displayed to establish a connection to an agent.