Documentum Agent: System Requirements

The following requirements are for the Documentum Agent:

Documentum Versions 6.5 SP1 (or later), 7.0, 7.1, 7.2 and 16.4

Hard Drive

Supported Databases

Oracle

Oracle 10g R2 (10.2.x)

Oracle 11g R1

Oracle 11g R2

Oracle 12c standalone database

DB2

DB2 9.5 Universal Database

DB2 9.7 Universal Database

SQL

Microsoft SQL Server 2005 Editions up to the latest Service Pack

Microsoft SQL Server 2008 Editions up to the latest Service Pack

Microsoft SQL Server 2008 R2 Editions up to the latest Service Pack

Microsoft SQL Server 2012 Editions*
*See Considerations for SQL Server 2012.

Solaris Containers and Zones

You can back up and restore data in both global and non-global zones.

For a list of supported components, see Unix Virtualization.

AIX LPAR/WPAR

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

File System Agent Requirements

• When this software is installed, the appropriate file system agent is also installed (if it is not already installed). For system requirements for the file system agents, see the following:

  • System Requirements - Microsoft Windows File System Agent

  • System Requirements - AIX File System Agent

  • System Requirements - HP-UX File System Agent

  • System Requirements - Linux File System Agent

  • System Requirements - Solaris File System Agent

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

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)

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

3. Execute the policy module. Use the following command:

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

SELinux is now configured to work with this application.

Microsoft Visual C++ Redistributable 2017 is Automatically Installed

Starting in Service Pack 18, Microsoft Visual C++ Redistributable 2017 (vcredist2017.exe) is automatically installed. If a computer does not have the latest Windows updates, the installation of Microsoft Visual C++ Redistributable 2017 will fail in installing Universal C Runtime.

The following Windows updates must be installed to prevent the installation failure:

KB2919355

KB2939087

KB2975061

KB2999226

Updates are not required on latest Windows operating system versions, such as Microsoft Windows 10 and Microsoft Windows Server 2016, as these versions come with the Universal C Runtime already installed.

DISCLAIMER

Certain third-party software and service releases (together, “Releases”) may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.