CPU :
Pentium 4 or above

Main Memory :
2GB or above

• 3GB is recommended for “RescureBoot”.
• 4GB or above is required when specifying Cloud for the destination saving backup image file.

Hard Disk :

• 2GB or more of available hard disk space is required at setup.
• 7 GB or more of available hard disk space is required for building AIP Boot Environment. 512 MB or more of available hard disk space is required when Boot Environment is not included.
• 10% of available space in the respective volumes for change tracking to take snapshots and incremental backups.

• To run backup tasks using the Deduplication Compression feature, reserving 1% or more of the total data of the backup source for saving the temporary working files in a volume that should not be included in the backup source is required.

DVD-ROM Drive :
Required to install the product and boot up the ActiveImage Protector Boot Environment.

Internet connection :
Required for online activation of the product

• Red Hat Enterprise Linux 10.0 / 9.0 – 9.6 / 8.0 – 8.10 / 7.0 – 7.9
• CentOS：8.1 – 8.4 / 7.0 – 7.9
• Oracle Linux 10.0 / 9.0 – 9.6 / 8.1 – 8.10 / 7.0 – 7.9

• UEK of 8.7-8.10 is not supported

• AlmaLinux 10.0 / 9.0 – 9.6 / 8.3 – 8.10
• MIRACLE LINUX 9.6 / 9.4 / 9.2 / 9.0 / 8.10 / 8.8 / 8.6 / 8.4
• Rocky Linux 10.0 / 9.0 – 9.6 / 8.3 – 8.10
• Amazon Linux 2
• SUSE Linux Enterprise Server 15 / Desktop 15
• openSUSE Leap 15

• The above OSs require internet connection

• Ubuntu 18.04LTS / 20.04LTS / 22.04LTS / 24.04LTS
• Debian 9 – 12

Notes on installation of the product：

• ActiveImage Protector Linux Edition supports only x86_64 architecture.
• Secure Boot is not supported.
• If installing the product on Red Hat Enterprise Linux or clone OS of the equivalent OS, please make sure the following packages are installed to run ActiveImage Protector’s installer. glibc.x86_64, libgcc.x86_64, libstdc++.x86_64, libuuid.x86_64, make.x86_64, nss-softokn-freebl.x86_64, zlib.x86_64, kernel-devel.
  Please refer here for more information.

• Local Disk（Internal /External）：HDD / SSD with ATA / SATA / eSATA / SCSI / SAS / FireWire (IEEE 1394) connection、Virtual hard disk created on the storage space
• Network Drive: Actiphy StorageServer / Network drive with NAS（Network shared folders compatible with file sharing SMB/CIFS protocol , shared folders of Windows OS and Samba） / iSCSI / SAN connection
• Cloud Storage：Amazon S3, Azure Storage, Wasabi Cloud, Nifty Cloud, Cloudian, S3 compatible object storage
• HDD / SSD / RDX / Flash memory with USB connection
• LTO（magnetic tape）
• SFTP Server

• Storage media of which the sector size is 512 bytes or more is supported.
• SAN (fibre channel) can be used only when the driver is loaded in the boot environment.
• LTO tape is supported on ActiveImage Protector Server / Virtual / Cluster / IT Pro.
• When using ActiveImage Protector Virtual, physical machine with HyperAgent installed can backup to LTO tape.
• As for verified LTO device List, please refer to Knowledge Base

• Local Disk（Internal /External）：HDD / SSD with ATA / SATA / eSATA / SCSI / SAS / FireWire (IEEE 1394) connection, Virtual hard disk created on the storage space
• Network Drive: Network drive with NAS（Network shared folders compatible with file sharing SMB/CIFS protocol , shared folders of Windows OS and Samba） / iSCSI / SAN connection
• Cloud Storage：Amazon S3, Azure Storage, Wasabi Cloud, OneDrive, Dropbox, Google Drive
• HDD / SSD / RDX / flash memory with USB connection
• SFTP / FTP / WebDAV（https / http）Server

• Storage media of which the sector size is 512 bytes or more is supported.
• SAN (fibre channel) can be used only when the driver is loaded in the boot environment.

Standard Partition, Linux LVM (volume group and logical volume)

• Even the above layout, if complex layout, may not be supported.
• Only limited support is provided for the volumes configured on Fake RAID, dmraid or mdraid.
• LVM thin-provisioned environment is not supported.
• Linux Unified Key Setup (LUKS) encryption is not supported.

The ActiveImage Protector Linux comes with the ActiveImage Console which provides remote management capabilities and operates ActiveImage Protector installed on Linux systems from a Windows OS even when X Windows is not configured.

Supported Windows OS：

• Windows 10（x64）or later Windows Desktop OS
• Windows Server 2016 or later Windows Server OS

Main Memory :
2GB or above

DVD-ROM Drive :
Required to install the product and boot up the ActiveImage Protector Boot Environment.

Others :
System requirements for Deduplication feature are as follows:

• A volume with available space of 1% or more of the total volume size of the backup source as the working area to back up using deduplication other than the storage space for backup image files.
• CPU: Dual core processor or above (recommended)
• Main Memory: 2GB or above (recommended)
• 8GB or more main memory is recommended when processing large volume data.
• Intel Itanium（IA-64）based systems are not supported.

File System :
FAT16, FAT32, NTFS, Linux Ext2, Linux Ext3, Linux Ext4, Linux Swap, Linux LVM, XFS, VMFS5（Smart Sector backup for 2TB or less）, VMFS6（Full Sector backup only）

• Cold backup supports ESXi 6.5 / 6.7 / 7.0 / 8.0
• The above file systems on MBR and GPT disks are supported.
• The above mentioned file systems of virtual disks on Storage Space configured with Windows 8 or later are supported.

Backup Destination :

• Local Disk（Internal /External）：HDD / SSD with ATA / SATA / eSATA / SCSI / SAS / FireWire (IEEE 1394) connection、Virtual hard disk created on the storage space
• Network Drive: Actiphy StorageServer / Network drive with NAS（Network shared folders compatible with file sharing SMB/CIFS protocol , shared folders of Windows OS and Samba） / iSCSI / SAN connection
• Cloud Storage：Amazon S3, Azure Storage, Wasabi Cloud, Nifty Cloud, Cloudian, S3 compatible object storage
• HDD / SSD / RDX / Flash memory with USB connection
• SFTP Server

• Please refer to Knowledge Base to check how to use iSCSI.
• SAN (fibre channel) can be used only when the driver is loaded in the boot environment.
• As for the supported destination storage when backing up in boot environment, please refer to　Knowledge Base
• As for mounting nfs share in CentOS-based boot environment, please refer to　Knowledge Base