System Requirements - Documentum iDataAgent

System Requirements Supported Features  

The following requirements are for the Documentum iDataAgent:

Application/Operating System

Processor

Documentum 6.5 SP1/Higher on:

AIX

AIX 6.1

Power PC (Includes IBM System p)

HP-UX

HP-UX 11i v3 (11.31)

Itanium

Linux

Red Hat Enterprise Linux/CentOS

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

Itanium, x64 or compatible processors

SuSE Linux (SLES)

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

Itanium, x64 or compatible processors

SuSE Linux 10 SP2 Enterprise Server

Itanium, x64 or compatible processors

Solaris

Solaris 10.x with a minimum of SunOS (Sparc) Patch 119963-14

Sparc5 or higher recommended

Windows Server 2003

Microsoft Windows Server 2003 32-bit and x64 Editions with a minimum of Service Pack 2

All Windows-compatible processors supported

Windows

Windows 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

*Core Editions not supported

All Windows-compatible processors supported

Hard Drive

230 MB minimum of hard disk space for software

Memory

64 MB RAM per stream/drive minimum required beyond the requirements of the operating system and running applications

Swap space = 2*RAM size

Supported Databases

Oracle

Oracle 10g R2 (10.2.x)

Oracle 11g R1

Oracle 11g R2 (supported since Documentum 6.7)

See System Requirements - Oracle iDataAgent for more information on the supported versions listed above.

DB2

DB2 9.5 Universal Database

See System Requirements - DB2 iDataAgent for more information on the supported version listed above.

SQL

MS SQL 2005 SP3

See System Requirements - Microsoft SQL Server iDataAgent for more information on the supported version listed above.

Solaris Zones/Containers Support

Data Protection of data residing on global and non-global zones is supported.

For a comprehensive list of supported components, see Unix Virtualization.

AIX LPAR/WPAR Support

Data protection on Logical Partitioning (LPAR) and Workload Partitioning (WPAR) is supported.

Peripherals

DVD-ROM drive

Network Interface Card

Miscellaneous

Network

TCP/IP Services configured on the computer.

The File System iDataAgent will be automatically installed during installation of this software, if it is not already installed. For System Requirements and install information specific to the File System iDataAgents, refer to:

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.

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