V11 SP8

System Requirements for Virtual Server Agent with Microsoft Azure

Azure Version

Commvault  software is supported for virtual machines deployed in Azure Classic or Azure Resource Manager (ARM).

For virtual machines deployed in Azure Classic, data recovery to Premium storage accounts is not supported. This restriction applies for Live Sync, VM conversion, and VM restore jobs. 

Virtual Server Agent Proxy Requirements

A physical machine or an Azure virtual machine with the Virtual Server Agent (VSA) installed can act as a VSA proxy to perform backups and restores.

For best results, deploy the VSA proxy and MediaAgent on virtual machines in the Azure cloud.

Deploying the VSA proxy on an Azure VM that is optimized for I/O intensive workloads will support faster backups. See Sizes for virtual machines in Azure for more information.

A VSA proxy must meet the following requirements:

  • The VSA proxy machine must run one of the following operating systems:
    • Windows Server 2016
    • Windows Server 2012 R2 and later
    • Windows Server 2008 R2 SP1 and later (requires .NET Framework 4.5)
  • Minimum of 100 GB disk space.
  • Minimum of 4 GB RAM, beyond the requirements of the operating system and any other running applications.

    If the CommServe software, MediaAgent, and VSA are all installed on the same Azure VM, provide a minimum of 10 GB RAM.

  • A VSA proxy deployed on a virtual machine in Azure must have a public IP address. 
  • A VSA proxy for Azure Classic must have an Azure management certificate installed
  • If the Azure subscription includes multiple regions, deploy at least one VSA proxy per region.

Guest Operating Systems

Virtual machines being backed up can have any of the guest operating systems that are supported by the Azure platform.

Firewall Requirements

Tunnel ports (for example, 8400 and 8403) must be opened in the security group for the instance to enable installation of the Virtual Server Agent to Azure virtual machines and communication with the CommServe system.

If you deploy a CommServe host in an environment with firewalls, create a persistent route from the CommServe host to the VSA proxy, as documented in Setting Up Proxy Connections Using a Predefined Firewall Topology. Specify the RESTRICTED setting for connections from the CommServe host to the VSA proxy (step 3 under If you chose not to use predefined firewall topologies) and the BLOCKED setting in the CommServe node settings for the proxy (step 9).

If a firewall proxy is installed, configure Internet options for the firewall proxy machine. On the HTTP Proxy tab of the Internet Options dialog box, enter the user name and password for the firewall proxy machine, using only the user name and not including the domain name with the user name.


Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software.

Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.