Cisco Cisco Process Orchestrator 3.0 User Guide

Ensuring both operational continuity and disaster recovery preparedness requires:

Creating a support team (see 

Planning for high availability by installing multiple Process Orchestrators on virtual machines (see 

Using one of the recommended databases (see 

Considering the dependencies Process Orchestrator has on other services (see 

Develop a strategy for performing regular database and system backups.

 

To maintain operational continuity and ensure that the people on your site are prepared for any 
emergency:

Create your Cisco Process Orchestrator Support team well in advance of any disaster. 

When a disaster occurs, the first step of any recovery process should be to contact this team. The 
members of this team should know the prescribed (and latest) list of procedures, and each member 
should have a pre-defined role in the recovery process.

This team should consist of:

The team assigned to day-to-day administration and operations. 

Although Process Orchestrator can be useful across a broad span of IT users, it needs an 
administrator/operator. This person will use the Operations Workspace (see 

) to monitor the health of processes and receive operational alerts, and 

will typically serve as the primary contact for customer support issues.

The database administrator (DBA) responsible for the database if the disaster is related to the 
Process Orchestrator database.

The manager of the VM farm on which the Process Orchestrator servers run.

Personnel who can run the software that restores the Process Orchestrator server. This can be the 
VM farm operator.

Because outages in individual upstream systems can affect processes that span technologies and 
services, maintain the contact information for the owners of any upstream systems (see 

). This information should include current names and phone 

numbers.