Loading...

Microsoft SQL Server Native Client ODBC Driver - Connecting the Web Server or Workflow Engine to the CommServe Computer

Applies To: Traffic between the Web Server/Workflow Engine and the CommServe computer

If a firewall is placed between the Web Server/Workflow Engine and the CommServe computer, you must configure the firewall to allow traffic between the two computers.

About This Task

  • Setting static ports is recommended because lost communication can occur if dynamic ports are used when the SQL Server instance is restarted.
  • Configuring the communication between the Web Server /Workflow Engine and CommServe computer requires updating connection parameters in the ODBC Data Source Administrator. For instructions on how to use the ODBC Data Source Administrator, consult the Microsoft documentation.

Procedure

  1. On the CommServe computer, ensure that the CommServe instance is set to listen on static port.

    For more information, go to the Microsoft article "Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)".

  2. On the Web Server/Workflow Engine computer, open the Windows Registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\Database\sINSTANCE, and then update Value data to 127.0.0.1\Commvault.
  3. In the SQL Server Configuration Manager on the Web Server or the Workflow Engine client machine, go to SQL Native Client 11.0 Configuration > Aliases and create a new alias.
    1. In the Alias - New dialog box, enter the following information:
      • In the Alias Name box, enter an alias name.
      • In the Port No box, enter the TPPM source port that you entered during the Setting Up a Standby CommServe Using TPPM. If you did not enter a TPPM source port during the workflow, you can find the port number by viewing Properties > Network > Summary on the Web Server or the Workflow Engine client.
      • In the Protocol box, enter TCP/IP.
      • In the Server box, enter 127.0.0.1\Commvault.
    2. Click OK.
  4. In the ODBC Data Source Administrator (64-bit) on the Web Server or the Workflow Engine computer, update the connection parameters as follows:
    • If you configured a network proxy using Commvault firewall settings, do the following:
      1. Access the Web Server or the Workflow Engine computer.
      2. In the ODBC Data Source Administrator (64-bit) dialog box, on the System DSN tab, select the <ServerHost>_CommServ system data source (SQL Server Native Client driver), and then click Configure.

        Where:

        <ServerHost> is the short name of the Web Server or Workflow Engine.

      3. On the Microsoft SQL Server DSN Configuration page, enter a name and description, and in the Server box, enter 127.0.0.1\Commvault.
      4. Click Finish.
    • If you configured a Windows firewall or a hardware-based firewall device, do the following:
      1. In the ODBC Data Source Administrator (64-bit) dialog box, on the System DSN tab, select the <ServerHost>_CommServ system data source (SQL Server Native Client driver), and then click Configure.

        Where:

        <ServerHost> is the short name of the Web Server or Workflow Engine.

      2. On the Microsoft SQL Server DSN Configuration page, enter a name and description, and in the Server box, enter 127.0.0.1\Commvault.
      3. Click Finish.
  5. From the CommCell Console, create an additional setting on the Web Server and/or the Workflow Engine client with the following values:
    • Name: nPORT
    • Category: Database
    • Type: Integer
    • Value Data: The Source port value that you entered during the Setting Up a Standby CommServe Using TPPM. If you did not enter a TPPM source port during the workflow, you can find the port number by viewing Properties > Network > Summary on the Web Server or Workflow Engine.

      Note: For more information see nPORT additional setting description.

  6. Download and run the QScript SetDBProxy.sqle script as follows, so that while running reports, it will use the localhost and TPPM port to connect to the CommServe database.
    1. Download the QScript SetDBProxy.sqle script from the Commvault Store.
    2. Move the script to the base folder on the CommServe computer.
    3. Run the following command from the CommServe computer:

      Qscript -f SetDBProxy.sqle -i commCellName proxyHostName proxyPortNumber

      Where:

      • commCellName = CommServe client name
      • proxyHostName = 127.0.0.1
      • ProxyPortNumber = TPPM source port that you entered during the Setting Up a Standby CommServe Using TPPM. If you did not enter a TPPM source port during the workflow, you can find the port number by viewing Properties > Network > Summary on the Web Server and/or the Workflow Engine client.
  7. Restart all services on the Web Server and/or the Workflow Engine computer.

What to Do Next

Follow the procedure in Configuring Access to the SMTP Server Using TPPM.

Last modified: 3/28/2019 7:05:12 PM