> Documentation > Deployment > Installations > Client Installations > Installing Commvault Packages on Client Computers > Commvault Packages Available for UNIX, Linux, and Macintosh Computers > Virtual Server Agent

Preinstallation Checklist for the Virtual Server Agent on Linux

The Virtual Server Agent (VSA) protects all of your virtual machines and unifies the data protection of physical and virtual environments. For more information, see one of the following:

Use the preinstallation checklist to prepare the computer where the Virtual Server Agent will be installed and to gather all the information you will need during the installation.

Verify System Requirements

Based on your virtual environment, verify that the computer where you will install the agent satisfies the minimum requirements specified in the following:

Verify License Requirements

Based on the licensing mechanism used in your CommCell environment, verify that the CommCell environment has the required licenses to use the Virtual Server Agent.

For more information, see the Commvault Licensing Program Guide.

Determine the Installation Location

Based on your environment, install the Virtual Server Agent on an appropriate computer. Each computer where the Virtual Server Agent is installed serves as a VSA proxy to manage backup and restore operations.

Environment

Where to install the software

Non-Clustered

  • For Amazon, install on one or more machines or Amazon instances.

    • For backups, the VSA must be installed on an Amazon instance in each region to be protected. Each VSA proxy can protect instances in the same region.

    • For VM conversion and restores, the VSA can be installed on an Amazon instance or on an external machine.

  • For Docker, install on a 32-bit or 64-bit UNIX machine.

  • For FusionCompute, install on a Linux, UNIX, or Windows machine.

  • For Nutanix AHV, install on one or more virtual machines running in the Nutanix cluster.

  • For OpenStack, install on one or more instances running in the OpenStack data center.

  • For Oracle Cloud Infrastructure, install on an instance running in Oracle Cloud Infrastructure.

  • For Oracle VM, install on a virtual machine hosted on an Oracle VM Server that is part of the Oracle VM deployment.

  • For Red Hat Virtualization, install on one or more virtual machines in the same data center as the virtual machines to be backed up.

  • For vCloud, install on a physical machine or a vCloud virtual machine.

  • For VMware, install on one or more physical computers or virtual machines.

Clustered

  • For Amazon, install on one or more machines or Amazon instances.

    • For backups, the VSA must be installed on an Amazon instance in each region to be protected. Each VSA proxy can protect instances in the same region.

    • For VM conversion and restores, the VSA can be installed on an Amazon instance or on an external machine.

  • For Docker, install on a 32-bit or 64-bit UNIX machine.

  • For FusionCompute, install on a Linux, UNIX, or Windows machine.

  • For Nutanix AHV, install on one or more virtual machines running in the Nutanix cluster.

  • For OpenStack, install on one or more instances running in the OpenStack data center.

  • For Oracle Cloud Infrastructure, install on an instance running in Oracle Cloud Infrastructure.

  • For Oracle VM, install on a virtual machine hosted on an Oracle VM Server that is part of the Oracle VM deployment.

  • For Red Hat Virtualization, install on one or more virtual machines in the same data center as the virtual machines to be backed up.

  • For vCloud, install on a physical machine or a vCloud virtual machine.

  • Virtual Server Agent for VMware does not support clustered environments.

User Accounts

When configuring a virtualization client, you must provide user credentials as noted in the following list:

  • For Amazon, define policies for user permissions as described in Amazon Web Services User Permissions for Backups and Restores.

  • For Docker, obtain administrator user credentials for the host where Docker is installed.

  • For FusionCompute, obtain administrator user credentials for the Virtual Resource Manager (VRM).

  • For Nutanix AHV, collect credentials for a user that has Prism administrator privileges for the Nutanix cluster.

  • For OpenStack, collect credentials for a user account with administrative privileges for the keystone node.

  • For Oracle Cloud Infrastructure, add required permissions for the OCID tenant and user.

  • For Oracle VM, collect administrator user credentials for Oracle VM Manager.

  • For Red Hat Virtualization, collect credentials for a user account with administrative privileges on the RHEV Manager.

  • For vCloud, collect user credentials for a vCloud Director user with administrator privileges.

  • For each VMware vCenter, collect user credentials with appropriate permissions as described in Configuration of User Accounts for VMware.

Deployment Planning

Before installing the Virtual Server Agent, review deployment options for your virtualization platform to understand how to optimize operations for your environment.

Gather Installation Data

Refer to the items in this section to gather the information that you will need during the installation. Record the information before you begin installing the software, so that you can refer to it during the installation.

You can install the Virtual Server Agent by using either the CommCell Console or the installation package created by the Download Manager. Any item that applies to only one of these installation methods is noted.

Commvault package to install

  • For installations using the CommCell Console, install the Virtual Server package, which is listed under the Virtualization category.

  • For installations using the installation package, install the VirtualServer package.

Note

If the File System Agent is not installed on the computer, the File System Core and File System packages are automatically installed with the package you selected. The File System Agent will not consume any license.

To gather the required information for the File System Agent, refer to the Gather Installation Data section in the Preinstallation Checklist for the UNIX, Linux, and Macintosh File System Agent.

Client computer installations

If the File System Agent or another package is already installed on the computer, you are not required to gather all the computer details again. The level of detail depends on how the package you selected is installed, as follows:

  • For installations using the CommCell Console, the installation program requests only the name of the client computer.

  • For installations using the installation package, the installation program reads the details from the previous installation.

Loading...