System Requirements - MediaAgent

The following requirements are for the MediaAgent:

Operating System

Processor

AIX

AIX 5.2 32-bit with maintenance level 7 and runtime library xlC.rte 8.0.0.0 or higher FIELD CERTIFIED

AIX 5.2 64-bit with maintenance level 7 and runtime library xlC.rte 8.0.0.0 or higher FIELD CERTIFIED

AIX 5.2 32-bit with technology level 10 and runtime library xlC.rte 8.0.0.0 or higher

AIX 5.2 64-bit with technology level 10 and runtime library xlC.rte 8.0.0.0 or higher

AIX 5.3 32-bit with technology level 6 and runtime library xlC.rte 8.0.0.0 or higher

AIX 5.3 64-bit with technology level 6 and runtime library xlC.rte 8.0.0.0 or higher

AIX 6.1 64-bit

 RS/6000 43P Model 150 – 375 MHZ or higher; Dual Processors recommended

HP-UX

HP-UX 11i v1 (11.11) 32-bit with OS patch PHCO29328 (contact Hewlett Packard to obtain the patch) 

HP-UX 11i v1 (11.11) 64-bit with OS patch PHCO29328 (contact Hewlett Packard to obtain the patch)

HP-UX 11i v2 (11.23) 64-bit

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

HP-UX -PA RISC 300 MHZ or higher; Dual Processors recommended
  HP-UX 11i v2 (11.23) 64-bit

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

Intel Itanium

 

Linux

CentOS

CentOS 4.6 with glibc 2.3.x

CentOS 5 with glibc 2.5.x FIELD CERTIFIED

Intel Pentium or compatible minimum required
 

CentOS 4.6 with glibc 2.3.x

CentOS 5 with glibc 2.5.x FIELD CERTIFIED

x64

 

Oracle Enterprise Linux

Oracle Enterprise Linux 5 with glibc 2.5.x

Intel Pentium, x64 or compatible processors
 

Red Flag Linux

Red Flag Linux AS 4.1 32-bit with glibc 2.3.x

 Intel Pentium or compatible 650 MHz processor minimum recommended; Dual 1 GHz or higher processors recommended
 

Red Hat Enterprise Linux AS/ES

Red Hat Enterprise Linux AS/ES 3.0 with glibc 2.3.x

Red Hat Enterprise Linux AS/ES 4.0 with glibc 2.3.x

Intel Pentium or compatible 650 MHz processor minimum recommended; Dual 1 GHz or higher processors recommended
 

Red Hat Enterprise Linux AS/ES 3.0 with glibc 2.3.x

Red Hat Linux AS 4.0 with glibc 2.3.x

Intel Itanium

 
 

Red Hat Enterprise Linux AS/ES 3.0 with glibc 2.3.x

Red Hat Enterprise Linux AS/ES 4.0 with glibc 2.3.x

x64

 
 

Red Hat Linux AS 4.0 with glibc 2.3.x

Power PC (Includes IBM System p)
 

Red Hat Linux ES 4.0 with glibc-2.3.x FIELD CERTIFIED

Intel Pentium or compatible 650 MHz processor minimum recommended; Dual 1 GHz or higher processors recommended
 

Red Hat Enterprise Linux

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

Intel Pentium or compatible 650 MHz processor minimum recommended; Dual 1 GHz or higher processors recommended

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

Intel Itanium

 

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

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

Power PC (Includes IBM System p)

SuSE Linux

SuSE Linux 9.0 Enterprise Server Edition with glibc 2.3.x

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

SuSE Linux 11 Enterprise Server Edition with glibc 2.9.x

 Intel Pentium or compatible 650 MHz processor minimum recommended; Dual 1 GHz or higher processors recommended

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

SuSE Linux 11 Enterprise Server Edition with glibc 2.9.x

Intel Itanium

 

SuSE Linux 9.0 Enterprise Server Edition with glibc 2.3.x

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

SuSE Linux 11 Enterprise Server Edition with glibc 2.9.x

x64

 

SuSE Linux 9.0 Enterprise Server Edition with glibc 2.3.x

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

SuSE Linux 11 Enterprise Server Edition with glibc 2.9.x

Power PC (Includes IBM System p)

NetWare

 NetWare 6.5 up to Support Pack 8

