Cisco Cisco Process Orchestrator 3.0 User Guide
5-13
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 5 Managing High Availability and Resiliency
Performing Disaster Recovery
Performing Disaster Recovery
This section discusses the following topics:
•
•
•
Recovering from a Server Failure
In a multi-server high availability environment, there is very little you need to do to recover from a single
server failure. When a Process Orchestrator server fails (due to, for example, a network outage, disk
failure, or software failure), the remaining Process Orchestrator servers within the environment will:
server failure. When a Process Orchestrator server fails (due to, for example, a network outage, disk
failure, or software failure), the remaining Process Orchestrator servers within the environment will:
1.
Recognize the failure (within a few seconds).
2.
Report the failure in event logs.
3.
Redistribute the work that was performed by the failed Process Orchestrator server among the
remaining healthy servers.
remaining healthy servers.
If the server failure is recoverable, simply bringing the server or service back up will put it back into the
high availability environment and operations will resume.
high availability environment and operations will resume.
If the server failure is not recoverable (for example, a hardware failure), you can add a new Process
Orchestrator server to the environment. There is very little need to recover the failed server; it will not
be considered healthy, and no work will be assigned to it. To delete the old server from the environment,
choose Administration > Orchestration Servers > Remove.
Orchestrator server to the environment. There is very little need to recover the failed server; it will not
be considered healthy, and no work will be assigned to it. To delete the old server from the environment,
choose Administration > Orchestration Servers > Remove.
Recovering from a Reporting Database Failure
If only your Reporting database has failed, there are several options:
•
If possible, recover the database server. Operations will resume as before, and no changes are
needed.
needed.
•
If the database server is not recoverable but the database is (because there is a backup), restore the
database to a new database server (see
database to a new database server (see
•
If both the database server and the database are not recoverable, recreate the database on a new
database server (see
database server (see
Restoring the Database to a New Database Server
To restore the database to a new database server:
Step 1
Open a console connecting to any Process Orchestrator server in the environment.
Step 2
Remove the existing Reporting Database connection and connect to the new database server (see
The changes will propagate throughout the entire high availability environment.