Setup for Global Command Center

The Global CommCell is created by deploying the core Commvault components. At minimum, the Global CommCell uses CommServe, Web Server, and Command Center for registration, switching, aggregation, monitoring, and direct entity operations.

To use Active Management and blueprints, also install and configure the Global Configuration Manager and Hub Service. The Global Command Center functions as the access portal for this environment.

Commvault Components

The following components can be deployed as part of the Global CommCell:

• CommServe

For information about installing the CommServe Server, see Server Installations.

• Web Server

To use Active Management and blueprints, install the following packages with the Web Server:

• Global Configuration Manager

• Hub Service

For information about installing the Web Server, see Installing the Web Server.

• Command Center

For information about installing the Command Center, see Installing the Command Center.

For supported deployment models and failover requirements, see Deployment Models and Failover Requirements.

Communication Flow

The Global Command Center supports two main types of functionality:

• Aggregation and switching: The Global Web Server connects to the Command Center URL of each Service CommCell. Use this flow to view dashboards, jobs, alerts, reports, and Service CommCell entities from the Global Command Center.

• Active Management and blueprints: Service CommCell Web Servers connect outbound to the Global Hub Service. Use this flow to create configuration in the Global Command Center and synchronize it to Service CommCells. The Global Web Server, Global Configuration Manager, and Hub Service must also be able to communicate with each other.

Set Up a Global Web Server

Configure the required Commvault packages on the Web Server that you want to configure as the Global Command Center.

The following sections are required for Active Management and blueprints.

Enable Global Configuration Manager

You must enable the Global Configuration Manager to allow the Global Command Center to create blueprints and synchronize entities across Service CommCells.

1. Add the bIsGlobalCommcell setting and configure its value to true.

1. Restart Commvault services on the Web Server and the CommServe to verify that the Global Configuration Manager is enabled.

Configure Global Configuration Manager Application

1. To set the Global Configuration Manager URL on all Web Servers in your Global CommCell environment, add the globalConfigManagerBaseUrl setting and configure its value as http://<GCMHostName>:5005/.

Include the port and trailing slash.

1. Verify the Global Configuration Manager health URL from the Global Configuration Manager server:

http://localhost:5005/globalconfig/health

1. If other Web Servers cannot access port 5005 of the Global Configuration Manager server, configure the required network routing. For supported deployment models and failover requirements, see Deployment Models and Failover Requirements.

Configure the Hub Service Application

1. To set the Hub Service URL on all Web Servers, add the hubServiceBaseUrl setting and configure its value as http://<HubServiceHostName>:5010/.

Include the port and trailing slash.

If Service CommCell Web Servers connect through a reverse proxy, configure hubServiceBaseUrl with the proxy URL instead of the direct Hub Service URL. The URL configured in hubServiceBaseUrl is sent to Service CommCells and is used for Active Management synchronization.

1. Verify the Hub Service health URL from the Hub Service server:

http://localhost:5010/hub/health

1. From each Service CommCell Web Server, verify that the Hub Service URL is reachable:

http://<HubServiceHostName>:5010/hub/health

Configure HTTPS for the Hub Service

If your environment requires HTTPS for the Hub Service, configure an HTTPS certificate for the Hub Service.

1. On the Hub Service server, go to the WebServerCore folder.

For example:

E:\Program Files\Commvault\ContentStore\WebServerCore

1. Run the following command:

dotnet CVDotNetContainer.dll https-cert configure --instance Instance001 --hostname "<HubServiceFQDN>" --certPath "<PFXCertificatePath>"

Replace <HubServiceFQDN> with the Hub Service host name and <PFXCertificatePath> with the path to the PFX certificate file.

1. When prompted, enter the certificate password.

The command stores the certificate and writes the following registry values:

• CVContainer\DotNet\httpsHostName

• CVContainer\DotNet\certPath

• CVContainer\DotNet\certPassword

• Verify the HTTPS port in the registry:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\CVContainer\DotNet

The HTTPS port is commonly 5006.

1. Update the hubServiceBaseUrl setting to use the HTTPS endpoint.

For example:

https://<HubServiceFQDN>:5006/

1. Verify the HTTPS Hub Service health URL from each Service CommCell Web Server:

https://<HubServiceFQDN>:5006/hub/health

Use a Reverse Proxy for the Hub Service

If Service CommCell Web Servers cannot connect directly to the Hub Service port, you can use a reverse proxy that is reachable from the Service CommCells and forwards requests to the Hub Service.

Configure hubServiceBaseUrl with the reverse proxy URL, and then validate the proxy URL from each Service CommCell Web Server. If hubServiceBaseUrl points to a direct Hub Service URL that Service CommCell Web Servers cannot reach, Active Management synchronization will not work.

Restart the Services

After you configure or change the Global Configuration Manager or Hub Service URLs:

1. On the CommServe and Web Servers, restart the Commvault services.

2. Perform an IIS reset.

3. Retry Active Management for the Service CommCell so that the updated Hub Service URL is sent to the Service CommCell.

You can also edit Service CommCell URLs from the Service CommCell details page after registration. After URL changes that affect Active Management, restart services, run IISRESET, and retry Active Management.

Verifying Health

After installation, verify that the Hub Service and Global Configuration Manager server are operating correctly.

Verify Hub Service Health

To confirm that the Hub Service is running, access one of the following URLs:

• http://localhost:5010/hub/health

• https://<HubServiceFQDN>:<https-port>/hub/health

• https://<HubServiceProxyFQDN>:<proxy-port>/hub/health

If additional troubleshooting is required, review the HubService.log file on the Global CommCell and the WebServer.log file on the Service CommCell Web Server. Connection errors in the Service CommCell WebServer.log often indicate an incorrect Hub Service URL, missing port, missing trailing slash, firewall block, or certificate issue.

Verify Global Configuration Manager Health

To check the health status of the Global Configuration Manager server, access the following URL:

http://localhost:5005/globalconfig/health

After completing all the steps and successfully verifying the health, the Global Command Center is ready to manage and synchronize entities across the registered Service CommCells.