Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Orchestrator, System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator
The following guidelines provide options in an Orchestrator deployment to improve high availability and performance.
An Orchestrator deployment is limited to one management server. A management server does not have to be available for runbook servers or runbooks to function. If the management server is not available, you cannot connect the Runbook Designer to publish runbooks or start, monitor, or stop runbooks. You can still start, monitor, and stop runbooks with the Orchestration console.
For high availability, you can deploy the Orchestrator database on a Microsoft SQL Server cluster with a minimum of two nodes.
The Orchestrator web service must be installed on a server that is running Internet Information Services (IIS). The Orchestrator web service does not have to be available for runbook servers or runbooks to function. If the Orchestrator web service is not available, you cannot run the Orchestration console to start, monitor, or stop runbooks. You can install the web service on multiple IIS servers configured for load balancing to provide high availability and additional capacity.
For high availability, you should have at least two runbook servers. If the primary runbook server for a runbook is unavailable, the runbook can run on another server. runbook servers are not designed to run on a computer configured as a cluster node.
For more information about specifying the runbook servers for a runbook, see the Using Runbooks in System Center 2012 - Orchestrator.
By default, runbook servers can run 50 runbooks simultaneously. The physical computer resources and the complexity of the runbook limit the actual number of runbooks that a runbook server can manage.
For the process to modify the number of runbooks that can run simultaneously, see How to Configure Runbook Throttling.