Preinstallation Checklist for the Virtual Server Agent on Windows
Use this preinstallation checklist to prepare the computer where you will install the Virtual Server Agent, and to gather all the information you will need during the installation.
Note: When you install or upgrade to V11 Service Pack 4 or later on a machine where the Virtual Server Agent is installed, .NET framework 4.5 (for Windows machines) and the latest VDDK driver (for VMware) are installed if they are not already present. After these components are installed, you must reboot the machines where they were installed.
Verify System Requirements
Based on your virtual environment, verify that the computer where you will install the agent satisfies the minimum requirements specified on the system requirements page for your operating system:
- System Requirements for Amazon
- System Requirements for Citrix Xen
- System Requirements for Huawei FusionCompute
- System Requirements for Microsoft Azure
- System Requirements for Virtual Server Agent with Microsoft Azure Stack
- System Requirements for Microsoft Hyper-V
- System Requirements for Nutanix AHV
- System Requirements for OpenStack
- System Requirements for Oracle Cloud Classic (deprecated)
- Oracle Cloud Infrastructure: System Requirements (only supported from the Command Center)
- System Requirements for Oracle VM
- System Requirements for Red Hat Virtualization
- System Requirements for vCloud
- System Requirements for VMware
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.
Where to install the software
When configuring a virtualization client, you must provide user credentials as follows:
- For Amazon, define policies for user permissions. For more information, see Amazon Web Services User Permissions for Backups and Restores.
- For Citrix Xen, collect credentials for the root user or a user account having the Pool Administrator (Pool Admin) role.
- For FusionCompute, obtain administrator user credentials for the Virtual Resource Manager (VRM).
- For Microsoft Azure credentials, see Setting Up an Application and Tenant for Azure Resource Manager.
- For Microsoft Azure Stack, see Setting Up an Application and Tenant for Azure Stack.
- For Microsoft Hyper-V, the user account credentials that are used to access the Hyper-V server or cluster for your virtualization instance must be part of the following administrator groups on the Hyper-V host:
- Hyper-V Administrators group
- For Windows Hyper-V Server 2008 R2, Local Administrators group
- For a Hyper-V cluster, the user account must have full Cluster Permissions (Read and Full Control).
- 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 Classic (deprecated), identify the endpoint that can be used to access Oracle Cloud and collect administrator user credentials.
- 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. For more information, see Configuration of User Accounts for VMware.
Before installing the Virtual Server Agent, review the following deployment options for your virtualization platform to understand how to optimize operations for your environment.
- Deployment - Virtual Server Agent for Amazon
- Deployment Planning for Citrix Xen
- Deployment for FusionCompute
- Deployment for Microsoft Azure
- Deployment for Microsoft Azure Stack
- Deployment Planning for Microsoft Hyper-V
- Deployment for Nutanix AHV
- Deployment for OpenStack
- Deployment for Oracle Cloud Classic (deprecated)
- Adding an Oracle Cloud Infrastructure Hypervisor (only supported from the Command Center)
- Deployment for Oracle VM
- Deployment Planning for Red Hat Virtualization
- Deployment for vCloud
- Deployment Planning for VMware
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
Install the Virtual Server package, which is under the Virtualization category.
- The VSS Provider package is installed as part of the Virtual Server Agent installation. (This package is not required for Citrix Xen.)
- 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 a license.
To gather the required information for the File System Agent, refer to "Gather Installation Data" in the Preinstallation Checklist for the Windows 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.
Last modified: 3/10/2020 9:47:31 PM