Microsoft SQL Server Native Client ODBC Driver

Applies To: Traffic between the Web Server and the CommServe computer

If a firewall is placed between the Web Server 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 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. Set up connectivity to your static listener ports as follows:

   • To route ODBC connection requests through a network proxy using Commvault firewall settings, complete the steps in Configuring Third-Party Connections Between Client Computers providing the following details:

     • Source client: The Web Server computer.

     • Source port: Any port that you want to set as a third-party port (preferably the same as the destination port). This port will be defined in the outgoing route tppm=[Local_port] of the firewall configuration file.

     • Destination client: The CommServe computer.

     • Destination port: The static listening port that you set on the SQL Server instance.

   • To configure a Windows firewall, see the Microsoft article "Configure the Windows Firewall to Allow SQL Server Access".

   • To configure a hardware-based firewall device, consult the manufacturer's documentation.

3. On the Web Server 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.

4. In the SQL Server Configuration Manager on the Web Server 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 127.0.0.1\Commvault.

      • In the Port No box, enter the TPPM source port originating from the Web Server to the CommServe computer.

      • In the Protocol box, enter TCP/IP.

      • In the Server box, enter 127.0.0.1\Commvault.

   2. Click OK.

5. In the ODBC Data Source Administrator (64-bit) on the Web Server 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 computer.

     2. In the ODBC Data Source Administrator (64-bit) dialog box, on the System DSN tab, select the WebServerHost_CommServ system data source (SQL Server Native Client driver), and then click Configure.

     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 WebServerHost_CommServ system data source (SQL Server Native Client driver), and then click Configure.

     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.

6. From the CommCell Console, create an additional setting on the Web Server client with the following values:

   • Name: nPORT

   • Category: Database

   • Type: Integer

   • Value Data: The Source port value that you entered in Step 2, above.

     Note

     For more information see nPORT additional setting description.

7. Restart all services on the Web Server computer.