System Requirements - File Archiver for Unix Agent

The following requirements are for the File Archiver for Unix Agent:

Operating System

Processor

AIX

AIX 5.2 32-bit and 64-bit with technology level 10 and runtime library xlC.rte 8.0.0.0 or higher

AIX 5.3 32-bit and 64-bit with technology level 6 and runtime library xlC.rte 8.0.0.0 or higher

AIX 6.1

Power PC (Includes IBM System p)

HP-UX

HP-UX 11i v1 (11.11) 32-bit with OS patch PHCO29328 (contact Hewlett Packard to obtain the patch)

HP-UX 11i v1 (11.11) 64-bit with OS patch PHCO29328 (contact Hewlett Packard to obtain the patch)

HP-UX 11.23 64-bit

HP-UX 11.31 64-bit

PA RISC

HP-UX 11.23 64-bit

HP-UX 11.31 64-bit

Intel Itanium

Linux

CentOS

CentOS 5.3 with kernel 2.6.18-128.el5

Intel Pentium or compatible minimum required

Debian

Debian 5.x with kernel 2.6.26-2-686

Intel Pentium or compatible minimum required

Debian 5.x with kernel 2.6.26-2-amd64

x64

OES File System

Novell OES2 Linux up to SP1 (SLES 10 SP2) 32-bit

Intel Pentium or compatible minimum required

Novell OES2 Linux up to SP1 (SLES 10 SP2) 64-bit

x64

This feature/product/platform requires a special software installation package. Contact your software provider to obtain this package.

Red Hat Enterprise Linux

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-34 (Update 3)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-42 (Update 4)

Red Hat Linux AS 4.0 with kernel 2.6.9-55 (Update 5)

Red Hat Linux AS 4.0 with kernel 2.6.9-67 (Update 6)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-78 (Update 7)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-89 (Update 8)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-8.el5

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-53.el5 (Update 1)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-92 (Update 2)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-128 (Update 3)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update 4)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-34 (Update 3)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-42 (Update 4)

Red Hat Linux AS 4.0 with kernel-2.6.9-55 (Update 5)

Red Hat Linux AS 4.0 with kernel-2.6.9-67 (Update 6)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-78 (Update 7)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-89 (Update 8)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-8.el5

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-53.el5 (Update 1)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-92 (Update 2)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-128 (Update 3)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update 4)

x64

SuSE Linux

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.244 (Patch Level 3)

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.308 (Patch Level 4)

Suse Linux 10 Enterprise Server with kernel 2.6.16.21-0.8

Suse Linux 10 Enterprise Server with kernel 2.6.16.46-0.12 (Patch Level 1)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.21 (Patch Level 2)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.34 (Update 2)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.54.5 (Patch Level 3)

SuSE Linux 11 Enterprise Server with kernel 2.6.27.19-5

Intel Pentium or compatible minimum required

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.244 (Patch Level 3)

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.308 (Patch Level 4)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.46-0.12 (Patch Level 1)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.21 (Patch Level 2)

SuSE Linux 11 Enterprise Server with kernel 2.6.27.19-5

x64

SGI IRIX64

SGI IRIX64 6.5 with revision 7.4.2 runtime libraries and the eoe.sw.dmi package installed.

SGI workstation with type IP30 system board

Solaris

Solaris 8 64-bit with Service Packs 108434-09, 108435-09, and 109147-20

Solaris 8 32-bit and 64-bit VERITAS File System with Service Packs 108434-09, 108435-09, and 109147-20

Solaris 9 4/04 64-bit

Solaris 9 64-bit with Service Packs 111711-02 and 111712-02

Solaris 10 64-bit

Solaris 10 6/06 64-bit

Sun Ultra2 or higher recommended

Cluster Support

See Clustering - Support

Memory

256 MB RAM or higher recommended total system memory

Hard Disk

250 MB minimum of hard disk space for software

50 MB of additional hard disk space for log file growth

20 MB of temp space required for install (where the temp folder resides)

3.5 KB per file of cache partition

Peripherals

DVD-ROM drive

Network Interface Card

Miscellaneous

TCP/IP Services configured on the computer.

On Solaris computers, the operating system must have been installed with at least the user level software option selected.

Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008 Redistributable Package can co-exist with other versions of this software.

If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.

To create SELinux policy module, perform the following steps as user "root":

Create the following files in the /usr/share/selinux/devel directory:

File Name

Content of the file

<directory>/<file_name>.te

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te

The content of the file should be as follows:

policy_module(<name>,<version>)

##############################

where:

<name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.

<version> is the version of the policy module. It can be any number, such as 1.0.0.

For Example: While creating a policy module for the backup_IDA application, you can use the following content.

policy_module(backup_IDA,1.0.0)

<directory>/<file_name>.fc

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc

The content of the file should be as follows:

Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.

/opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDrDatabase.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libIndexing.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.

[root]# make backup_IDA.pp

Compiling targeted backup_IDA module

/usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp

/usr/bin/checkmodule: policy configuration loaded

/usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod

Creating targeted backup_IDA.pp policy package

rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc

[root]# semodule -i backup_IDA.pp

[root]#

Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as �supported� in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.