System Requirements - Image Level ProxyHost iDataAgent

  This feature/product/platform is deprecated in this release. See Deprecated Features, Products, and Platforms for more information.

The following requirements are for the Image Level ProxyHost iDataAgent:

If using this Agent with a snapshot engine, refer to System Requirements- Image Level ProxyHost  iDataAgent - Snapshots Support information on the operating system vendors supported for each snapshot engine with this Agent.

Operating System

Processor

Linux

Red Hat Enterprise Linux

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-78 (Update 7)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-67 (Update 6)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-55 (Update 5)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-42 (Update 4)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-34 (Update 3)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-71

x64

Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-71

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-92 (Update 2)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-8

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-53 (Update 1)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-238 (Update 6)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-238 (Update 6)

x64

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-194 (Update 5)

x64

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-194 (Update 5)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update 4)

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update 4)

x64

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-128 (Update 3)

Intel Pentium or compatible minimum required

SuSE Linux (SLES)

SuSE Linux 11 Enterprise Server with kernel 2.6.32.12-0.7 (Update 1)

Intel Pentium or compatible minimum required

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.21 (Update 2)

Intel Pentium or compatible minimum required

SuSE Linux 10 Enterprise Server with kernel 2.6.16.46-0.12 (Update 1)

Intel Pentium or compatible minimum required

Solaris

Solaris 9 with a minimum of Service Packs 111711-02

Sparc5 or higher recommended

Solaris 10.x

Sparc5 or higher recommended

Windows

Windows 2008

Microsoft Windows Server 2008 R2 Editions*

*Core Editions not supported

All Windows-compatible processors supported

Microsoft Windows Server 2008 32-bit and x64 Editions*

All Windows-compatible processors supported

Windows 2003

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

All Windows-compatible processors supported

Hard Drive

Linux and Solaris

240 MB minimum of hard drive space for software 

100 MB of additional hard disk space for log file growth

10 MB of temp space required for install or upgrade (where the temp directory resides)

Windows

116 MB minimum of hard disk space for software/ 549 MB recommended

50 MB of additional hard disk space for log file growth

83 MB of temp space required for install or upgrade (where the temp folder resides)

Memory

Windows

32 MB RAM minimum required beyond the requirements of the operating system and running applications

Linux and Solaris

16 MB RAM minimum required beyond the requirements of the operating system and running applications

Swap space = 2*RAM size

Cluster Support

The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems. For information on supported cluster types, see Clustering - Support.

Peripherals

DVD-ROM drive

Network Interface Card

Fiber Channel card (HBA) if the data to be protected resides on SAN-attached volumes

Miscellaneous

The File System iDataAgent will be automatically installed during installation of this software, if it is not already installed. For System Requirements specific to the File System iDataAgent, refer to System Requirements - Microsoft Windows File System iDataAgent.
On Solaris computers, the operating system must have been installed with at least the user level software option selected.

Network

TCP/IP Services configured on the computer.

.NET Framework

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

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.

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