System Center R2 Instance 3-Deploying Scom monitoring SHAREPOINT1-DB preparation

In the previous section of SharePoint 2013 Instance 1-building a three-tier server farm, we have built a three-tier farm for SharePoint 2013. At the beginning of this section, we use System Center Operation Manager R2 (scom) to monitor this three-tier farm.

With scom we can monitor the SharePoint farm in the following ways:

1. HW monitoring: Can monitor the operating status and performance status of CPU, memory, hard disk space, network, etc. of the server in the farm.

2. OS monitoring: Can monitor the OS system services, system logs and other status.

3. DB monitoring: You can monitor the health, job status, etc. of SharePoint db instances.

4. SP monitoring: Use the MP pack to monitor SharePoint applications, monitor SharePoint Health Analytics reports, application services, logs, and more.

5. APM Monitoring: You can perform code-level monitoring of Web applications on the SharePoint front-end.

Next we'll start installing the deployment scom server.

First, we still need to install a SQL Server for scom: SRV-SQL03, such as the Red Place.

The physical separation of scom databases and SharePoint databases here is primarily due to the subsequent expansion of scom to other business servers, and the use of active-active SQL clusters (db#1 and db# in the diagram). 2) to assume the database instances for SharePoint and Scom and SCDPM, which will be covered in other chapters later.

650) this.width=650; "title=" clip_image002 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image002" src= "http://s3.51cto.com/wyfs02/M02/6E/C6/wKioL1WHv9CBOYJKAAEwT1sKva0261.jpg" height= "455"/>

Install the server configuration and account number as follows:

Server	Host Name	Memory	Ip
Database db#3	Srv-sql03	12G	192.168.5.65

Name	Role	Permissions
Xcloud\sql_install	SQL Server Installation Account	Members of the SQL Server local Administrators group
Xcloud\sql_service	SQL Server service Account	No

We open the SQL installer for a completely new stand-alone installation.

650) this.width=650; "title=" clip_image004 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image004" src= "http://s3.51cto.com/wyfs02/M00/6E/C6/wKioL1WHv9ezQwT6AADyERWjD3U195.jpg" height= "/>"

Choose SQL Server Feature Installation

650) this.width=650; "title=" clip_image006 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image006" src= "http://s3.51cto.com/wyfs02/M01/6E/C6/wKioL1WHv9ygKWQAAAFRs7-x64Y207.jpg" height= "420"/>

Select the following features:

650) this.width=650; "title=" clip_image008 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image008" src= "Http://s3.51cto.com/wyfs02/M02/6E/C6/wKioL1WHv-TjqD2CAAIMvWzUvUg272.jpg" height= "520"/>

Here the instance name is msscom and installed on the D drive

650) this.width=650; "title=" clip_image010 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image010" src= "http://s3.51cto.com/wyfs02/M00/6E/C6/wKioL1WHv-zRhMGJAAFUOaxOhQQ702.jpg" height= "417"/>

Define the SQL Service account

650) this.width=650; "title=" clip_image012 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image012" src= "http://s3.51cto.com/wyfs02/M01/6E/C6/wKioL1WHv_CQwatAAAFwXsT9Zj8333.jpg" height= "417"/>

Collation Selection: SQL_Latin1_General_CP1_CI_AS

Although scom collations support SQL_Latin1_General_CP1_CI_AS and Chinese chinese_prc_ci_as

And Latin1_General_CI_AS, French_CI_AS, Cyrillic_general_ci_as, Japanese_ci_as, Traditional_spanish_ci_as, However, the instance collation of the data warehouse only supports SQL_Latin1_General_CP1_CI_AS, so here the collation is selected as above.

650) this.width=650; "title=" clip_image014 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image014" src= "http://s3.51cto.com/wyfs02/M02/6E/C6/wKioL1WHv_nDqNYAAAEoG6VSLK8531.jpg" height= "416"/>

Here by the way, the letter meaning of the collation is:

SQL =sql Server collation, direct null =windows collation;

CP1 specifying the code page sort order

CI = case insensitive, cs= case sensitive;

AI = accent-insensitive, as = accent-sensitive;

So sql_latin1_general_cp1_ci_as says: Using SQL Collation Latin1_General, case-insensitive, accent-sensitive, non-Unicode data on code page 1252, sort order 52.

650) this.width=650; "title=" clip_image016 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image016" src= "http://s3.51cto.com/wyfs02/M00/6E/C6/wKioL1WHv_3hs-8PAAFlMIp3Hmg575.jpg" height= "/>"

Specify administrator

650) this.width=650; "title=" clip_image018 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image018" src= "http://s3.51cto.com/wyfs02/M01/6E/CA/wKiom1WHvknyDr_VAAGBCEaTTao117.jpg" height= "419"/>

Specify Reporting Services Configuration mode

650) this.width=650; "title=" clip_image020 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image020" src= "http://s3.51cto.com/wyfs02/M01/6E/CA/wKiom1WHvlCjwkguAAFXyRR-1Gg563.jpg" height= "419"/>

Final confirmation of installation

650) this.width=650; "title=" clip_image022 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt = "clip_image022" src= "http://s3.51cto.com/wyfs02/M02/6E/CA/wKiom1WHvljyZQGxAAFSRJ4aL6w858.jpg" height= "418"/>

Final installation Complete

650) this.width=650; "title=" clip_image024 "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=" clip_ image024 "src=" http://s3.51cto.com/wyfs02/M00/6E/CA/wKiom1WHvlzweq1GAAGlH7tDS6U051.jpg "height=" 419 "/>

The database for scom is ready to be completed.

It's a good idea to have another instance to use as a database for scom's Data Warehouse, and then start installing scom.

This article is from the "Iron Fist of the Invincible Speaker" blog, please be sure to keep this source http://yaojiwei.blog.51cto.com/762134/1664140

System Center R2 Instance 3-Deploying Scom monitoring SHAREPOINT1-DB preparation