Planning for CommServe LiveSync Setup

Verify that the prerequisites needed to setup the environment are available before setting up the CommServe LiveSync.

Note: Identical software must be used for setting up the production and the standby CommServe hosts. Ensure that the Operating System and SQL Server version (including service packs) are identical in the both the production and standby hosts.


You must have the necessary hardware for setting up the CommServe server on the production host and the standby hosts. More than one standby host is supported.

For more information on the hardware specification for the CommServe server, see Hardware Specifications for the CommServe Server.

Operating System

CommServe LiveSync can be set up on all operating systems supported by the CommServe server.

For more information on the supported operating systems, see CommServe Server: System Requirements.

Note: CommServe LiveSync is not supported when the CommServe server is configured with Microsoft Failover Cluster.

License Requirements

  • CommServe Server

    No special licenses are required for setting up the CommServe server.

  • SQL Server Agent

    You must have two Microsoft SQL Server agent licenses, one for the production CommServe host and the other for the standby CommServe host.

For information about licensing, see the Commvault Licensing Program Guide.

Installation Packages

The following Commvault installation packages are required for setting up the production and standby CommServe hosts:

  • CommServe

    Additional packages are installed by default during the CommServe installation. For more information, see the Additional Packages Installed with the CommServe section in Preinstallation Checklist for the CommServe.

  • CommServe Failover

    The SQL Server agent and the CommServe Failover package are automatically installed in a new instance. (No additional user intervention is needed.)

Firewall and Network Requirements

By default, this solution requires that all clients communicate with the CommServe server using a proxy. (By default, the SQL Clients installed in the CommServe hosts is used as the proxy.)

Note: A default topology, Firewall Topology created for failover clients, is created for communication between the production and standby CommServe hosts using port 8408. This default topology routes requests between the CommServe and the SQL instances and is created irrespective of the option selected for communication.
Hence, it is important to verify and ensure that production and standby CommServe hosts are able to reach other using port 8408.

To facilitate communication between the clients and the CommServe, verify the following conditions:

  • Both the active host and the passive CommServe hosts can reach the tunnel ports that are associated with the SQL clients in both the active host and the passive CommServe hosts.
  • If the SQL clients are used as the proxy, verify that all the clients in the CommCell environment can communicate with the port and hostname of the SQL clients in both the active host and the passive CommServe hosts.
  • If a dedicated proxy is already set up and available in your environment, use this dedicated proxy to communicate with the CommServe server.

    Note: A dedicated proxy is recommended in environments with a large number of clients. (5000 or more approximately.)

  • To failover to a CommServe hosted in the cloud, or if there is a firewall between the active host and the passive CommServe hosts, see Setting Up a Standby CommServe Using TPPM.

    See Also: Network TCP Port Requirements.


Using a Floating CommServe Name

You can use a floating CommServe hostname to setup the CommServe failover. A floating CommServe hostname can be used either as an alternative to setting up a dedicated proxy, or in combination with an existing proxy setup.

See Setting Up Failovers Using A Floating CommServe Name for more information.

Last modified: 3/4/2020 7:03:30 PM