Intel Pentium or compatible minimum required
  The NetWare MediaAgent / iDataAgents are installed on a NetWare server using a Novell client computer, with Novell Client 4.9 on one of the following operating systems:

Microsoft Windows XP Professional

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

Solaris

Solaris 8 32-bit with Service Packs 108434-09, 108435-09, and 109147-20

Solaris 8 64-bit with Service Packs 108434-09, 108435-09, and 109147-20

Solaris 9 4/04 32-bit

Solaris 9 4/04 64-bit

Solaris 10 64-bit

 Sun Ultra5 station or higher; Dual Processors recommended
Solaris 10 64-bit

x64

 

Tru64

Tru64 OSF1 Release 5.1B-3

Compaq® (DEC) AlphaServer DS Series computer or higher recommended

Windows

Windows Server 2003

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

Microsoft Windows Server 2003 32-bit Editions** with a minimum of Service Pack 1 (as guest OS/virtual machine) on VMware GSX and ESX

Windows Server 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

Microsoft Windows Server 2008 R2 Editions*

*Web Server Editions not supported

**On VMware virtual machines, Hyper-V virtual machines, and Hyper-V R2 Core machines, Magnetic Library configuration is supported.

All Windows-compatible processors supported

 

Cluster Support

See Clustering - Support

Memory

4 GB RAM minimum required; 8 GB RAM recommended if MediaAgent with x64 is used with Deduplication

Virtual memory should be set to twice the amount of available physical memory

Hard Disk

Windows

130 MB for the MediaAgent software and log file growth/ 298 MB recommended

Enough additional local disk space to accommodate the index cache (with a minimum of 256 MB). It is recommended that the index cache is configured to be written on a partitioned drive, used exclusively for holding index cache. For information on calculating the space requirements for index cache, see Calculating the Storage Space Required for Index Cache.

85 MB of temp space required for install or upgrade (where the temp folder resides)
An undersized index cache can result in degraded backup and restore performance. A severely undersized index cache can render backups and restores on that MediaAgent inoperable.

MediaAgent installation and upgrade require additional 200 MB of free disk space on the drive in which the Operating System and temp directory resides, to copy temporary files during the install or upgrade process.

Unix

250 MB for the MediaAgent software and log file growth

Peripherals

DVD-ROM drive

Network Interface Card. For NetWare MediaAgents, if NetWare AHA 2944 card is used, driver version 8.30.13 (or later) must be installed for this card.

SCSI bus adapter for each attached media library

Sufficient hard disk space when backing up to magnetic drives.

Swap space = 2*RAM size

Media library or stand-alone drive attached to local SCSI adapter(s), backup device available through Storage Area Network (SAN), or magnetic disk partitions for backup data.
Contact your software provider, for a list of supported storage devices (libraries, drives, media and SAN devices) and compatible SCSI cards.

Miscellaneous

TCP/IP Services configured on the computer.

For NetWare MediaAgents, IP protocol enabled and binded to the specific Network Interface Card (NIC).

Drivers for SCSI Adapters (Supplied by your SCSI Adapter provider)

Drivers for media drives (Supplied by your media drive provider)

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.

Notes on MediaAgent Installation

The MediaAgent should not be installed on a compressed drive.

The Netware File System iDataAgent will be automatically installed during installation of the Netware MediaAgent, if it is not already installed. For System Requirements specific to the File System iDataAgent, refer to System Requirements - NetWare Server iDataAgents.

For information on installing the MediaAgent software on the Microsoft Virtual Server, see Considerations for backing up the Microsoft Virtual Server.

Notes on Combined Installations

You will often install more than one module (For example, CommServe, MediaAgent, Client) on a single computer so that it can perform two or more functions. For example, you may want to back up the file system of a MediaAgent; hence, you would install both the MediaAgent and client software on that computer.

When you combine two or more functions on a single computer, the storage resources required to support the software for that computer are not essentially cumulative. This is because modules share some of the same software. As a result, combined installations require about 30 MB less disk space than installations where the software resides on separate computers.

(If CommServe, MediaAgent and Client software are installed on the same computer.)

Contact your software provider, for a list of supported storage devices (libraries, drives, media and SAN devices) and compatible SCSI cards.

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.