Loading...

Preinstallation Checklist for the Virtual Server Agent on Windows

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.

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.

  • 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 Citrix Xen, install on a dedicated virtual machine on a standalone XenServer.
    • For Microsoft Azure, install on a physical server or a VM in the Azure cloud that has a public IP address configured.
    • For Microsoft Hyper-V, install on a standalone Hyper-V server.
    • 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 VM, install on a Windows virtual machine running in Oracle VM Manager.
    • 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 VMware, install on one or more Windows 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 Citrix Xen, install on one or more dedicated virtual machines on each XenServer in a Xen pool.
    • For Microsoft Azure, install on a physical server or a VM in the Azure cloud that has a public IP address configured.
    • For Microsoft Hyper-V, install on all Hyper-V servers (physical nodes) in the cluster.
    • 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 VM, install on a Windows virtual machine running in Oracle VM Manager.
    • For Red Hat Virtualization, install on one or more virtual machines in the same data center as the virtual machines to be backed up.
    • 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 Citrix Xen, collect credentials for the root user or a user account having the Pool Administrator (Pool Admin) role.
    • For Microsoft Azure, see Setting Up an Application and Tenant for Azure Resource Manager or Setting Up a Microsoft Azure Management Certificate for Azure Classic for credential requirements.
    • 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 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 each VMware vCenter, collect user credentials with appropriate permissions as described in Configuration of User Accounts 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.

    SnapProtect package to install
    Install the Virtual Server package, which is listed 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 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 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:
    • 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.