V11 SP8

Configure CommServe Failover (Without DNS)

You can configure CommServe failover on the production or standby CommServe host without using a Domain Naming System (DNS) to resolve the CommServe host names.

When you configure the failover, the settings are automatically populated on the other CommServe host.


  1. Start Failover Configuration.
  2. In the Physical Hostname boxes, type the physical computer host name of Node1 (production) and Node 2 (standby) CommServe host.
  3. In the SQL Agent Client Name, type the client name of the second instance on Node1 (production) and Node 2 (standby) CommServe host.
  4. In the Storage Policy box, select the storage policy to be used for the SQL database and log backups and restores.
  5. Clear the Use DNS Server for Failover check box.

    If the option is not selected, you need to manually change the CommServe name on the clients. Alternatively, you can configure a proxy and allow the CommServe and clients to communicate through the proxy. For instructions, see Using Commvault Proxy for Disaster Recovery.

    If you want to change the CommServe name on all the client computers, select the Allow client name change operations check box. This option is not recommended for environments with 100+ clients as the name change operation could be very slow. Also, all the remote clients must be reachable at the time of the failover.

  6. Click Next.
  7. Optional: If you want email notifications on the failover status or monitoring issues, select the Enable Email Alerts check box.
    1. In the SMTP Server Hostname, enter the host name or IP address of the SMTP server. For example, mail.company.com.
    2. Enter the From, To, and CC email IDs.
    3. Click Next.
  8. In the Summary screen, click Advanced.
  9. On the Node Info tab, in the Subclient boxes, enter a name for the subclient that the failover component will create on Node1 (production) and Node 2 (standby) CommServe hosts.

    Note: If a Subclient has to be recreated, open the CommCell Console and delete the subclient first.

  10. Click the Additional Details tab, and enter the following details:
    1. In the CS Instance for Failover box, specify the instance in which the Node 2 (standby) CommServe host is installed.
    2. In the Time Interval for Sync Operation box, enter the time interval in minutes for synchronizing the databases on both the nodes.
    3. Optional: If you want to disable the sync operation, In the Enable Synchronization of Nodes box, select No.
    4. In the Time Interval for Full Backups box, enter the time interval (in days) for running a full backup and restore of  the CommServe database to the passive node.
    5. In the Test Failover Group Name box, select the client computer group that was created for test failover operations.
    6. Optional: If you want to run customized scripts before or after the failover operation, click Browse corresponding to the appropriate pre or post script and then select the path to the custom script.
  11. Click Save.
  12. In the summary screen, click Finish.


As soon as you complete the failover configuration, the software initiates the following actions:

  • Creates the SQL subclient and triggers the initial sync up of the CommServe databases. You can view the status of the backup and restore operation for the SQL subclient from the Job Controller. Subsequent transaction log backup and restores operations are scheduled based on the sync time interval defined during the configuration.
  • The java.exe process starts running in the task manager. If the CommServe host is also configured with witness server role, you will notice two java.exe processes running in the task manager.
  • If the Enable Email Alerts option was selected, an alert will be generated and sent to the specified email address, to indicate the successful completion of the configuration wizard.

What To Do Next

  • Disable the Restartable option for the SQL DB (Data Recovery) Job Type. (You can set this option in the Job Management > Job Restarts dialog from Control Panel.) Disabling it is intentional, because restarting that type of job can result in very lengthy delays due to retries and timeouts. Please do no re-enable the Restartable option for SQL DB (Data Recovery) jobs on systems configured for failover.
  • Open CommCell Console and verify that the SQL backup and restore jobs complete successfully.
  •  Perform a Test Failover to verify the readiness of the standby CommServe host.

    For instructions, see Testing CommServe Failover to the Standby Host.

Related Topic

Failover Monitor - Quick Reference