System Requirements - Domino Mailbox Archiver Agent

System Requirements Supported Features  

The Domino Mailbox Archiver Agent supports the following Lotus Domino Server releases in both Domino Cluster and non-Domino Cluster environments.

Application/Operating System

Processor

Lotus Domino Server Release 8.02 32-bit on:

AIX

AIX 6.1

Power PC (Includes IBM System p)

AIX 5.3 with technology level 7 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

Power PC (Includes IBM System p)

Linux

Red Hat Enterprise Linux/CentOS

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

Intel Pentium, x64 or compatible processors

SuSE Linux (SLES)

SuSE Linux 10.x with glibc 2.4.x

Intel Pentium, x64 or compatible processors

Solaris

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

UltraSPARC III and higher recommended

Windows

Windows 2008

Microsoft Windows Server 2008 x64 Editions*

*Core and R2 Editions not supported

All Windows-compatible processors supported

Microsoft Windows Server 2008 32-bit Editions*

All Windows-compatible processors supported

Windows 2003

Microsoft Windows Server 2003 x64* Editions with a minimum of Service Pack 1

All Windows-compatible processors supported

Microsoft Windows Server 2003 32-bit Editions with a minimum of Service Pack 1

All Windows-compatible processors supported

Lotus Domino Server Release 8.02 64-bit on:

AIX

AIX 6.1 64-bit

Power PC (Includes IBM System p)

AIX 5.3 with technology level 7 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

Power PC (Includes IBM System p)

Windows

Windows 2003

Microsoft Windows Server 2003 x64 Editions with a minimum of Service Pack 1

All Windows-compatible processors supported

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

AIX

AIX 6.1 64-bit

Power PC (Includes IBM System p)

AIX 5.3 with technology level 7 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

Power PC (Includes IBM System p)

Linux

Red Hat Enterprise Linux/CentOS

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

Intel Pentium, x64 or compatible processors

SuSE Linux (SLES)

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

Intel Pentium, x64 or compatible processors

SuSE Linux 10.x with glibc 2.4.x

Intel Pentium, x64 or compatible processors

Solaris

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

UltraSPARC III and higher recommended

Windows

Windows 2003

Microsoft Windows Server 2003 x64* Editions with a minimum of Service Pack 2

*Core Editions not supported

All Windows-compatible processors supported

Microsoft Windows Server 2003 32-bit Editions with a minimum of Service Pack 1

All Windows-compatible processors supported

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

AIX

AIX 6.1 64-bit

Power PC (Includes IBM System p)

AIX 5.3 with technology level 7 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

Power PC (Includes IBM System p)

Windows

Windows 2008

Microsoft Windows Server 2008 x64 Editions*

*Core Editions not supported

All Windows-compatible processors supported

Windows 2003

Microsoft Windows Server 2003 x64* Editions with a minimum of Service Pack 2

All Windows-compatible processors supported

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

All Windows-compatible processors supported

Hard Drive

1.5 GB minimum of hard disk space for software.

500 MB of free disk space is required for job result directory.

Memory

AIX, Linux, and Solaris

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

Swap space = 2*RAM size

Windows

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

*Very Large Memory Module (VLMM) supported.

Lotus Notes Client Add-In

The Lotus Notes Client Add-In is supported with the following Lotus Notes client applications running on a Microsoft Windows platform:
  • Notes Client 8.5.x
  • Notes Client 8.0.x
  • Notes Client 9.0.x

Peripherals

DVD-ROM drive

Network Interface Card

Miscellaneous

Network

TCP/IP Services configured on the computer.

The Domino Mailbox Archiver Agent does not support Domino Attachment and Object Service (DAOS).

If the Domino Mailbox Archiver Agent for Unix is installed on a client computer where the File Archiver for Unix Agent is installed and the computer is running a kernel not supported by the File Archiver for Unix Agent, then the GXHSMService will not launch. In such scenarios, uninstall the File Archiver for Unix Agent. This will not uninstall the GXHSMService as the Domino Mailbox Archiver Agent for Unix is still installed on the client computer.

Microsoft Visual C++

Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008 Redistributable Package can co-exist with other versions of this software.

.NET Framework

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

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.

For 32-bit Domino Servers running on Windows Server 2003 and 2008 x64 platforms, special considerations apply. See Installing 32-bit Components on a Microsoft Windows x64 Platform for more information. For Windows Server 2008 platforms, Core Editions are not supported.

Notes on Domino Cluster Installations

If you are running a Lotus Domino Server in a Domino Cluster, special restore considerations apply. See Restore Considerations for this Agent in Restore Data - Lotus Notes/Domino Server for more information.

Notes on Lotus Notes Client Add-In Installations

For Windows clients, JRE 1.7.0_17 is installed automatically with the Lotus Notes Client Add-In software if it is not already installed.

For Macintosh clients, JRE 1.5.x must be installed manually prior to installing the Lotus Notes Client Add-In software.

Lotus Client Add-In is supported only as 32-bit component on a Microsoft Windows x64 platform.

The Lotus Notes Client Add-In can be installed on the following platforms:
  • Microsoft Windows Server 2008
  • Microsoft Windows 7 Editions
  • Microsoft Windows Vista Editions
  • Microsoft Windows XP Editions

*Server Editions are not commonly used for the Client Add-In

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