DB2 MultiNode Agent (DB2 DPF) - System Requirements

The following requirements are for the DB2 MultiNode agent (DB2 DPF).

DB2 Database 11.1 64-bit

Operating System

Operating System Version

Architecture

AIX

AIX 7.2 64-bit

PowerPC

AIX 7.1 64-bit

PowerPC

AIX 6.1 TL 02 SP00 or higher, 64-bit

PowerPC

Linux

NeoKylin Linux

NeoKylin Linux 6.5

x64

Red Hat Enterprise Linux

Red Hat Enterprise Linux 8.x

Before you install the Commvault software, you must manually install the libxcrypt.x86_64 and libnsl.x86_64 packages on the computer.

x64

Red Hat Enterprise Linux 7.x

  • x64

  • PowerPC (big endian or little endian)

  • Compatible processors

Red Hat Enterprise Linux 5.x with libstdc++ version 4.2.4 or above

x64

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

PowerPC

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

x64

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x or a more recent version

x64

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12-1.25.x or a more recent version

x64

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

x64

SuSE Linux (SLES)

SuSE Linux 15 (Initial Release/SP1 and later SPs) with glibc 2.26.x and higher

x64

SuSE Linux 12 (Initial Release/SP1/SP2/SP3/SP4/SP5) with glibc 2.19.x

x64

SuSE Linux 12 SP1 Enterprise Server

  • PowerPC

  • PowerPC (little endian)

SuSE Linux 11 (Initial Release/SP1 and later SPs) with glibc 2.9.x and higher

x64

Solaris

Solaris 11.x

Ultra5 or higher recommended

Z-Linux

Red Hat Enterprise Linux

Red Hat Enterprise Linux 6.x

s390x 64-bit

Red Hat Enterprise Linux 5.x

s390x 64-bit

SuSE Linux (SLES)

SuSE Linux 12.x Enterprise Server

s390x 64-bit

DB2 Universal Database 10.5/10.1/9.7/9.5 64-bit

Operating System

Operating System Version

Architecture

AIX

AIX 7.2 64-bit

PowerPC

AIX 7.1 64-bit

PowerPC

AIX 6.1 TL 02 SP00 or higher, 64-bit

PowerPC

HP-UX

HP-UX 11i v3 (11.31) 64-bit

Itanium

HP-UX 11i v1 (11.23)

Itanium

Linux

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x or a more recent version

Supported only on DB2 versions 10.5, 10.1, and 9.7.

x64

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12-1.25.x or a more recent version

x64

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

x64

SuSE Linux (SLES)

SuSE Linux 12 (Initial Release/SP1/SP2/SP3/SP4/SP5) with glibc 2.19.x

x64

SuSE Linux 11 (Initial Release/SP1 and later SPs) with glibc 2.9.x and higher

x64

SuSE Linux 11 with Service Pack 1

x64

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

x64

SuSE Linux 10 with Service Pack 3

x64

Solaris

Solaris 11.x

Sparc T/M series

Solaris 10 Update 6 or equivalent

Sparc T/M series

DB2 Universal Database 9.7/9.5 32-bit

Operating System

Operating System Version

Architecture

AIX

AIX 7.2 64-bit

PowerPC

AIX 7.1 64-bit

PowerPC

AIX 6.1 TL 02 SP00 or higher, 64-bit

PowerPC

Linux

Red Hat Enterprise Linux/CentOS

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

  • x86

  • Compatible processors

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

  • x86

  • Compatible processors

SuSE Linux (SLES)

SuSE Linux 11 (Initial Release/SP1 and later SPs) with glibc 2.9.x and higher

  • x86

  • Compatible processors

SuSE Linux 10 (Initial Release/SP1/SP2/SP3/SP4) with glibc 2.4.x

  • x86

  • Compatible processors

Solaris

Solaris 10 Update 6 or equivalent

Sparc T/M series

Hard Drive

See System Requirements - DB2 iDataAgent

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.

Miscellaneous

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:

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

Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software. Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.

Loading...