System Requirements - Image Level ProxyHost iDataAgent

System Requirements | Snapshot Support

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 3.0 with kernel 2.4.21-15 (Update 2)

Red Hat Enterprise Linux AS 3.0 with kernel 2.4.21-47 (Update 8)

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

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

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

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

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

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

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

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

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

SuSE Linux

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.191 (Patch Level 2)

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.244 (Patch Level 3)

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.308 (Patch Level 4)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.21-0.8

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

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

Intel Pentium or compatible minimum required

Solaris

 Solaris 8 with a minimum of Service Packs 108434-09

Solaris 9 with a minimum of Service Packs 111711-02

Solaris 10 		Sun Sparc5 or higher

Windows

Windows 2003

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

Windows Server 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

Microsoft Windows Server 2008 R2 Editions*

*Core Editions not supported

All Windows-compatible processors supported

Cluster Support

See Clustering - Support

Memory

Linux and Solaris

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

Swap space = 2*RAM size

Windows

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

Hard Disk

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)

Peripherals

DVD-ROM Drive

Network Interface Card

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

Miscellaneous

TCP/IP Services configured on the computer.

The File System iDataAgent will be automatically installed during installation of the Image Level ProxyHost iDataAgent, 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.

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.

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 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 may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for 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.