Configuring the CommServe Failover Component Using Advanced Configuration
You must configure the CommServe Failover component on the production and standby CommServe hosts and the individual witness server hosts.
Before You Begin
- Login to the host computer as member of the Administrators group.
- Install the CommServe Failover component on the production and standby CommServe hosts and on separate Windows hosts acting as Witness Servers at the standby CommServe location.
- Record the CommCell Username and Password to perform SQL agent backup and restore jobs.
- If User Account Control (UAC) is enabled on the computer, you must manually assign full access permissions to the install_directory/CVFailover folder for the Windows user account used for running Cvfailover services.
About This Task
When configuring the failover component on witness server hosts, to speed up the process, perform the steps on one witness server host and then copy the C:\Program Files\<Install folder>\CVFailover\conf folder to the same location on the other Witness Server hosts. When you run cvfailover_config.cmd command on the other two Witness Server hosts, the information provided during the first installation will be automatically populated.
- At the command line on CommServe hosts, go to installation_directory_of_second_instance/cvfailover and enter the following command:
For witness server hosts, go to installation_directory/cvfailover and enter the command.
- Provide the following input parameters during the cvfailover configuration.
Inputs marked with * (asterisk) will appear only when running the script on CommServe hosts.
Input parameters Values Configuration Type 2 Which role this machine should be assigned to: Enter 1 for Client only role (applicable for CommServe hosts)
Enter 2 for Server only role (applicable for Witness Server hosts)
Enter 3 for both Server and Client roles (applicable for CommServe hosts)
Credentials for Application Start Windows user account under which the cvfailover service will run. Witness service port 1, Witness service port 2 These are the open port numbers that are used to communicate to the servers. Accept the default values or provide other open port numbers and then press Enter. All configured hosts must use the same ports. Five Witness Server names or addresses Provide the fully qualified domain name of the witness server hosts.
Server1 – Server3 are the Witness Servers hosts.
If only three witness Servers exist, then Server4 and Server5 entries will be left blank.
*Listening port for clients: These are the open port numbers that are used to communicate to the clients. Accept the default values or provide other open port numbers and then press Enter. All configured hosts must use the same ports. *Instance name of CS Instance name on which the CommServe is installed. For example, Instance001. *Id of the CommServ (1 - first, 2 - second): Type 1 if configuring on production CommServe host
Type 2 if configuring on standby CommServe host
*DNS name for floating CS (host name only): Specify the host name of the floating CommServe name. *Domain name for floating CS (domain name only): Specify the domain name of the floating CommServe name. *Fully qualified name of DNS controller: Specify the fully qualified name of the DNS controller. For example, dns.company.com> *Parameters of the first CommServ
Physical IP of the first CommServ: <IP_address_of_production_CS>
Client name of Instance002 of the first CommServ: <production_CS_second_instance_client_name>
Sub-client name of Instance002 of the first CommServ: <production_CS_subclient_name>
DB Instance (connect parameter) of first CommServ:<production_CS_database_instance_name>
Physical IP of the first CommServ:18.104.22.168
Client name of Instance002 of the first CommServ: prodcs_instance2
Sub-client name of Instance002 of the first CommServ: prodcs_sql
DB Instance (connect parameter) of first CommServ: prodcs\COMMVAULT
*Parameters of the second CommServ
Physical IP of the second CommServe: <IP_address_of_standby_CS>
Client Name of Instance002 of the second CommServ:<standby_CS_second_instance_client_name>
Sub-client name of Instance002 of the second CommServ: <standby_CS_subclient_name>
DB Instance (connect parameter) of second CommServ: <standby_CS_database_instance_name> For example:
Physical IP of the second CommServ:22.214.171.124
Client name of Instance002 of the second CommServ: failovercs_instance2
Sub-client name of Instance002 of the second CommServ: failovercs_sql
DB Instance (connect parameter) of second CommServ: failovercs\COMMVAULT
*Credentials for starting jobs Specify the username and password noted in the Recording the Username And Password section. *Staging folder for DB restored Specify the staging location where the SQL database will be restored.
Staging folder for DB restored: C:\db_undo
*E-mail alert parameters: Specify the SMTP server name and email address of sender and recipient users (administrators) who will receive critical email alerts in the event of a disaster. On receiving the critical email alert, the administrator will configure the failover.
When a disaster occurs, the initial email alert is sent after 20 minutes by default. Later on, repeated email notifications are sent every 10 minutes.
You can modify the time interval (in minutes) for sending repeated email notifications to the administrators.
Enable debug alerts (0-disables, 1 - enabled)0]: 0
Host name of SMTP server: smtp.mail.com
From address for alerts: <server_user_id>
TO address for alerts: <server_admin_id>
CC address for alerts[none]:
Period or repeating the critical e-mail notifications (0-disable e-mails):
Verify input(yes/no) Type yes to verify the input parameter values before saving the configuration file. By default, the input parameters are not verified.
Once you configure CommServe failover on the CommServe hosts, you will notice that javaw.exe process running in the task manager.
If the CommServe host is also configured with witness server role, you will notice two javaw.exe processes running in the task manager.
Note: Completing this step will 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.