CommServe Failover Configuration Workflow

The CommServe Failover Configuration workflow is a predefined workflow for configuring basic failover on the production and standby CommServe hosts for disaster recovery purposes.

For more information on using basic configuration for disaster recovery failover, see Basic Configuration.

Download this workflow from the Software Store. See Download Workflows from Software Store.

This workflow can be manually executed from the CommCell Console.

How It Works

This predefined workflow automates these operations:

  1. Checks the following prerequisites:
    • MediaAgent must be on a separate host
    • Host name for instance 1 and instance 2  on the CommServe hosts must not be the same
    • Test and critical client group names do not exist already.
    • Specified storage policy name does not exist already.
    • The library must be configured on the MediaAgent.
  2. Installs the SQL Agent and CommServe Failover components on the production and standby CommServe hosts.
  3. Creates a non-deduplicated storage policy on the production CommServe host.
  4. Creates subclients for the second instance of production and standby CommServe hosts.
  5. Creates test and critical client groups and adds the clients to the client groups.
  6. Configures the CommServe Failover component using basic failover configuration based on the inputs provided.

Prerequisites

Prior to executing the workflow, ensure the following:

  • Make sure the CommServe software installed on the production and standby hosts meet the requirements for disaster recovery failover. Review the CommServe Installation: Considerations for Disaster Recovery Failover.
  • Create a network shared folder on the standby CommServe and make sure it is accessible by the production CommServe host.
  • The library must be configured on the MediaAgent.
  • 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.

Running the Workflow

  1. From the CommCell Browser, go to Workflows.
  2. Right-click CVFailoverConfigurationWorkflow and then click All Tasks > Execute.
  3. From the Run workflow on list, select the workflow engine and enter values for the following variables:
    • In the ProdCsHostname box, type the host name for the production CommServe host.
    • In the DRCsHostname box, type the host name for the standby CommServe host.
    • In the CSClientName box, type the common client name used by production and standby CommServe hosts .
    • In the MediaAgentforSPCreation box, select a MediaAgent. Make sure the MediaAgent is on a separate host at the standby CommServe location.
    • In the LibraryName box, type the library configured on the MediaAgent.
    • In the StoragePolicyName box, type a name for the storage policy that will be created by the workflow.
    • In the ClientGroupNameForTestDR box, type a name for the test client computer group that will be created by the workflow.
    • In the ClientsForTestDR box, select one or more clients to be added to the test client computer group.
    • In the ClientGroupNameForCriticalDR box, type a name for the critical client computer group that will be created by the workflow.
    • In the ClientsForCriticalDR box, select one or more clients to be added to the critical client computer group.
    • In the Security-JobUserName box, type the CommCell user name with permissions to run jobs. For example, administrator.
    • In the Security-JobPwd box, type the password for the CommCell user.
    • In the DomainUserName box, type the Windows user account under which the cvfailover service will run.
    • In the DomainUserPwd box, type the password for the Windows user account.
    • In the emailId box, type the email addresses of users who will receive alerts on workflow progress.
    • In the SharedLocationonDRCSforInstallxmlcpy box, type the network path to the shared folder on the standby CommServe host. For example, \\drcs\failovershared.
    • In the LocalPathofSharedLocation box, type the local path to the shared folder on the standby CommServe host. For example, c:\failovershared.
    • In the SetupLocationonProdCS box, type the complete path to the installer package on the production CommServe host. For example, C:\DISC1\Winx64\setup.exe .
    • In the HostnameforInstance2-onProdCS box, type a host name for the instance 2 on the production CommServe host. Make sure the host name is different from the production CommServe host name.
    • In the ClientNameForInstance2-onProdCS box, type a client name for the instance 2 on the production CommServe host. Make sure the client name is different from the production CommServe client name.
    • In the SQLSubclientName-ProdCS box, type a name for the SQL subclient that will be created by the workflow on the second instance of the production CommServe host.
    • In the SetupLocationonDRCS box, type the complete path to the installer package on the standby CommServe host. For example, C:\DISC1\Winx64\setup.exe .
    • In the HostnameforInstance2-onDRCS box, type a host name for the instance 2 on the standby CommServe host. Make sure the host name is different from the standby CommServe host name.
    • In the ClientNameForInstance2-onDRCS box, type a client name for the instance 2 on the standby CommServe host. Make sure the client name is different from the standby CommServe client name.
    • In the DatabasestoBackup box, select the SQL databases that will be backed up by the SQL subclient.
    • In the SQLSubclientName-DRCS box, type a name for the SQL subclient that will be created by the workflow on the second instance of the standby CommServe host.
    • In the drivePool-Optional box, type the drive pool  to be used by the MediaAgent.
    • In the Scratchpool-Optional box, type the scratch pool to be used by the MediaAgent.
    • In the InstalldirforInstance2-onProdCS box, type the installation path for installing the second instance on the production CommServe host. Optional.
    • In the Cvdport.for.client.onProdCs box, type the Cvd port number to be used for installing the second instance on the production CommServe host. Optional.
    • In the Evmgrs.port.forclient.onProdCS box, type the Evmgrs.port number to be used for installing the second instance on the production CommServe host. Optional.
    • In the InstalldirforInstance2-onDRCS box, type the installation path for installing the second instance on the standby CommServe host. Optional.
    • In the Cvdport.for.client.onDRCs box, type the Cvd port number to be used for installing the second instance on the standby CommServe host. Optional.
    • In the Evmgrs.port.forclient.onProdCS box, type the Evmgrs.port number to be used for installing the second instance on the standby CommServe host. Optional.
  4. Click OK.

    You can track the progress of the workflow job from the Job Controller.

Post Workflow Operations

The CommServe failover configuration workflow installs and configures the SQL agent and CommServe failover component on the production and standby CommServe hosts.

After running the workflow, you must synchronize the databases and logs on both the CommServe hosts. To synchronize the databases and logs, run the CommServe Log Shipping Workflow or follow Step 7 and Step 8 on the Basic Configuration page.