1-Touch for AIX: System Requirements

Operating System

The following are the requirements for 1-Touch on AIX:

Server

AIX 7.2 64-bit with Technology Level 1 or higher (LPAR with shared fibre channel card NPIV supported)

AIX 7.1 64-bit with Technology Level 2 or higher (LPAR with shared fibre channel card NPIV supported)

AIX 6.1 64-bit with Technology Level 2 or higher (LPAR with shared fibre channel card NPIV supported)

Client

AIX 7.2 64-bit with Technology Level 1 or higher (LPAR with shared fibre channel card NPIV supported)

AIX 7.1 64-bit with Technology Level 2 or higher (LPAR with shared fibre channel card NPIV supported)

AIX 6.1 64-bit with Technology Level 2 or higher (LPAR with shared fibre channel card NPIV supported)

Hard Drive

1-Touch Server

6 GB of minimum disk space is required for installing the software.

512 MB of free disk space is required for job result directory.

3 GB of free disk space is required for log directory.

6-8 GB of a disk space is required per recovery job on a NIM master server. The disk space size depends on the size of the MKSYSB backup of the client's root volume group (rootvg).

To find the disk space size:

  1. Right-click the subclient and click Backup History.

  2. On the Backup History Filter dialog box, click OK.

  3. In the Backup Job History tab, right-click the 1-Touch Backup job and click View Job Details.

  4. On the Job Details dialog box, click the Attempts tab and check the Size of Application for the 1-Touch Server Update phase.

  5. Click OK.

For example, if you plan to recover two AIX services or LPARs at the same time and the average MKSYSB size is 8GB, you will need 16GB of disk space.

Client

No additional disk space required beyond File System iDataAgent disk space requirements.

Memory (RAM)

3 GB minimum

Processor

Power PC (Includes IBM System p)

Notes

Server

  • The 1-Touch Server must be a dedicated AIX machine running the NIM master server environment.

Client

  • NIM client must be installed and/or configured on clients (EZ-NIM client).

  • Clients should have a configured network card that can be used to boot from a NIM master.

  • For clients with link aggregation or EtherChannel, ensure that standard network adapter is configured for communication with NIM server.

  • The 1-Touch server can be in the same subnet as the client computer, or it can be in a different subnet. However, if they are in different subnets, ensure that there is no network firewall between the server and the client.

    For each different subnet there should be NIM network resource defined. This is important not only when NIM master and client are in different subnets, but also in case 1-Touch recovery is performed to a client that is in a different subnet than the NIM master and the original client. If the network resource is not defined for the destination client subnet and selected during recovery, 1-Touch recovery will not be successful. For more information on defining NIM network resources, refer to IBM NIM documentation.

  • Only active volume group will be backed up during 1-Touch backup.

This feature is not supported when bootable partitions are on the disk arrays (snapable disk).

Supported File System and Volume Manager Types

  • AIX logical Volume Manager for Root and Non- root Volumes (LVM)

  • VERITAS Volume Manager 5.0 or higher for Non root Volumes (VXVM)

  • Journal File System (JFS) (AIX)

  • Enhanced Journal File System (JFS2) (AIX)

DISCLAIMER

Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software. Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.

Loading...