Configuring Access to the Commvault MongoDB Using a Port-Forwarding Gateway

To serve the Command Center features such as the global search, listing pages, and dashboards, all Commvault Web Servers access a single designated Commvault MongoDB which provides data to support the mentioned features. If firewall restrictions prevent these Web Servers from connecting to the designated MongoDB instance, you must configure a Commvault network gateway to establish a successful connection.

Procedure

1. To identify the Web Server machine running the designated MongoDB, execute the following query in Commvault SQL server instance which will provide the ID of the client running the designated MongoDB instance:

   use CommServ;

   exec AppGetDefaultWebserverId;

   which returns the Web Server client ID where the default MongoDB is installed.

   Note

   This designated MongoDB will always be running on a Web Server client.

2. Navigate to the Commvault installation directory on the Web Server machine returned from step 1, and then open the MongoDB configuration located in the following path:

   For Windows: <commvault_installation_directory>\ContentStore\MongoDB\Server\cvmongod.cfg

   For Unix: <commvault_installation_directory>\MongoDB\Server\cvmongod.conf

3. Copy the net::port value that indicates the port where the MongoDB is running.

4. Configure the network route between the remote Web Server and the designated MongoDB (running on the Web Server).

5. To map the port-forwarding gateway to the designated MongoDB port via network routes, run the ConfigureThirdPartyConnections workflow with the following values:

   • Source client: Remote WebServer client

   • Source port number: Local port on the Remote WebServer client

   • TPPM type: None

   • Destination client: Designated MongoDB (running on the Web Server)

   • Destination port number: Port of designated mongoDB server mentioned in Step 3.

6. Restart IIS services on the remote Web Server:

   1. In the command prompt, type iisreset.

   2. Press Enter.