Scom 2012 knowledge sharing-4: Understanding Deployment Scenarios

Platform: System Center 2012 RTM/SP1

(1) Single Server deployment

The Single Server Management Group solution combines all management group roles that can coexist on a single instance of Windows Server 2008 R2 SP1 or Windows Server 2012 Operating System (running as a member server in the Active Directory domain. This instance can be on a dedicated hardware or virtual computer. You can deploy the operation console on a computer other than a single server and access the Web Console through a browser. Then, the agent is usually deployed to a limited number of devices based on the capacity of the server where the system center 2012-Operations Manager is deployed.

Use Cases

To use Operations Manager for evaluation, testing, and management package development (typically in a non-production or pre-production environment), you can deploy it in a single server management group.The configuration of a single server management group usually lacks stability and performance and can only support minimal production load.

A single server deployment can meet the functional requirements.

650) This. width = 650; "Title =" Clipboard "style =" border-top: 0px; border-Right: 0px; Background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; padding-Right: 0px; "Border =" 0 "alt =" Clipboard "src =" http://img1.51cto.com/attachment/201407/18/639838_1405691281wrSi.png "Height =" 420 "/>

However, there are also a lot of single-server deploymentRestrictions:

1. The configuration of a Single Server Management Group is the easiest to deploy, but its performance is limited. Therefore, common objects are also limited.

2. This configuration does not include the gateway server role. Therefore, all monitored devices must be in the same Active Directory forest as the management server, or you must use certificates on both managed computers and Management servers to provide mutual authentication.

3. A single server and a single management group are located on a group of hardware. This configuration only supports one instance for each server role, so it cannot support managing proxy failover between servers.

How to deploy scom 2012: http://technet.microsoft.com/zh-cn/library/hh457006.aspx on a single server

Bytes ------------------------------------------------------------------------------------------------------------------

(2) distributed Deployment Scenarios

It allows the allocation of functions and services between multiple servers to allow scalability. It can include all Operations Manager server roles and supports monitoring devices across trust boundaries by using gateway servers.

To manage the scalability and high availability of servers and gateway servers, you can deploy System Center 2012-operations manager or system center 2012 Service Pack 1 (SP1) in the Distributed Management Group) -Operations Manager. By default, all management servers are members of all management server resource pools. This balances the monitoring load of the Management Group when adding new management servers and provides automatic failover for monitoring.

Distributed Management GroupDistribute operations manager among multiple servers.For example, you can install and operate databases on one server, install the Web Console on another server, and install the report server on a separate server. This is different from installing a single server management group. All functions in this solution are installed on one server.

You can install a Web Console on an independent server or an existing management server, but you cannot install the management server function on a server with an existing Web console. If you want to install the Management Server and Web Console on the same server, you must install these two functions at the same time or install the management server before installing the Web console.

Distributed Deployment scenario.

In: database servers, gtw servers, and management servers all achieve load balancing or high availability.

650) This. width = 650; "Title =" Clipboard [1] "style =" border-top: 0px; border-Right: 0px; Background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; padding-Right: 0px; "Border =" 0 "alt =" Clipboard [1] "src =" http://img1.51cto.com/attachment/201407/18/639838_1405691290VAgJ.png "Height =" 594 "/>

The operation Console does not directly communicate with the database. All communications are forwarded to the resource pool through TCP 5724, and then transferred to the database server using ole db on TCP 1433 or custom port specified by the customer. However, the application diagnostics Console (together with the Web Console) communicates directly with the database.

Distributed Management Groups are usually used to monitor large pre-production environments and large production environments., These environments

1. Cross the trust boundary between the domain and the workgroup.

2. It has multiple network environments separated by firewalls.

3. High Availability is required.

4. A Scalable monitoring solution is required.

Bytes ------------------------------------------------------------------------------------------------------------------

Best practices

1. High Availability must be taken into account for medium-and large-scale deployment, including: High Availability of MS, high availability of SQL, and automatic enabling of Agent failover if more than three Ms servers are used, and scom roles should be separated whenever possible.

2. Best practices: 1. MS and SQL are in the same physical network. Try not to boast about the router. 2. Use the gataway server if you boast of the WAN. 3. SQL is used as a cluster. 4. Data Warehouse supports multiple management groups. 5. resource pools are used for specific functions (Linux, UNIX, and network devices ).

3. Virtualization best practices: 1. Management Servers can be virtualized. After virtualization, Ms must meet the minimum requirements. 2. Database virtualization is not recommended, but it can be virtualized to ensure disk I/O.

Bytes ------------------------------------------------------------------------------------------------------------------

This article is from the blog "Zeng luxin's technical column" and will not be reposted!

Scom 2012 knowledge sharing-4: Understanding Deployment Scenarios