If a disaster occurs in the primary data center, you can
continue to provide business support if you have a valid backup. You
restore the backup to the secondary data center and then verify the
restored data.
About this task
Restoration is the process of rebuilding all or part of
a backup to the corresponding secondary environment, as shown in this
diagram. In this case, Backup N-2 was not successful. Backup N-3 was
immediately run to replace it. Figure 1. Restoration process
Important: To ensure the consistency of all
data, the restoration must occur for the whole cell and underlying
database.
Procedure
To restore the production environment to the secondary
environment, complete the following steps:
Reinstall the installation data, including the IBM® Business Automation
Workflow installation
data.
Reinstall Db2® and create the Db2 instance.
Restore the configuration data to all servers from the
backup configuration data.
Restore the runtime data to all servers by replicating
the backup runtime data.
Perform changes that are specific to the environment.
For example, update the host name to reflect the secondary
environment, or change the data source configuration to point to the
secondary database.
Validate the connectivity to the resources outside the
recovery scope.
To restart the environment, follow these steps:
Start the database server.
Start the deployment manager and node agents.
Start the message servers of IBM Business Automation
Workflow.
Start the support servers of IBM Business Automation
Workflow.
Start the application servers of IBM Business Automation
Workflow.
Verify the restored environment and determine whether it
is valid.
Recover inflight transactions.
Redirect load to the new environment.
Tip: You can typically set the same host name and IP address
for the secondary environment as for the primary environment. This
step depends on your backup policy.