CommServe Log Shipping Workflow

CommServe Log Shipping is predefined workflow that will back up and restore the CommServe databases and transaction logs from the production CommServe host to a standby CommServe host at regular intervals automatically.

The workflow can be used as a alternative to creating database and log backup and restore schedules for basic failover configuration. 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. Initiate a full backup job for the databases defined in the subclient content of the production CommServe host.
  2. If the backup job completes successfully, run a restore job to restore the databases to the standby CommServe host.

    If the backup job did not complete, re-run a full backup job of the databases.

  3. If the restore job completes successfully,  wait till the specified cycle delay time and then initiate a transaction log backup for the production CommServe databases.

    If the restore job did not complete successfully, initiate a full backup job once again.

  4. After the log backup is complete, restore the backed up transaction logs to the standby CommServe host.
  5. After the log restore job is complete, checks is the restore job was successful.
  6. If the restore was successful, checks when the last full database backup job was run.
    • If the number of days is equal or greater than the number of days defined in the workflow, initiates a new full database backup.
    • If the number of days is lesser than the defined value, initiate a new transaction log backup.

Prerequisites

Prior to executing the workflow, ensure the following:

  • Install and configure the SQL server agent and CommServe failover component with basic failover configuration on the second instance of the production and standby CommServe hosts. For instructions on implementing basic failover configuration, see Basic Configuration.

    As an alternative, you can run the CommServe Failover Configuration workflow to build the CommServe hosts with basic failover configuration.

Running the Workflow

  1. From the CommCell Browser, go to Workflows.
  2. Right-click LogShipping 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 ClientNameOfSQLidaOnProdCS box, type the client name of the second instance on the production CommServe host.
    • In the BackupSetOfSQLidaOnProdCS box, type defaultBackupSet.
    • In the InstanceNameOfSQLidaOnProdCS box, type the instance name of the SQL agent on the production CommServe host. For example, Prodcs\NetApp.
    • In the SubclientNameOfSQLidaOnProdCS box, type the name of the SQL subclient configured to back up the production CommServe databases.
    • In the ClientNameOfSQLidaOnDRCS box, type the client name of the second instance on the standby CommServe host.
    • In the InstanceNameOfSQLidaOnDRCS box, type the instance name of the SQL agent on the standby CommServe host.  For example, DRcs\NetApp.
    • In the UndoLocationPathOnDRMachine  box, type the path to the db_undo folder on the standby CommServe host.
    • In the BackupSetOfSQLidaOnDRCS box, type defaultBackupSet.
    • In the NextFullBackupInDays box, type the minimum number of days allowed between subsequent full database backups. If the number of days since the last full database backup job is equal or greater than the defined value, a new full database backup job is initiated.
    • In the CycleDurationInMinutes box, type the time interval (in minutes) between subsequent log backup and restore cycle. After a log restore job, the workflow waits for the specified time interval before starting a new log backup job.
  4. Click OK.

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

    The workflow runs the backup and restore cycles continuously based on the inputs defined in the workflow.