Setting Up Client Communication With the CommServe

In the CommServe LiveSync setup, a client (or clients) is used as the proxy to route requests and responses between the CommServe server and the clients in the CommCell, before and after a failover.

By default the SQL clients installed on the CommServe hosts are used as the proxy . If necessary, you can disable the SQL clients as the proxy client or use an alternate client to act as a proxy.

Before You Begin

  • Verify the Firewall and Network Requirements described in Planning for CommServe LiveSync Setup.
  • Ensure that the tunnel port on the proxy client is accessible to both the CommServe hosts and the clients in the CommCell.

    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.
    This is an important requirement, irrespective of the option selected for communication. By default, the production and standby CommServe hosts reach each other using port 8408 (proxy client tunnel port).

  • Run the CommServe Port Forwarding Gateway Configuration workflow to open the necessary ports required to communicate across third-party firewalls such as the following:
    • When you plan to setup a standby CommServe host in a cloud
    • When a remote application needs an ODBC connection to the CommServe host, such as the Web Serve and/or Workflow Engine
    • When there is a firewall between the CommServe and other Commvault entities, such as Web Server, Web Console, Java GUI, Custom Reports Engine, Workflow Engine, and Cvcloud

    For more information on this workflow, see Setting Up a Standby CommServe Using Port Forwarding Gateway Configuration.


  1. On the CommCell Console ribbon, in the Home tab, click Control Panel.

    The Control Panel dialog box appears.

  2. In the CommCell group, click CommServe LiveSync.

    The CommServe LiveSync dialog box appears.

  3. In the Connectivity tab, from the Configure proxy options, select the method to communicate with the CommServe. Choose from the following options:

    Use Network Gateway

    Choose this option to specify dedicated proxy computer(s) as a network gateway that routes requests to the CommServe. One or more clients can be used as a network gateway (or proxy). Use the drop-down list to select the client group containing the client(s) that must be used as a network gateway. Make sure that a client group with the appropriate client(s) is created before selecting this option.

    By default the Failover clients client group containing the SQL Client installed on Instance002 of Commvault software is used. Make sure that all clients can communicate with the SQL client in the active CommServe, on the tunnel port. By default, port 8408 is used as the tunnel port. (To view the port, right-click the SQL client on the active CommServe host > Properties > Network > Summary. The tunnel ports are displayed under [incoming].) A network topology will be automatically created and both the SQL clients will act as the proxy (or network gateway). All the remote clients will communicate with the CommServe using these SQL clients.

    Note: Make sure that remote clients are able to connect to the network gateway client on the tunnel port.

    If a dedicated network gateway group is selected, make sure that all remote clients are able to connect to that dedicated network gateway clients on the tunnel port. The default tunnel port for the network gateway group is 8403.

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

    Network routes are automatically configured and pushed to all or some of the clients based on your selection. Make sure that all the client can resolve and connect to the proxy port.

    Manually Select Clients for External Client Group

    When selected, the [External Clients for Failover] Client Group is emptied, so that the necessary clients can be manually added to this client group.

    Use Existing Configuration

    Choose this option to use an alternate method for re-pointing the clients after a failover. For example, if you plan to use your existing network configuration or while using the sCSINTERFACELIST additional setting, described in Configuring Multiple CommServe Hostnames for Disaster Recovery.

    Note: Network routes to facilitate communication will NOT be created under the Network Topologies node in the CommCell Browser. Hence, you must ensure that your network configuration will work after a failover.

  4. Click OK.


Depending on the selection, appropriate network routes will be automatically created under the Network Topologies node in the CommCell Browser.

Additional Information

  • Irrespective of the options selected in this dialog box, the Network Topology created for failover clients topology is always created to provide one-way firewall between internal and external client groups for routing connections from CommServe and MediaAgent to the failover clients (or the SQL instances). For more information on this topology, see Network Topologies and Clients Groups Created for CommServe LiveSync.
  • When the CommServe LiveSync operation is enabled, by default, multiple CommServe hostnames is automatically enabled for all the clients in the CommCell, using the sCSINTERFACELIST additional setting on the Clients For Commserv LiveSync client group. This ensures that the clients can reach either the production or standby CommServe host, whichever is active. For more information on this setting, see Configuring Multiple CommServe Hostnames for Disaster Recovery.

Last modified: 5/25/2021 6:06:58 PM