V11 SP8
Loading...

System Requirements - Notes Database iDataAgent

The IBM Notes and IBM Domino iDataAgents support the following IBM Domino releases in a non-Domino cluster environment.

  • If you have Domino server running in a clustered environment, install the IBM Domino Agent on each Domino server. For more information, see Notes Database Restore Consideration.
  • Multiple Domino versions (9.0 and 8.5) are supported on the same UNIX client.

Application/Operating System

Architecture

IBM Domino 9.0.x Social Edition 32 bit on:

Linux

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 7.x

Intel Pentium, x64 or compatible processors

Red Hat Enterprise Linux/CentOS 6.x with a minimum of glibc 2.12-1.25.x

x64

SuSE Linux (SLES)

SuSE Linux 11.x Enterprise Server

Intel Pentium, x64 or compatible processors

Windows

Windows 2012

Microsoft Windows Server 2012 R2 Editions

All Windows-compatible processors supported

Microsoft Windows Server 2012 Editions

*Core Editions are not supported.

All Windows-compatible processors supported

Windows 2008

Microsoft Windows Server 2008 Editions

*Core Editions are not supported.

All Windows-compatible processors supported

IBM Domino 9.0.x Social Edition 64 bit on:

AIX

AIX 7.1 64-bit

Power PC (Includes IBM System p)

AIX 6.1 TL 02 SP00 64-bit or higher

Power PC (Includes IBM System p)

Linux

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 6.x with a minimum of glibc 2.12-1.25.x

x64

SuSE Linux (SLES)

SuSE Linux 11.x Enterprise Server

x64

Windows

Windows 2012

Microsoft Windows Server 2012 R2 Editions

All Windows-compatible processors supported

Microsoft Windows Server 2012 Editions

*Core Editions are not supported.

All Windows-compatible processors supported

Windows 2008

Microsoft Windows Server 2008 Editions

*Core Editions are not supported.

All Windows-compatible processors supported

Lotus Domino Server Release 8.5.x 32-bit on:

Linux

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 5.x or higher (with glibc 2.5.x)

Intel Pentium, x64 or compatible processors

SuSE Linux (SLES)

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

Intel Pentium, x64 or compatible processors

SuSE Linux 10.x with glibc 2.4.x

Intel Pentium, x64 or compatible processors

Windows

Windows 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

*Core Editions are not supported.

* Special configuration considerations apply. See Enabling 32-Bit Installations on 64-Bit Windows Computers for more information.

All Windows-compatible processors supported

Lotus Domino Server Release 8.5.x 64-bit on:

AIX

AIX 7.1 64-bit

Power PC (Includes IBM System p)

AIX 6.1 TL 02 SP00 64-bit or higher

Power PC (Includes IBM System p)

Linux

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 5.x or higher (with glibc 2.5.x)

x64

SuSE Linux (SLES)

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

x64

SuSE Linux 10.x with glibc 2.4.x

x64

Windows

Windows 2008

Microsoft Windows Server 2008 x64 Editions*

*Core Editions are not supported.

All Windows-compatible processors supported

Hard Drive

1.5GB of minimum disk space is required for installing the software.

Miscellaneous

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.

.NET Framework

.NET Framework 4.0 is automatically installed. Note that .NET Framework 4.0 can co-exist with other versions of this software.

Microsoft Visual C++

The following Redistributable Package is installed automatically. Note that the Redistributable Package can co-exist with other versions of this software.

Microsoft Visual C++ 2010 Redistributable Package

Notes on Domino 8.5.X on Windows 2012

For Domino 8.5.X on Windows 2012, ensure that the Domino Sever has 8.5.3 Fix Pack 4 and later installed on it.

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.