Load-Balancing Service Manager Management Servers
Updated: November 1, 2013
Applies To: System Center 2012 - Service Manager, System Center 2012 R2 Service Manager, System Center 2012 SP1 - Service Manager
You can use network Load Balancing (NLB) in Windows Server 2008 to configure a pool of computers so that they take turns responding to requests. In System Center 2012 – Service Manager, the initial Service Manager management server that you deploy is the server that processes workflows. You can deploy additional management servers to provide failover for a failed initial management server and to provide load balancing for handling Service Manager console. For more information about Windows Server 2008 NLB, see the Network Load Balancing Deployment Guide. For more information about additional Service Manager management servers, see Deploying Additional Service Manager Management Servers.
As a minimum, you have to deploy an initial Service Manager management server—the management server that hosts the workflow processes—and at least one additional Service Manager management server. In an environment of this kind that consists of two Service Manager management servers, configure NLB to use both management servers, as shown in the following illustration.
If you deploy two or more additional Service Manager management servers, you can isolate the initial Service Manager management server from the NLB pool. This reduces the workload on the initial Service Manager management server, resulting in better workflow performance. It also load-balances all of the Service Manager consoles across the remaining Service Manager management servers. This scenario is shown in the following illustration.
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.