System Requirements - MediaAgent

The following requirements are for the MediaAgent:

Operating System		Processor
AIX	AIX 7.1	Power PC (Includes IBM System p)
	AIX 6.1 64-bit	RS/6000 43P Model 150 - 375 MHZ or higher; Dual Processors recommended
	AIX 5.3 64-bit with technology level 6 and runtime library xlC.rte 8.0.0.0 or higher	RS/6000 43P Model 150 - 375 MHZ or higher; Dual Processors recommended
	AIX 5.3 32-bit with technology level 6 and runtime library xlC.rte 8.0.0.0 or higher Note that all AIX platforms support Logical Partitions (LPAR).	RS/6000 43P Model 150 - 375 MHZ or higher; Dual Processors recommended
HP-UX	HP-UX 11i v3 (11.31) 64-bit	Itanium
	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 -PA RISC 300 MHZ or higher; Dual Processors recommended
	HP-UX 11i v2 (11.23) 64-bit	Itanium
	HP-UX 11i v1 (11.11) 64-bit with a minimum of OS patch level of December 2008 patch bundle or higher (contact Hewlett Packard to obtain the patch)	HP-UX -PA RISC 300 MHZ or higher; Dual Processors recommended
	HP-UX 11i v1 (11.11) 32-bit with a minimum of OS patch level of December 2008 patch bundle or higher (contact Hewlett Packard to obtain the patch)	HP-UX -PA RISC 300 MHZ or higher; Dual Processors recommended
Linux	Oracle Linux
	Oracle Linux 5.x 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 Linux AS 4.0 with glibc 2.3.x	Power PC (Includes IBM System p)
	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 4.0 with glibc 2.3.x	Itanium
	Red Hat Enterprise Linux AS/ES 4.0 with glibc 2.3.x	x64
	Red Hat Enterprise Linux AS 5.x with glibc 2.5	x64
	Red Hat Enterprise Linux/CentOS
	Red Hat Enterprise Linux/CentOS Server 5 with glibc 2.5.x	Power PC (Includes IBM System p)
	Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x	Intel Pentium, Itanium, x64, Power PC (Includes IBM System p) or compatible processors
	Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x	Intel Pentium, Itanium, x64, Power PC (Includes IBM System p) or compatible processors
	Red Hat Enterprise Linux/CentOS 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/CentOS 5 Advanced Platform with glibc 2.5.x	Itanium, x64 or compatible processors
	SuSE Linux (SLES)
	SuSE Linux 11.x with glibc 2.9.x and above	x64
	SuSE Linux 11.x with glibc 2.9.x and above	Power PC (Includes IBM System p)
	SuSE Linux 11.x with glibc 2.9.x and above	Itanium
	SuSE Linux 11.x with glibc 2.9.x and above	Intel Pentium or compatible 650 MHz processor minimum recommended; Dual 1 GHz or higher processors recommended
	SuSE Linux 11.x with glibc 2.11.x	Intel Pentium, x64 or compatible processors
	SuSE Linux 10 Enterprise Server Edition with glibc 2.4.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	Itanium
	SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x	Power PC (Includes IBM System p)
	SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x	x64
	Ubuntu
	Ubuntu 10.04 LTS	Intel Pentium, x64 or compatible processors
Solaris	Solaris 9 4/04 64-bit	Ultra5 station or higher; Dual Processors recommended
	Solaris 9 4/04 32-bit	Ultra5 station or higher; Dual Processors recommended
	Solaris 11.x	x64
	Solaris 11.x	Ultra5 station or higher; Dual Processors recommended
	Solaris 10.x with a minimum of SunOS (Sparc) Patch 119963-14	Ultra5 station or higher; Dual Processors recommended
	Solaris 10.x 64-bit	x64
Tru64	Tru64 OSF1 Release 5.1B-3	Compaq® (DEC) AlphaServer DS Series computer or higher recommended
Windows	Windows 2012
	Microsoft Windows Server 2012 Editions See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8 for more information.	All Windows-compatible processors supported
	Windows 8
	Microsoft Windows 8 Editions* *Tape Libraries/Drives are not supported. See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8 for more information.	All Windows-compatible processors supported
	Windows 7
	Microsoft Windows 7 Editions* *Tape Libraries/Drives are not supported.	All Windows-compatible processors supported
	Windows 2008
	Microsoft Windows Server 2008 32-bit and x64 Editions* *Web Server Editions not supported	All Windows-compatible processors supported
	Windows Vista
	Microsoft Windows Vista Editions* *Tape Libraries/Drives are not supported.	All Windows-compatible processors supported
	Windows 2003
	Microsoft Windows Server 2003 32-bit, 64-bit and 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 (as guest OS/virtual machine) on VMware GSX and ESX On VMware virtual machines, Hyper-V virtual machines, and Hyper-V R2 Core machines, Disk Library configuration is supported.	All Windows-compatible processors supported
	Windows XP
	Microsoft Windows XP Editions* with a minimum of Service Pack 3 *Tape Libraries/Drives are not supported.	All Windows-compatible processors supported

Hard Drive

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 the Index Cache Directory.

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.

732 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

256 MB for the MediaAgent software and log file growth

Memory

4 GB RAM minimum required; 32 GB RAM recommended if MediaAgent is used with Deduplication. For granular details on MediaAgent sizing, refer to the Deduplication Building Block Guide.

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

A MediaAgent that is also a Catalog Server requires an additional hard disk space of 4% of the total data protected by all MediaAgents using the Catalog Server.

Peripherals

DVD-ROM drive

SCSI bus adapter for each attached media library

Sufficient hard disk space when backing up to disk 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

Network

TCP/IP Services configured on the computer.

Drivers

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

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

.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":

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)

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]#

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.

On Unix 64-bit computers, you can opt to install either the 32-bit version or 64-bit version of the agent. See Install the MediaAgent or Linux File System Deployment to run the appropriate install.

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

(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 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

System Requirements - MediaAgent

Operating System

Processor

AIX

HP-UX

Linux

Oracle Linux

Red Flag Linux

Red Hat Enterprise Linux AS/ES

Red Hat Enterprise Linux/CentOS

SuSE Linux (SLES)

Ubuntu

Solaris

Tru64

Windows

Windows 2012

Windows 8

Windows 7

Windows 2008

Windows Vista

Windows 2003

Windows XP

Hard Drive

Windows

Unix

Memory

Peripherals

Miscellaneous

Network

Drivers

.NET Framework

Microsoft Visual C++

SELinux

Notes on MediaAgent Installation

DISCLAIMER