Cisco Cisco Process Orchestrator 3.0 User Guide

This topic documents the basic approach used to support operational continuity, the ability to maintain 
availability during routine maintenance, and disaster recovery requirements for a Cisco Process 
Orchestrator. Using the production-level planning and operations described in the following topics, 
implementing these features should result in as much as 99.95% up time for your site:

The Cisco Process Orchestrator active-active server provides a highly available and scalable solution, 
the goal of which is to virtually eliminate down time due to hardware application failures. This solution, 
which protects critical pieces of the system from failure and excessive loads, includes these features:

Rather than a single server performing all of the work (running processes, monitoring triggers, and 
so on), a Process Orchestrator environment can contain many servers. If one server fails, as long as 
another is available to take its place, useful work can continue. 

In a Process Orchestrator environment, all servers connected to the system share the workload, 
which helps increase scalability and performance. The more servers that are available in the system, 
the less work each of them must perform. 

A Process Orchestrator environment is available during routine maintenance, such as rebooting the 
operating system, applying OS security patches, and performing minor upgrades (even to the 
Process Orchestrator itself).