System Requirements - Linux File System iDataAgent

AIX HP-UX FreeBSD Linux Solaris Tru64 Supported Features  

The following are the requirements for Linux File System iDataAgent:

Operating System

Processor

Linux

Debian

Debian 7.x

Intel Pentium, x64 or compatible processors

Debian 6.x

Intel Pentium, x64 or compatible processors

Debian 5.x

Intel Pentium, x64 or compatible processors

Fedora

Fedora release 9 with glibc 2.8.x

Intel Pentium, x64 or compatible processors

Fedora release 8 with glibc 2.7.x

Intel Pentium, x64 or compatible processors

Fedora release 17 with glibc 2.15.x

Intel Pentium, x64 or compatible processors

Fedora release 16 with glibc 2.14.x

Intel Pentium, x64 or compatible processors

Fedora release 15 with glibc 2.13.x

Intel Pentium, x64 or compatible processors

Fedora release 14 with glibc 2.13.x

Intel Pentium, x64 or compatible processors

Fedora release 13 with glibc 2.12.x

Intel Pentium, x64 or compatible processors

Fedora release 12 with glibc 2.11.x

Intel Pentium, x64 or compatible processors

Fedora release 11 with glibc 2.10.x

Intel Pentium, x64 or compatible processors

Fedora release 10 with glibc 2.9.x

Intel Pentium, x64 or compatible processors

Gentoo

Gentoo release 11 with glibc 2.12.x

Intel Pentium, x64 or compatible processors

Gentoo release 10.1 with glibc 2.6.x

Intel Pentium, x64 or compatible processors

Mandriva

Mandriva Linux 2010 with glibc 2.10.x

Intel Pentium, x64 or compatible processors

Mandriva Linux 2009 with glibc 2.9.x

Intel Pentium, x64 or compatible processors

OpenSuSE

OpenSuSE 13.1 with glibc 2.18.x

Intel Pentium, x64 or compatible processors

OpenSuSE 12.3 with glibc 2.17.x

Intel Pentium, x64 or compatible processors

OpenSuSE 12.2 with glibc 2.15.x

Intel Pentium, x64 or compatible processors

OpenSuSE 12.1 with glibc 2.14.x

Intel Pentium, x64 or compatible processors

OpenSuSE 11.3 with glibc 2.11.x

Intel Pentium, x64 or compatible processors

OpenSuSE 11.2 with glibc 2.10.x

Intel Pentium, x64 or compatible processors

OpenSuSE 11.1 with glibc 2.9.x

Intel Pentium, x64 or compatible processors

OpenSuSE 11.0 with glibc 2.8.x

Intel Pentium, x64 or compatible processors

Oracle Linux

Oracle Linux 6.x with glibc 2.12.x

Intel Pentium, x64 or compatible processors

Oracle Linux 5.x with glibc 2.5.x

Intel Pentium, x64 or compatible processors

Oracle Linux 4.x with a minimum of glibc 2.3.4

Intel Pentium, x64 or compatible processors

Red Flag Linux

Red Flag Linux 5.x with a minimum of glibc 2.3.4

x64

Red Flag Linux 4.x with a minimum of glibc 2.3.4

Intel Pentium or compatible processors

Red Hat Enterprise Linux/CentOS

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

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

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

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

Red Hat Enterprise Linux/CentOS 4.x with a minimum of glibc 2.3.4

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

Scientific Linux

Scientific Linux SL 5.x with glibc 2.5.x

x64

Scientific Linux 6.x

x64

Slackware

Slackware 14.0 with glibc 2.15.x

Intel Pentium, x64 or compatible processors

SuSE Linux (SLES)

SuSE Linux 11.x with glibc 2.9.x and above

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

SuSE Linux 10.x with glibc 2.4.x

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

Ubuntu

Ubuntu 9.10

Intel Pentium, x64 or compatible processors

Ubuntu 9.04

Intel Pentium, x64 or compatible processors

Ubuntu 8.10

Intel Pentium, x64 or compatible processors

Ubuntu 8.04

Intel Pentium, x64 or compatible processors

Ubuntu 12.04 LTS

Intel Pentium, x64 or compatible processors

Ubuntu 11.10

Intel Pentium, x64 or compatible processors

Ubuntu 11.04

Intel Pentium, x64 or compatible processors

Ubuntu 10.04 LTS

Intel Pentium, x64 or compatible processors

Z-Linux

Linux on zSeries (System z9/z10)

s390x 64-bit, s390 31-bit

Red Hat Enterprise Linux

Red Hat Enterprise Linux 5.x

s390x 64-bit, s390 31-bit

Red Hat Enterprise Linux 4.x

s390x 64-bit, s390 31-bit

SuSE Linux (SLES)

SuSE Linux 11.x Enterprise Server

s390x 64-bit, s390 31-bit

SuSE Linux 10.x Enterprise Server

s390x 64-bit, s390 31-bit

Cluster - Support

The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.

For information on supported cluster types, see Clustering - Support.

Hard Drive

750 MB minimum of hard disk space for software

100 MB of additional hard disk space for log file growth

500 MB of reserved hard disk space for the Job Results directory

1 GB of temp space required for install or upgrade (where the temp folder resides)

For information on space requirements to install/upgrade the File System and service pack, see Service Pack - System Requirements.

Memory

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

Swap space = 2*RAM size

Peripherals

DVD-ROM drive

Network Interface Card

Miscellaneous

Network

TCP/IP Services configured on the computer.

SELinux

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

Supported File Systems

The Linux File System iDataAgent supports the following file systems:

B-tree File System (Btrfs)

Extended 2 File System (ext2)

Extended 3 File System (ext3)

Extended 4 File System (ext4)

General Parallel File System (GPFS)

Global File System (GFS/GFS2)

Lustre File System (Clustered File System)

Moose File System (MooseFS)

Oracle Cluster File System (OCFS2)

Reiser File System (reiserfs)

VERITAS File System (VxFS)

VERITAS Cluster File System (VxCFS)

X9000 IBRIX File System (IBRIXFS) 6.x

'X' File System (XFS)

Volume Managers

Veritas Volume Manager (VxVM) 5.0 or higher

Logical Volume Manager (LVM)

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with 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