System Requirements

A machine that you plan to protect with Veeam Agent for IBM AIX must meet requirements listed in the table below.

Specification	Requirement
Hardware	Memory: 1 GB RAM (for standard backup and restore operations) / 4 GB RAM (for bare metal recovery). Disk space: 1.5 GB free disk space for product installation. Network: 10 Mbps or faster network connection to a backup target.
OS	IBM AIX 7.1 – 7.3 TL1 are supported. Note: IBM AIX 6.1 has an experimental support status. For details about experimental support, see this Veeam KB article. Backup of a Virtual I/O Server (VIOS) is not supported. Only GA versions and updates of the IBM AIX OS that have been released before version 4.1 of Veeam Agent for IBM AIX are supported.
File System	All file systems supported by the supported operating systems. Consider the following: Total size of all file systems included in a file-level backup must not exceed 218 TB. Size of a file in a backup must not exceed 16 TB. Name of a file in a backup must not be larger than 254 bytes. Keep in mind that characters that you can use in the file name may be encoded in 2 bytes or more. Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files. JFS2 snapshots are not supported. Backup of clustered systems (including IBM PowerHA SystemMirror) is not supported.
Software	The following utilities must be installed on the machine: mlocate — required for file system indexing. You must use the mlocate utility that is provided with Veeam Agent in the product installation media. If you upgrade to Veeam Agent for IBM AIX version 4.1 and you have the mlocate utility provided with one of the previous versions of Veeam Agent for IBM AIX installed in your system, you must replace the existing mlocate utility with the mlocate utility provided with Veeam Agent 4.1 in the product installation media. tar — required for file system indexing, exporting and rotating logs. It is installed with the product. gzip — required for file system indexing, exporting and rotating logs. It must be installed separately. mkisofs — required for creating Veeam Recovery Media. [For IBM AIX 7.3, 7.2 and 7.1 TL1 or higher] This utility is pre-installed in the OS and does not require separate installation. [For IBM AIX 7.1 TL0 and 6.1] You must install version 1.13 of the mkisofs utility. [For IBM AIX 7.1] bos.rte.libc version 7.1.5.0 or later must be installed.

AIX Environment

The LIBPATH AIX environment variable on the Veeam Agent computer must be set to blank (default value). If a different value is specified for this variable, you must make adjustments to the AIX environment for proper operation of Veeam Agent. For details, see this Veeam KB article.

Backup Target

Backup can be performed to the following types of storage:

Local (internal) storage of the protected machine (not recommended)
Direct attached storage (DAS), such as USB, eSATA or Firewire external drives
Network Attached Storage (NAS) able to represent itself as NFS or SMB (CIFS) share

[For Veeam Agent for IBM AIX version 4.1] Veeam Backup & Replication 12.1 or later backup repository

[For Veeam Agent for IBM AIX version 4.0] Veeam Backup & Replication 11a (build 11.0.1.1261) or later backup repository

Important

Consider the following about backup repositories:

[For local storage] A backup repository should be created on a separate volume from a volume that contains data you plan to back up.

[For Veeam backup repository] Veeam Cloud Connect repositories, repositories with enabled KMS encryption and object storage repositories managed by Veeam Backup & Replication are not supported.

Network

Consider the following:

If you back up to a repository managed by a Veeam backup server, Veeam Agent for IBM AIX must be able to establish a direct IP connection to the Veeam Backup & Replication server. Veeam Agent for IBM AIX cannot work with Veeam Backup & Replication that is located behind a NAT gateway.
Domain names of the Veeam Agent machine, Veeam Backup & Replication server and other servers in the Veeam backup infrastructure must be resolvable into IPv4 addresses.