Loading...

Restoring Workflow Transaction Logs to a Standby Host

After you set up a high availability environment for your Workflow Engine, you have the option to move your Workflow operations to your standby host. Moving your Workflow operations to your standby host can be planned or can be due to an unplanned event.

Before You Begin

Set up a high availability environment for the Workflow Engine. For instructions, see Setting Up Disaster Recovery Failover to a Warm Standby Workflow Engine Environment.

Procedure

Scenario: Unplanned Move (Failure of the Production Host)

  • On the standby host, do the following to recover workflow operations if the production host fails:
    1. Disable the daily restore schedule.

      For instructions, see Enabling or Disabling a Schedule.

    2. Start the Workflow service.

      For information about the Workflow service, see Available Services.

    3. Resume the Workflow jobs.

      These are the jobs that were running on the production host when the failure occurred and are now available on the standby host.

      For instructions, see Resuming a Job in the Job Controller.

Scenario: Planned Move

  1. On the production host, do the following to move workflow operations from the production host to the standby host:
    1. Stop the Workflow service.

      For information about the Workflow service, see Available Services.

    2. For the Workflow Engine (WFEngine) database transaction logs, run a backup.

      For instructions, see Backing Up SQL Transaction Logs.

  2. On the standby host, do the following to move workflow operations from the production host to the standby host:
    1. For the Workflow Engine (WFEngine) database transaction logs, run a restore.

      Important: On the Options tab, select the Latest Backup Data check box and the Apply Log Backups Only check box.

      For instructions, see Restoring SQL Transaction Logs to a Hot Standby Server.

    2. Disable the daily restore schedule.

      For instructions, see Enabling or Disabling a Schedule.

    3. Start the Workflow service.

      For information about the Workflow service, see Available Services.

    4. Resume the Workflow jobs.

      These are the jobs that were running on the production host when the services were stopped and are now available on the standby host.

      For instructions, see Resuming a Job in the Job Controller.

What to Do Next

On your standby host:

  • If you scheduled and disabled a backup for the Workflow Engine (WFEngine) database transaction logs, enable the schedule so that the transaction logs are backed up now that you moved to the standby host.
  • If you did not schedule the transaction log backup in advance, schedule it now. For instructions, see Backing Up SQL Transaction Logs.

Last modified: 10/13/2017 9:36:29 AM