Readme
Revised on September 14, 2017
This document contains the important information regarding the
use of this product. It is highly recommended that you read this
document carefully before using this product.
* For system requirement, please visit here.
Table of
Contents
Precautions
to observe when upgrading/updating
Basic Points
Limitations to the
use of Hyper-V Enterprise Edition
Backup
Deduplication
Compression
Recovery
Image File Management
Consolidation
and Archiving Incremental Backup Files
Virtual Conversion
for VMware
products (conversion to virtual machine)
for
VMware products (conversion to virtual disk)
for
Microsoft Hyper-V (conversion to virtual machine)
for
Microsoft Hyper-V (conversion to virtual disk)
Boot
Environment Builder (Linux)
Boot
Environment Builder (Windows PE)
Boot
Environment (Linux)
Boot
Environment (Windows PE)
Image Explorer
Push Installer
Remote Client Management Console
Connect to Remote Host
Preference
Other Utilities
ReZoom (Restore Virtual Machines)
IT Pro Edition Creator
Others
- Please be aware of the
following restrictions before upgrading from version 3.5.
- It is highly recommended
to restart the system upon completion of the upgrading process.
- The connection history
with the remote console is not migrated.
- It is recommended to
delete the PreBoot environment, if any before upgrading.
- When migrating schedules
configured with the storage destination settings as network
shared folders, you will be prompted to enter credentials after
upgrading. The replication feature is disabled when upgraded.
- With migrated schedules,
the [Send Task Summary] option in [Preference] -> [E-Mail
Notification] is enabled. If this feature is not needed, disable
this option after upgrading.
- If using for Hyper-V
Enterprise, upgrading from an earlier version is not supported.
It is recommended to recreate the schedules since the
requirements for creating a backup image files have changed from
version 3.5 to use the ReZoom (Restore Virtual Machines)
feature.
- Since the upgrading
process includes un-installation of the product, upon
completion, a system reboot is required. In the event that an
error occurs during the upgrade process, the product is
recognized as uninstalled. If this issue is encountered,
re-install the program by using the update files.
- If the product's package
includes the patch program, please apply the patch upon
installation of the product.
- Before applying the patch
program, ensure that no task such as backup task is running.
Back to
Table of Contents
- ActiveImage
Protector supports up to the maximum number of 128 disks per
system.
Up to the maximum number of 24 volumes
per disk are supported.
- After the first image file was created, if the
compression rate is changed in backup schedule setting window,
the consequently executed backup task creates a base image file.
This product does not support image file set that has mixed
image files of different compression rates.
- Please
ensure that you select an image file in image file set that is
not in use on any other host. If you select an image file in
image file set that is in use on another host, the task may
fail in error or may not be completed successfully.
Ex. 1: Restore incremental image file
included in image file set that is in use for Consolidation
process on another host. → Restore task failed with error.
Ex. 2: Consolidate image files in an image file set mounted as
writable on another host. → Consolidation task is logged to be
successfully completed in history, however, the files are not
consolidated.
- Backup images version "208" created with
ActiveImage Protector Version 3.5 SP7 or later are supported.
* ReZoom feature（Restore Virtual Machines) is not
supported.
- If login credentials to access a network shared
folder are changed, you may be prompted to restart the system.
- Please be aware of the
following restrictions before upgrading from version 3.5.
- You are recommended to
restart the system upon completion of upgrading process.
- The connection history
with remote console is not migrated.
- You are recommended to
delete the PreBoot environment, if created, before upgrading.
- To migrate the schedules
configured with the settings for network shared folder as the
storage destination, you will be prompted to enter credentials
after upgrading. Replication feature is disabled when upgraded.
- With the migrated
schedules, [Send Task Summary] option in [Preference] - [E-Mail
Notification] is enabled. If you do no need to use this feature,
please disable this option after upgrading.
- Upgrading from an earlier
version to Hyper-V Enterprise version is not allowed. Since the
requirements for creating the backup image files to use with AIP
Version 3.5 are different with ReZoom feature (Restore VM), you
are recommended to create the schedules again.
- Since upgrading process
includes uninstallation of the product, upon completion of
upgrading process, system reboot is required. In the event that
an error occurs during upgrading process, the product is
recognized to be uninstalled. If you encounter the problem,
please re-install the program by using the update files.
Back to
Table of Contents
Hyper-V Enterprise Edition does not support the following
features:
- Execution of a backup task at system shutdown
- Virtual conversion from physical disk
- Virtual conversion from a backup image file to
VMware target host
- Push Installation
Back to
Table of Contents
- Backup of Disk does not support dynamic disk.
- In order to execute a hot backup including
snapshot of a database using the Oracle VSS writer in the system
environment in which the Oracle Database 11g for Microsoft
Windows is configured, the backup source database must be up and
running in ARCHIVELOG mode.
Refer to the following URL in the Oracle Database Platform Guide
for a description on how to perform Database Backup and Recovery
using VSS.
http://otndnld.oracle.co.jp/document/products/oracle11g/111/windows/E05885-02/vss.htm
- If an image file including system volume created
by a scheduled task is restored and intended to boot for the
first time, the following error may be logged. The following
error does not affect consistency of the restore source image
file and restored system.
"Creation of image file by using
<Schedule Name> did not successfully complete."
- While backup schedule settings are configured
with [Separate image file for each disk] option enabled, and the
disk number of the backup source is changed or replaced, base
(full) backup of the above mentioned disk will be created
instead of incremental backup by the consequently scheduled
backup task.
- Boot Environment (Linux) does not recognize
virtual disks converted from ReFS volumes and storage spaces. Do
not select these types of virtual disks as converted from ReFS
volume and storage space for the storage destination to save
system backup image file.
- Please remember the following when backing up
CSV on Windows Server 2008 R2:
- Backup of a disk or a volume with no ownership
is not supported. Backup supports source disk or volume with
ownership.
- Please make sure every virtual machine on CSV is
shut down before you start backup task.
- Only full backup is supported. Incremental
backup is not supported.
- Backup by Disk does not support source disks
including CSVFS volume.
- Backup of CSVFS volume in combination with other
file system volume is not supported.
- In the event that anotehr
backup task for the same CSVFS source volume is scheduled to run
at the same time on a different host, go to [Preference] -
[General] and ensure that [Skip CSVFS volume with no ownership]
option is enabled. If the option is disabled, depending on the
status of the source volume's ownership, execution of a backup
task may cause VSS confliction.
- Online backup on Windows 10/Server 2016 causes
Event ID513 error logged in Windows Event Log.
- In case of backing up dynamic volume configured
with volumes on multiple disks, the image file name is not
correctly displayed in Summary page of the Backup Wizard.
- (6685) After a base backup image file is created
in new backup image generation set, and the image file is
corrupted or lost for some reason but Reconcile function is
executed to create an incremental image file, the image file
forms a sequel to the incremental image file in prior generation
of image set.
- (6700) If a backup image file is successfully
created but an error is logged in task log, the error is
indicated in the [Dashboard] - [System Protection Status] and
may be regarded as a target for an alert.
- Backup image files which includes a volume
formatted with a file system other than NTFS cannot be restored
to extended size.
- If the schedule is defined and applied within
five minutes or less before the scheduled start time, the first
scheduled task will not be executed according to the schedule.
- If a dynamic disk is specified as restore
target, the entire disk cannot be restored. Restore of an
existing volume on a dynamic disk is not supported.
- When the following operations are performed to
the backup source volume to create a backup image, a full (base)
backup must be executed before running the subsequently
scheduled incremental backup in order to update sector tracking
information on the volume.
- Resize volume
- Format volume
- Delete $AIPMAP on volume
- Execute stoptracking command using
AipControl.exe
- Before performing a cold backup of the disk
encrypted by using Microsoft BitLocker Drive Encryption from the
system on the product media, you need to decrypt the disk in
Windows, as an encrypted disk cannot be backed up.
- Combined use of this software with another
product which uses VSS is not supported. If another product
which use VSS is already installed, please ensure that AIP tasks
are not scheduled while another product using VSS is running.
- If a host machine is restarted while a backup
task is being executed, restart of the machine does not resume
the aborted backup process. Re-execute the same backup task
again.
- If the destination to save backup image files in
backup schedule setting is changed, the file name for the base
and incremental backup image files in the new destination may be
duplicated with the existing image file name from the former
destination. The consistency and sequentiality of the created
image files are guaranteed for an image file set saved in a
single destination.
- While consolidation task
is being executed for incremental image file set on host machine
other than backup source machine, incremental backup shall not
be executed to create source incremental backup images for the
image file set. Incremental backup task shall be executed at the
subsequent incremental backup schedule.
- Backup for exFAT volume becomes full sector
backup (Base and Incremental).
- You cannot specify a letter or a symbol other
than single byte alphanumeric characters for the path of
temporary work folder to use the Deduplication Compression
feature.
- Execution of a task using a backup image file
created with Deduplication Compression feature enabled takes
longer process time than a task executed using a backup image
file created with Common Compression feature.
Back to
Table of Contents
- Backup images cannot be restored to disk which
differ in sector size of the backup source.
- When a number of hard
disks are connected to the system, and there exists a hard disk
with the same signature as the restore source disk other than
restore target, please select [Use disk signature of restore
target] to restore.
- Restore to two or more than two bare-metal hard
disks connected to the system is not supported.
- When the MBR or first track is restored, MBR or
first track in base backup image is restored.
- [Restore drive letter] option is not supported.
- Restore tasks restoring
to bare metal disk or restoring multiple items at a time may end
with -701 error. If you encounter this problem, please retry the
restore task again.
- In boot environments
built by using Windows 10 ADK, please select the restore target
from the context menu. Drag-and-drop of restore source to the
restore target is not supported.
- If Restore by Disk is
selected to restore an image of MBR disk to a bare metal disk
larger than 2TB at the same proportion as the original,
restoring the volume up to 2TB at the maximum is supported.
- Partitions created by
[Create Partition] are unformatted.
- Overwriting restore to
the partitions created by [Create Partition] cannot be processed
by a single task execution. Upon completion of a restore task,
you need to execute another task to overwrite to the created
partition.
- Partition Creator
function does not support dynamic disk.
- Restoring dynamic volume
only supports overwriting restore to existing volumes on dynamic
disk and restore by volume on basic disk.
- Recovery of the system on
mirror-configured dynamic volume is not supported.
- You cannot restore split
image with deduplication compression from optical media.
- You cannot restore uEFI
system disk image with ratio expanding, even if you selected
larger HDD size than original HDD size.
Back to
Table of Contents
- Before running a consolidation task, please make
sure that at least the same or more available space than the
size of consolidated image files is in the storage of source
image files.
- While executing an incremental backup task on
the backup source host machine, a consolidation task for the
image file set cannot be executed from another host. Please
execute the consolidation task only after the incremental backup
task is completed on the backup source host machine.
- If any of the following conditions are met in
the system environment or consolidation source, even if some
data are deleted from incremental image files up to the latest
one, the processed image size is not decreased by the deleted
data size but may increase.
- Mount driver is not configured in the system
environment.
- Source volume is formatted with file system
other than NTFS.
Back to
Table of Contents
- Virtual conversion does not support dynamic disk
as conversion source.
- Virtual conversion does not support backup image
of dynamic volume as conversion source.
- If you perform a virtual conversion with the
thick provisioning (for VMware products) or fixed virtual disk
size (for Microsoft Hyper-V) option, the process time may be
longer depending on the conversion source disk size.
- In the event of virtual conversion from image
files, task execution progress may continue to be 0% after the
task is started.
- P2V Conversion does not support datastore on
ESXi 6.5 host as the target storage.
- To connect to vCenter
Server of VMware vSphere or ESXi hypervisor for the target host,
port 902 is used. If you fail to establish the connection,
please make sure that the port is opened in Windows Firewall
settings on the target host.
- If P2V Conversion by
using vCenter Server of VMware vSphere does not start, please
directly specify ESXi hypervisor as the target for conversion.
- Network name including double-byte character is
not displayed on wizard.
- Conversion to datastore on ESXi 4.x host is not
supported.
- Direct conversion to
VMWare ESXi host using VMware vSphere free licensed edition does
not support conversion with creation of a new folder.
- If not specifying a destination folder, the
files are created in root directory in datastore.
- (6532) Conversion to an
NFS datastore is not supported.
- (7655) You cannot convert
7 or more HDD together.
- Before selecting local or shared folder for the
destination, please ensure that the storage destination is NTFS
formatted. Storage destination such as NAS formatted with Linux
FS such as FAT/FAT32, Linux Ext4, etc., is not supported.
- You need to log in as administrator or domain
administrator. Users in administrator group or domain
administrators group are not authenticated.
- uEFI system conversion is supported only with
conversion target host supporting Generation 2 virtual machines.
- If Hyper-V host on
Windows Server 2008 R2 is selected as the target host, the
network settings are not applied to the created virtual
machines.
- Conversion to VHDX supports Windows 8/Windows
Server 2012 of later OS only.
Back to
Table of Contents
- To create USB boot media, please make sure 512MB
or more available space in USB memory.
- To create boot environment in USB memory
formatted with file system other than FAT (FAT32), formatting
the USB memory in FAT (FAT32) is required.
Back to
Table of Contents
- To create USB boot media, please make sure 512MB
or more available space in USB memory.
- To create (Windows PE-based) Boot Environment
(ISO or PreBoot environment), please make sure Windows AIK or
Windows ADK is configured in the system.
Windows ADK needs to include the following components:
- Deployment Tools
- Windows Preinstallation Environment(Windows PE)
- To create boot media or to create PreBoot
environment on BIOS boot system, it is recommended to use
Windows AIK or Windows ADK of the same version as the system.
- To create PreBoot environment in a uEFI boot
system, please use the following Windows AIK or Windows ADK
depending on the system environment.
Windows 10/2016
Windows ADK for Windows 10 (Windows Assessment &
Deployment Kit for Windows 10)
Windows 8.1/2012R2
Windows ADK 5.1（Windows Assessment & Deployment
Kit for Windows 8.1 Update）
Windows 8/2012
Windows ADK 4.0（Windows Assessment & Deployment
Kit for Windows 8)
Windows 7/2008R2
Windows AIK 3.0（Windows auto-installation kit for
Windows 7 SP1)
- To create 64-bit Boot Environment (Windows PE),
a 64-bit OS is required.
- Device drivers must support Windows PE based OS
version to create the boot environment. Windows PE based OS
version will be displayed in "Detailed information of the
Windows PE tool" in [Windows PE kit] of [Windows PE based boot
environment builder].
- Boot environment in USB memory using Windows AIK
3.0 (Windows auto installation kit for Windows 7 SP1) is not
supported in uEFI environment.
- [Burn to DVD media] option is not provided for
Windows XP/2003. After creating ISO image, please use a
third-party writing software to burn the ISO image to DVD media.
Back to
Table of Contents
- uEFI boot with secure boot option is not
supported. With CSM (Compatibility Software Module) enabled,
uEFI boot is supported in legacy mode (MBR) or compatible mode.
With CSM disabled or if CSM boot is enabled in uEFI mode only,
uEFI boot is not supported.
- Add Device Driver feature is not supported.
- If a single byte space is included in the path
to storage destination for saving volume backup image, you may
encounter an error.
- If a Windows 7 system disk or later is created
in Boot Environment and restored in Windows module (including
Windows PE boot environment), please execute restore task
without changing restore settings. Should you change restore
settings, disk meta data is not restored and the restored system
fails to boot up.
- Once Boot Environment is booted up, please do not
remove the media until all operations
are complete.
- If clicking on [Create
Support Info], the message dialog is not displayed. The
support information file is created in "/opt/BE" in the
following format:
AipSupportInfo_yyyymmdd_hhmm.tgz
- Drive letters indicated in disk map are not consistent
with those in Explorer for browsing a file.
- When overwriting to restore the mounted volume, please
unmount the target volume by selecting [Utilities]-[Mount
(Local)] before you proceed with further operation.
- You cannot restore split image from optical media.
- (7669) You cannot mount image.
Back to
Table of Contents
- You can access a network shared folder by taking
the following operating procedures:
- Directly access in Explorer.
- Go to [Utilities] - [Network Setting] and create
network drive to access.
- Japanese letters are not supported.
- To use the Deduplication Compression feature,
folders on local storage can be selected as temporary work
folders.
- Once Boot Environment
is booted up, do not remove the media until all operations are
complete.
- Conversion to VHDX file is not supported in boot
environment created by using Windows AIK 3.0 (Windows Automated
Installation Kit for Windows 7 SP1).
Back to
Table of Contents
- Copying a large number of
files takes long in time.
- A file cannot be directly
executed from an image file.
- Browsing the contents in
ReFS and Linux FS are not supported.
- File property copied from
directly opened image file is not maintained. If the file
property needs to be maintained, please use Mount Image feature.
- Items in an image file
are grayed out, however, you can browse or copy items in
folders.
Back to
Table of Contents
- Push Installer supports version 2016 R2 or later
installation packages.
- You cannot select a remote host which does not
return response to Ping command.
- To obtain a host list from Active Directory,
please make sure that the settings for Ping command with Active
Directory name to be responded from searching host.
- If incomplete search result is obtained, please
retry the searching.
- Cancelling host search may take long.
- Before you execute Push Installer, please make
sure that the log-in user has administrative right and is
authorized to access administrative shared resource on the
target host.
- Push Installer supports the following versions:
- Version 3.5：SP7
- Version 2016：SP1 or later
- Upgrading by Push Installer can migrate the
entire existing files including setting files and schedules.
- Installation by Push Installer deletes the
entire files. If you select [No reboot on uninstall] option,
some of the files are not deleted until the system is rebooted.
Back to
Table of Contents
- Remote Host Management List supports the
following versions for monitoring the status :
- Windows Edition：Version 3.5 SP7 or later
- Linux Boot Environment：Version 2016 or later
- Windows PE Boot Environment：Version 2016 or
later
- Linux Edition：Version 2016 or later
- Boot Environment：Version 2016 or later
- When multiple
schedules are created, only the schedules for the most immediate
execution are listed.
- (7532) To select any
host from the search result, please click on the host name. The
checkboxes may be disabled even if you click on.
- In the event that the host name on Remote Host
Management List is changed, please delete the host name from the
list and add it to the list again.
- When adding host which booted Boot Environment to
the list, please enter "root" to user name/password.
- Connection only to
version 2016 agent or later is supported.
- If AIP was installed by selecting [Typical] or
[Custom] - [Firewall Setting], the following TCP/UDP port rules
required for network communication with the agent are applied to
the inbound rule settings for Windows Firewall.
- AIP Console（TCP/UDP）
- AIP Push Installer（TCP/UDP）
- AIP Service（TCP/UDP）
If AIP was installed with otherwise configured
settings, ensure that the Windows Firewall exception settings are
configured for the following TCP/UDP ports on both managing and
managed host's OS in order to display remote networked computers
on which the AIP agent is installed.
- TCP Port 48236
- UDP Port 48238
- UDP Port 48239
- Windows File and printer sharing
- If you change any of the above port numbers, a
restart the service (ActiveImage Protector Service) is required.
- To connect to an AIP agent on a remote host, the
same or lower version of AIP agent as on local host must be
configured on the managed remote host. A connection to a newer
AIP agent than the AIP agent on the local host cannot be
established.
- To connect to Boot Environment (Windows PE)
agent, a User Name and Password are not required.
- To connect to AIP agent Linux Edition including
Boot Environment agent, log in as "root" user. To connect to
Boot Environment (Linux), a password is not required.
- When connected to Boot Environment (Windows PE)
agent, AIP CLI is disabled.
- To disconnect from a
remote computer, select [Connect to local host]. The same is
true if there is no agent installed on local host.
- When connecting to
Version 2016 Linux Edition agent, you cannot use the below
functions.
- [Image Manager] - [Mount]
menu
- [Advanced Options] -
[Scripting] - "Run on" menu in Schedule Backup
- Please do not use [Desktop] and [Documents] in
file/folder explorer. These short cut do not work correctly.
Back to
Table of Contents
- (6248) [Remember windows position and size
between sessions] in Console Setting is disabled.
Back to
Table of Contents
- The use of Event Log Viewer allows you to
monitor the latest 200 events. If the number of events logged in
the period you specify exceeds 200, no events are displayed.
- All contents may not be displayed in Task
Summary.
Back to
Table of Contents
ReZoom feature does not support restoring virtual
machines from an image file that does not meet the above
conditions.
ReZoom feature does not support the use of an image
file created by Cold Backup feature.
- Restoring to Hyper-V host of which version is
earlier than the backup souce host version is not supported.
Restoring to Hyper-V host of the same or later version is
supported.
- Restoring a selected virtual machine from backup
image file of Windows Server 2008 (Hyper-V 1.0) is not
supported. Windows Server 2008 (Hyper-V 1.0) is not supported as
the restore target either.
- Even when the processor makers of the backup
source Hyper-V host and restore target Hyper-V host are
different, ReZoom feature can be executed.
- Restore of a
virtual machine, which a differential virtual hard disk file
created by using Hyper-V Manager is connected to, is not
supported.
- In the event
that you cancel a task for restoring a virtual machine, the
in-processing file may remain on the restore target host. If you
encounter the problem, please manually delete the file.
- If you select
a password protected backup image file and enter an invalid
password, please cancel the selection of the image file in
ReZoom wizard and reselect an image file.
- If you select
a backup image file from the file’s History in network shared
folder, in the event that you are not authenticated to access
from the system to the folder yet, you should not be allowed to
select the image file. Please ensure that you are authenticated
to access from the system to the folder before you try to select
the image file again.
- ReZoom it!
does not support a virtual machine named with a double-byte
character or an image file of which config file's path name is
defined by using a double-byte character.
Back to
Table of Contents
- To create IT
Pro media, the Windows AIK or Windows ADK configured in the
system is required. The following components are required for
the Windows ADK.
- Deployment
Tools
- Windows
Preinstallation Environment (Windows PE)
- When creating
an ISO file and the DVD media option is selected to write the
created ISO file, be aware of the following limitations:
- Only blank
media can be used to write ISO file. If you have to use RW
media, please make sure that all data are purged from the media.
- To create USB
boot environment media, please make sure you have USB memory
with more than 1GB. 32GB or more media is not supported to use.
- You cannot
create USB flash drive bootable environment by using Windows AIK
3.0 (Windows Automated Installation Kit for Windows 7 SP1) in a
uEFI environment.
- Depending on
the display type, you may encounter the problem that the screen
display is not properly adjusted to the screen resolution
setting you configured.
- Available
device drivers have to support Windows PE OS version which the
creating boot environment is based on.
- Depending on
the device driver type, addition of the device driver to boot
environment media may fail. If you encounter this problem,
please boot up ActiveImage Protector Boot Environment (Windows
PE) and go to [Utility] - [Driver Loader].
- (7184) When
you select network shared folder for the destination to save ISO
files, you may get an error (GetDiskFreeSpaceEx). If you
encounter this problem, please specify local storage for the
destination.
Back to
Table of Contents
- Before using this product, ensure that [Windows
System Restore] (System Protection) is disabled.
- If using a disk defrag utility along with this
product, it is highly recommended to execute a backup task
immediately after completion of a defrag (defragmentation) to
create a full (base) backup image. When running disk
defragmenter software, the sectors on the disk are changed and
the size of incremental backup file may increase.
- Before migrating the virtual systems from a
VMware virtual environment to dissimilar virtual machine
hypervisors or physical computers, uninstall the VMware Tools
configured on virtual guest machines before creating backup
image files.
Back to
Table of Contents
Back to Index