Name Management Troubleshooting

Updated

Cannot Open Web Console or Command Center After Updating the Web Server Hostname

Symptom

You cannot open Web Console or Command Center after renaming the computer hosting the Web Server. This can occur if the Web Server is installed on a remote computer (not the CommServe computer).

Resolution
  • On the Web Server computer, update the hostname in the following registry keys, and then restart the Tomcat services:

    • HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\instance_name\WebConsole\baseUrl

    • HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\instance_name\CustomReportsEngine\webServerUrl

    For example: Change the host name in the URL: http://new_host_name:81/SearchSvc/CVWebService.svc/.

  • If you use Private Metrics Reporting, you must change the upload URL for the Private Metrics Reporting Server in the Control Panel of each CommServe computer that uploads data. Otherwise, the reports will try to open on the Cloud Services Website. For instructions, see Activating Private Metrics Reports in a v10 or v11 CommCell Console.

Name Change Fails to Inform Clients of a CommServe Name Change

If the name change operation fails to inform clients of the new CommServe name, then perform the following steps.

  1. Restart the services on the CommServe computer.

  2. Restart the services on the Client/MediaAgent computers where the error occurred.

Name Change Fails During a Failover in a Clustered Environment

Symptom

After a failover to a new node, the CommServe hostname is not automatically updated. This happens when the CommServe hostname of the active node in a clustered environment is changed before the failover occurs.

Resolution

Perform the name change operation on the new node. See Changing the CommServe Computer Name for instructions.