Planning the MediaAgent Installation

For a successful installation, some careful planning is required to ensure that Commvault integrates seamlessly with your environment.

Use the following checklist to prepare the computer where the MediaAgent will be installed:

Verify System Requirements

Make sure that the computer's operating system and hardware are supported by the MediaAgent. For more information, see MediaAgent System Requirements.

Verify License Requirements

Based on the licensing mechanism used in your CommCell environment, verify that the CommCell has the required licenses to use the MediaAgent. For information about licensing, see the Commvault Licensing Program Guide.

Verify Requirements for Installation Environments

If you plan to install the MediaAgent on a virtual machine, the virtual machine must be configured with fast-access storage media. Ensure that the CPU and memory resources recommended in MediaAgent System Requirements are always available for the virtual machine.

Determine the Role of Your MediaAgent

The MediaAgent can have different roles. Determine which of the following roles are required in your environment, and review their respective requirements:

Role	Requirements
MediaAgent as a Data Mover	The MediaAgent computer must meet the requirements specified in MediaAgent System Requirements.
MediaAgent to host the Deduplication database (DDB)	The MediaAgent computer must meet the requirements specified in Deduplication Building Block Guide.
MediaAgent to host the Index Cache	The MediaAgent computer must meet the index cache requirements: Hardware Requirements.
MediaAgent for Snap Copy	The client computer where you want to perform IntelliSnap backups must meet the MediaAgent requirements specified in MediaAgent System Requirements.

Download the Software

Choose one of the following methods to download the software:

If you plan to install from the CommCell Console, no action is required. The Commvault software is automatically downloaded during the installation.

Note

Before you use the CommCell Console to perform installations, you must review the Prerequisites for Installations Using the CommCell Console.
If you plan to use the installation package, make sure that the package includes the MediaAgent software. If missing, create a new installation package and include the software. For instructions, see Downloading Software for Windows Computers Using the Download Manager.

Note

The installation package that you used to install the CommServe software is Windows-based. If you need to install on UNIX computers, see Downloading Software for UNIX, Linux, and Macintosh Computers Using the Download Manager.

Determine the Configurations that Meet Your Requirements

Every environment has different requirements. Consider the following additional configurations and information prior to completing your installation planning:

For Windows Computers

Install Commvault in a New Instance

If Commvault is already installed on the computer, but your environment requires the MediaAgent in a separate instance, you can install the MediaAgent in a new instance. For more information, see Multi-Instance Installations.

Configure a Floating Host Name

A floating host name is a virtual host name that is useful in those scenarios when the MediaAgent needs to be moved or changed at some point in time. For example, the floating name minimizes the downtime for failover operations when the MediaAgent undergoes a hardware refresh. For more information, see Configuring a Floating Host Name for the CommServe or MediaAgent Software.

For UNIX Computers

Install as a SUDO User With Root Privileges

If you want to install as a SUDO user, add the SUDO user to the /etc/sudoers file. For more information, see Adding SUDO Users with Root Privileges on a UNIX Client.

Install as a Non-Root User

If the computer where you want to run the installation does not have a root user defined, you can install agents as a non-root user. Before the installation, review the considerations described in Installation of UNIX Agents by a Non-Root User.

Install in a Predefined Directory or Mount Point

If you want to install in a predefined directory, review the considerations described in Installation of UNIX Agents in a Predefined Directory.

Install Commvault in a New Instance

Change the Branding of the Installation Package

You can change the software name to a different name, such as your organization's name. For more information, see Changing the Branding of a UNIX Installation Package.

Configure the Kernel Parameter

You can configure or modify the kernel parameters on the MediaAgent. For more information, see Kernel Parameter Configuration.

Installing MediaAgent on Cloud / Virtual Environments

Installing MediaAgent on cloud or virtual environment is supported. For more details about AWS and Azure Sizing, see the following:

MediaAgent Placement Recommendation

You can refer to the following recommendations when installing the MediaAgent on cloud or virtual environment:

Install the MediaAgent that hosts the DDB in the same region as that of the workload that is protected.
Install the MediaAgents in a common GridStor configuration within a single zone.
Install the Access Node (VSA Proxy) in a common pool within a single zone.
Install the MediaAgents across multiple zones in the same region where high-availability is required. However, this will incur transfer fees in and out of the zone. For more information about data transfer cost, contact the AWS support.
Install the Access Nodes (VSA Proxy) across multiple zones in the same region where high-availability is required. However, this will incur transfer fees in and out of the zone. For more information about data transfer cost, contact the AWS support.

The following are not supported:

Distributing MediaAgents in a common GridStor configuration across regions, as latency affects the backup performance when the source host and the MediaAgents are separated by WAN distances.
Distributing Access Nodes in a pool that spans regions, as latency affects the backup performance when the source host and the Access Node are separated by WAN distances.