System Requirements - Unix File System iDataAgent

System Requirements | Snapshot Support

The following requirements are for the Unix File System iDataAgents.

Operating System

Processor

AIX

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

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

AIX 6.1 64-bit

Power PC (Includes IBM System p)

FreeBSD

FreeBSD 6.x

x86 compatible

FreeBSD 7.x

x86 compatible
 
recut.gif

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

HP-UX

 HP-UX 11i v1 (11.11) with a minimum of OS patch PHCO_29328 and PHCO_29287 (contact Hewlett Packard to obtain the patch)

HP-UX 11i v2 (11.23)

HP-UX 11i v3 (11.31)

PA-RISC

HP-UX 11i v2 (11.23)

HP-UX 11i v3 (11.31)

Intel Itanium

SGI IRIX64

SGI IRIX64 6.5 with revision 7.4.2 runtime libraries

SGI workstation with type IP30 system board

Linux

CentOS

CentOS 4.x or higher with glibc 2.3.x

Intel Pentium, x64 or compatible processors
 

Debian

Debian 5.x with glibc 2.7.x

Intel Pentium, x64 or compatible processors

Fedora

Fedora release 8 with glibc 2.7.x

Fedora release 9 with glibc 2.8.x

Fedora release 10 with glibc 2.9.x

Intel Pentium, x64 or compatible processors
 

Gentoo

Gentoo 10.x with 2.6.x kernel

Intel Pentium, x64 or compatible processors

 

Mandriva

Mandriva Linux 2009 with glibc 2.9.x

Intel Pentium, x64 or compatible processors
 

OpenSuSE

OpenSuSE 11.0 with glibc 2.8.x

OpenSuSE 11.2 with glibc 2.10.1

x64

Oracle Enterprise Linux

Oracle Enterprise Linux 4 with glibc 2.3.x

Oracle Enterprise Linux 5 with glibc 2.5.x

Intel Pentium, x64 or compatible processors

Red Flag Linux

Red Hat Enterprise Linux 4.x with glibc 2.3.x

Intel Pentium or compatible processors

Red Flag Linux 5.x with glibc 2.3.x

x64
 

Red Hat Enterprise Linux

Red Hat Linux 9.0 32-bit distributions and versions with glibc 2.3.x

Red Hat Enterprise Linux 3.x with glibc 2.3.x

Red Hat Enterprise Linux 4.x with glibc 2.3.x

Red Hat Enterprise Linux 5.x with glibc 2.5.x

Red Hat Enterprise Linux 6.x with glibc 2.12.x

Intel Pentium, Intel Itanium, x64, Power PC (Includes IBM System p) or compatible processors
 

Scientific Linux

Scientific Linux SL 5.2 with glibc 2.5.x

x64

SuSE Linux

SuSE Linux 9.x with glibc 2.3.x

SuSE Linux 10.x with glibc 2.4.x

SuSE Linux 11.x with glibc 2.9.x

Intel Pentium, Intel Itanium, x64, Power PC (Includes IBM System p) or compatible processors

Ubuntu

Ubuntu 8.04

Ubuntu 8.10

Ubuntu 9.04

Ubuntu 9.10

Ubuntu 10.04 LTS

Intel Pentium, x64 or compatible processors

Solaris

Solaris 8 with a minimum of Service Packs 108528-13

Solaris 9

Solaris 10.x (Flying Zones supported)

Sun Sparc5 or higher recommended

Solaris 10.x (OpenSolaris supported)

x64

Tru64

Tru64 OSF1 Release 5.1B-3 or higher

Compaq® (DEC) AlphaServer DS Series computer or higher recommended

Cluster Support

See Clustering - Support

Memory

16 MB RAM minimum required beyond the requirements of the operating system and running applications

Swap space = 2*RAM size

Hard Disk

215 MB minimum of hard disk space for software

100 MB of additional hard disk space for log file growth

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

Peripherals

DVD-ROM drive

Network Interface Card

Miscellaneous

TCP/IP Services configured on the computer.

The operating system must have been installed with at least the user level software option selected

The Unix File System iDataAgents support the following file system types:

Supported File System(s)

Unix File System iDataAgent(s) Providing Support
Advanced File System (advfs) Tru64
CD-ROM File System (cdfs) All
Enhanced Journal File System (JFS2) AIX
Extended 2 File System (ext2) Linux
Extended 3 File System (ext3) Linux
Extended 4 File System (ext4) Linux
General Parallel File System (GPFS) Linux
Hierarchical File System (HFS) HP-UX
Journal File System (JFS) AIX, HP-UX
Oracle Cluster File System (OCFS2) Linux
Reiser File System (reiserfs) Linux
Red Hat File System GFS 5.2 Linux
Unix File System (UFS) All except IRIX
VERITAS File System (VxFS) AIX, HP-UX, Linux, Solaris
VERITAS Cluster File System (VxCFS) AIX, HP-UX, Linux, Solaris
'X' File System (XFS) IRIX and Linux
Zettabyte File System (ZFS) Solaris 10 6/06 64-bit only
 

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":

  1. 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)

 
  1. 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]#

  1. 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.