operations manager 2007 r2 sizing helper

8/7/2019 Operations Manager 2007 R2 Sizing Helper

http://slidepdf.com/reader/full/operations-manager-2007-r2-sizing-helper 1/101

** To use this Sizing Helper - you need to enable this content to r

You should see a Security Warning below the ribbon bar (& above the formular

Click the Options button and select "Enable this Content"

Small to Medium Deployment

(250-1000 computers)

Advanced Deployment(Cross Platform, Remote Sites, URL, AEM)

Large Deployment(1000-10,000 computers)

Sizi



un Macro

bar) indicating Macros have been disabled.

Supported Configuration and Best Pr

How to assess current managementcapacity?

ng Helper

Data Warehouse Disk Configurat



Small to Medium Deployment

(250-1000 computers)** click on the scenario to see HW recommendations

Scenario 1# of Computers (Windows/Unix or Linux)

# of Windows Computers

# of Remote Sites for Windows Computers

# of Windows Computers in Each Remote Site

# of Unix or Linux Computers# of Remote Sites for Unix or Linux Computers

# of Unix or Linux Computers in Each Remote Site

Estimated # of Simultaneous Operations Consoles


# of Windows Computers# of Remote Sites for Windows Computers


# of Unix or Linux Computers

# of Remote Sites for Unix or Linux Computers










Back to Scenarios




Scenario 4

# of Computers (Windows/Unix or Linux)# of Windows Computers









1-250

1-250

0

0

00

0

5

251-500

251-5000

0

0

0

0

5

501-750

501-750

0

0

0

0

0



10

751-1000751-1000

0

0

0

0

0

10



Large Deployment

(1000-10,000 computers)** click on the scenario to see HW recommendations






















Back to Scenarios



1001-3000

1001-3000

0

0

00

0

25

3001-6000

3001-60000

0

0

0

0

50

6001-10000

6001-10000

0

0

0

0

0



25



Advanced Deployment

(Cross Platform, Remote Sites)** click on the scenario to see HW recommendations






















Back to Scenarios




Scenario 11

Large Scale URL Monitoring

Scenario 12

Large AEM Monitoring



6000

6000

2

2000; 1000

00

0

50

3000

25000

0

500

0

0

25

2900

2500

0

0

400

2

200; 100



25



Supported Configuration

Agents & Consoles

3,000 agents reporting to a management server

1,500 agents reporting to a gateway server

6000 Computers [Windows/Unix or Linux] computer

10000 Computers [Windows/Unix or Linux] computer

Clients - Application Error Monitoring

25,000 Application Error Monitoring (AEM) machines r

100,000 AEM machines reporting to a dedicated mana

Cross-Platform Monitoring

500Unix or Linux computers monitored per dedic

100Unix or Linux computers monitored per dedic

URL Monitoring

3000 URLs monitored by a dedicated management

12000 URLs monitored by a dedicated management

Please refer to the following link for the latest updated O

Best Practices

Disk Configuration

For all the Server Roles, we recommend storage controlle

Please refer to the following link for the latest updated O

Back to Scenarios



s monitored per management group with 50

s monitored per management group with 25

eporting to a dedicated management server

ement group

ted management server

ted gateway server

server

group

sMgr R2 Supported configuration:

r with battery-backed write cache enabled

sMgr R2 Design Guide:



consoles opened simultaneously

consoles opened simultaneously

http://technet.microsoft.com/en-us/library/bb309428.aspx

http://technet.microsoft.com/en-us/library/dd789005.aspx







How to assess current management group capacit

Summary

Management group capacity can be bound by a combination of: IOPS an

Assessing the current IOPS used by the current deployment will give yo

additional capacity is available to manage additional computers (assumi

Assessing current performance health

Before we start assessing the current level of capacity, let's make sure

If the current deployment is already running over capacity, then that ne

There are several key performance counters (on the SQL server hosting

If any of the following counters does not meet the specified threshold, t

LogicalDisk(*)\% Idle Time

(If 0 for a long time, then indicate

LogicalDisk(*)\Avg. Disk Queue Length

< 2 (for each disk participating

LogicalDisk(*)\Avg Disk sec/Read

< 20ms (preferrably < 10ms)

LogicalDisk(*)\Avg Disk sec/Write

< 20ms (preferrably < 10ms)

Another key performance indicator is whether the SQL server hosting th

MSSQL:Buffer Manger\Buffer cache hit ratio

Should be as close to 100% as pos

Assessing available capacity

If the above counters falls well within the specified threshold, then your

Now we can address the original question of assessing current manage

This depends mostly on the disk throughput (measured by IOPS) curren

The best way to figure out how much IOPS you currently have is to talk

You can also determine maximum throughput by measuring it using too

SQLIO Download: http://www.microsoft.com/downloads

SQLIO Documentation: http://technet.microsoft.com/en

However, to use SQLIO, you have to test your disks in a lab (not in a pro

If you just want to make a rough guess, here's a table to help you out:

Disk Estimated Maximum T

Back to Scenarios



15k SCSI/SAS/FC 174

10K SCSI/SAS/FC 125

7.2k SATA 74

Assessing current capacity

Now you need to determine how much IOPS your management group is

To find out, sample the counter "Physical Disk\Disk Transfers/sec" throu The average is the current IOPS utilized by your management group

Assuming the management group currently manages 1000 computers.

It consumes 1000 IOPS and the disk array has 4000 IOPS in terms of av

This means on average, the system requires 1 IOPS per computer, leavi

However, to be conservative, you want to leave 20% buffer to the syste



y?

d available server memory.

an idea of how much

ing the number of consoles remain constant)

our overall deployement is healthy, performance wise.

ed to be addressed first.

the Ops DB) that can be utilize to make this asssessment.

en it indicates insufficient disk I/O and more disk spindles need to be added.

disk perf issue)

in the array. E.g. < 4 for a 4 disk RAID 10 configuration)

e Ops DB has sufficient memory, this can be assessed using the following count

sible. < 80% indicates SQL server needs more memory

management group is likely to be in good performance health

ent group capacity.

ly being utilized and the maximum IOPS that your disk array provides.

o the person in charge of your SAN or storage array (or the vendor)

ls like SQLIO

/details.aspx?familyid=9a8b005b-84e4-4f24-8d65-cb53442d9e19&displaylang=

-us/library/cc966412.aspx#EDAA

duction environment).

eoretical Random IO



currently utilizing.

ghout the peak of a normal business day and calculate its average

ilable capacity

ng an available capacity of managing an additional 3000 computers

m, leaving an available capacity of 2200 additional computers to be managed



r & threshold:

n



Scenario 1








Minimum Hardware Recommendation:Role: Root Management Server, Operations

& Operations Data Warehouse Server

Hardware:

• 4 disk RAID 10 (147GB)

• 8 GB RAM

• Quad Proc

DB Size

Number of Days for Data Retention

Number of Computers Total Size (MB)

Total Size (GB)

Suggested Space Allocation

with 50% buffer (GB)

DW Size


Number of Computers

Total Size (MB)

Total Size (GB)Suggested Space Allocation


Back to Scenarios



1-2501-250

0

0

0

0

0

5

Database Server,

(w/ SRS & Web Console Server)

7

2504104.48

4.01

6.01

365

250

165799.28

161.91178.10



Scenario 2








Minimum Hardware Recommendation:Role: Root Management Server

Hardware:

• 2 disk RAID 1

• 4 GB RAM

• Dual Proc

Role: Operations Database Server,

& Operations Data Warehouse Server

Hardware:

• 6 disk RAID 10 (147GB)• 4 GB RAM

• Dual Proc

DB Size


Number of Computers

Total Size (MB)

Total Size (GB)



DW Size


Number of Computers

Total Size (MB)

Total Size (GB)


Back to Scenarios



251-500251-500

0

0

0

0

0

5

(w/ SRS & Web Console Server)

7

500

8208.97

8.02

12.02

365

500

331598.55

323.83

356.21



Scenario 3









Hardware:

• 2 disk RAID 1

• 8 GB RAM

• Dual Proc

Role: Management Server

Hardware:

• 2 disk RAID 1

• 4 GB RAM• Dual Proc

Role: Operations Database Server

Hardware:

• 4 disk RAID 10

• 4 GB RAM

• Dual Proc

Role: Operations Data Warehouse Server (w/ SRS and

Hardware:• 8 disk RAID 10 (147GB) (Data)

• 2 disk RAID 1 (Log)

• 4 GB RAM

• Dual Proc

DB Size

Number of Days for Data Retention 7

Number of Computers 750

Back to Scenarios



Total Size (MB) 12313.45

Total Size (GB) 12.02

Suggested Space Allocation 18.04


DW Size

Number of Days for Data Retention 365Number of Computers 750



Suggested Space Allocation 534.31




501-750501-750

0

0

0

0

0

10

eb Console Server)



Scenario 4

Number of Computers (Windows/Unix or Linux)Number of Windows Computers

Number of Remote Sites for Windows Computers

Number of Windows Computers in Each Remote Site

Number of Unix or Linux Computers

Number of Remote Sites for Unix or Linux Computers

Number of Unix or Linux Computers in Each Remote Site

Estimated number of Simultaneous Operations Consoles


Hardware:

• 2 disk RAID 1

• 8 GB RAM

• Dual Proc


Hardware:

• 2 disk RAID 1

• 4 GB RAM• Quad Proc


Hardware:

• 4 disk RAID 10 (Data)


• 8 GB RAM

• Dual Proc

Role: Operations Data Warehouse ServerHardware:

• 10 disk RAID 10 (300GB) (Data)


• 8 GB RAM

• Dual Proc

Role: SRS and Web Console Server

Hardware:

Back to Scenarios



• 2 disk RAID 1

• 4 GB RAM

• Dual Proc

DB Size



Total Size (GB)



DW Size


Number of Computers

Total Size (MB)





751-1000751-1000

0

0

0

0

0

10



7

100016417.93

16.03

24.05

365

1000

663197.11

647.65712.42



Scenario 5









Hardware:

• 4 disk RAID 10

• 12 GB RAM

• Quad Proc


Hardware:

• 4 disk RAID 10



Hardware:



• 8 GB RAM

• Quad Proc

Role: Operations Data Warehouse ServerHardware:



• 8 GB RAM

• Quad Proc


Hardware:

Back to Scenarios



• 2 disk RAID 1

• 4 GB RAM

• Quad Proc

DB Size



Total Size (GB)



DW Size


Number of Computers

Total Size (MB)





1001-30001001-3000

0

0

0

0

0

25



7

300049253.80

48.10

72.15

365

3000

1989591.33

1942.962137.26



Scenario 6









Hardware:

• 4 disk RAID 10

• 16 GB RAM

• Quad Proc

Role: Management Server (managing up to

Hardware:

• 4 disk RAID 10



Hardware:

• 4 disk RAID 10

• 8 GB RAM

• Quad Proc


Hardware:• 14 disk RAID 10 (Data)


• 16 GB RAM

• Quad Proc

Role: Operations Data Warehouse Server

Hardware:


Back to Scenarios




• 16 GB RAM

• Quad Proc


Hardware:

• 2 disk RAID 1• 4 GB RAM

• Quad Proc

DB Size


Number of Computers

Total Size (MB)

Total Size (GB)



DW Size


Number of Computers

Total Size (MB)

Total Size (GB)





3001-60003001-6000

0

0

0

0

0

50

3000 agents)

3000 agents)



7

6000

98507.61

96.20

144.30

365

6000

3979182.66

3885.92

4274.51



Scenario 7









Hardware:

• 6 disk RAID 10

• 32 GB RAM

• 2 Quad Proc


Hardware:

• 4 disk RAID 10



Hardware:

• 4 disk RAID 10

• 8 GB RAM

• Quad Proc


Hardware:• 4 disk RAID 10

• 8 GB RAM

• Quad Proc


Hardware:

• 2 disk RAID 1

• 4 GB RAM

Back to Scenarios



• Quad Proc


Hardware:



• 32 GB RAM• 2 Quad Proc


Hardware:



• 32 GB RAM

• 2 Quad Proc

Role: SRS and Web Console ServerHardware:

• 2 disk RAID 1

• 4 GB RAM

• Quad Proc

DB Size


Number of Computers

Total Size (MB)

Total Size (GB)



DW Size


Number of Computers

Total Size (MB)

Total Size (GB)





6001-100006001-10000

0

0

0

0

0

25

3000 agents)

3000 agents)

3000 agents)

1000 agents)



7

10000

164179.35

160.33

240.50

365

10000

6631971.09

6476.53

7124.19



Scenario 8









Hardware:

• 4 disk RAID 10

• 16 GB RAM

• Quad Proc

Role: Management Server (managing 3000

Hardware:

• 4 disk RAID 10


Role: Management Server (managing 3 Gat

Hardware:

• 4 disk RAID 10

• 8 GB RAM

• Quad Proc




• 16 GB RAM

• Quad Proc


Hardware:


Back to Scenarios




• 16 GB RAM

• Quad Proc


Hardware:


• Quad Proc

Role: Gateway Server (managing 1500 agen

Hardware:

• 4 disk RAID 10

• 8 GB RAM

• Quad Proc

Role: Gateway Server (managing 1000 agenHardware:

• 4 disk RAID 10

• 4 GB RAM

• Quad Proc

Role: Gateway Server (managing 500 agent

Hardware:

• 2 disk RAID 1

• 4 GB RAM

• Dual Proc

DB Size


Number of Computers

Total Size (MB)

Total Size (GB)



DW Size


Number of Computers

Total Size (MB)

Total Size (GB)





60003000

2

2000; 1000

0

0

0

50

gents)

way Servers)



ts)

ts)

s)

7

6000

98507.61

96.20

144.30

365

6000

3979182.66

3885.92

4274.51



Scenario 9









Hardware:

• 4 disk RAID 10

• 12 GB RAM

• Quad Proc


Hardware:

• 4 disk RAID 10


Role: Management Server (managing 500 U

Hardware:

• 4 disk RAID 10

• 8 GB RAM

• Quad Proc




• 8 GB RAM

• Quad Proc


Hardware:


Back to Scenarios




• 8 GB RAM

• Quad Proc


Hardware:


• Quad Proc

DB Size


Number of Computers

Total Size (MB)

Total Size (GB)

Suggested Space Allocationwith 50% buffer (GB)

DW Size


Number of Computers

Total Size (MB)

Total Size (GB)





30002500

0

0

500

0

0

25

gents)

nix or Linux computers)



Scenario 10









Hardware:

• 4 disk RAID 10

• 12 GB RAM

• Quad Proc


Hardware:

• 4 disk RAID 10


Role: Management Server (managing 100 U

Hardware:

• 2 disk RAID 1

• 4 GB RAM

• Dual Proc

Role: Management Server (managing 3 Gat

which manages the Unix or Linux coHardware:

• 2 disk RAID 1

• 4 GB RAM

• Dual Proc


Hardware:


Back to Scenarios




Number of Computers

Total Size (MB)

Total Size (GB)





29002500

0

0

400

2

200; 100

25

gents)

nix or Linux computers)

way Servers,

puter in remote sites )



r Linux computers in first remote site)

r Linux computers in first remote site)

r Linux computers in second remote site)

7

2900

47612.01

46.50

69.74



365

2900

1923271.62

1878.19

2066.01



Scenario 11

Large Scale URL Monitoring

Rule of Thumb 1:

Rule of Thumb 2: Must use dedicated management group

Rule of Thumb 3: Always use dedicated management ser

Rule of Thumb 4: 1 dedicated management server can m

Rule of Thumb 5: 1 dedicated management group can ma

Number of URLs RMS MS

1-1000 URLs

1001-3000 URLs

3001-6000 URLs

6000-12000 URLs

All rule of thumbs and numbers present

• 2 disk RAID 1


• 2 disk RAID 1


• 2 disk RAID 1• 4 GB RAM• Dual Proc

• 2 disk RAID 1• 8 GB RAM• Quad Proc





Back to Scenarios



if monitoring more than 1000 URLs

er if monitoring more than 50 URLs

nage up to 3000 URLs

nage up to 12,000 URLs (**when using the Bulk URL Editor)

DB+DW+RS Notes

ed here applies only to URL monitoring created with the Bulk URL Editor


• 2 disk RAID 1 (Log)• 4 GB RAM• Dual Proc

1 dedicated

Management Server

• 4 disk RAID 10 (Data)• 2 disk RAID 1 (Log)• 4 GB RAM• Dual Proc

1 dedicatedManagement Server

• 8 disk RAID 10 (Data)• 2 disk RAID 1 (Log)• 8 GB RAM• Quad Proc

2 dedicatedManagementServers

• 8 disk RAID 10 (Data)• 2 disk RAID 1 (Log)• 16 GB RAM• Quad Proc

4 dedicatedManagementServers



OpsMgr DB: Number of Days for Data Retention 7

Fudge Factor 1.5

Total Number of events collected per day 196.14

Average size of an event on disk 862.15

Total number of alerts collected per day 0.72

Average size of an alert on disk 29689.4

Total number of perf counter collected per day 8911.34Average size of a perf counter on disk 129.29

Total number of state changes collected per day 47.52

Average size of a state change on disk 1935.83

Number of Server Computers 10000



Total Size (GB) with 50% Buffer 240.50

Back to Scenarios



OpsMgr DW: Number of Days for Data Retention 365

Fudge Factor 1

Total Number of events collected per day 196.14

Average size of an event on disk 1707.17

Total number of alerts collected per day 0.72

Average size of an alert on disk 1135.63

Total number of perf counter collected per day 8911.34Average size of a perf counter on disk 174.45

Total number of state changes collected per day 47.52

Average size of a state change on disk 315.41

Number of Server Computers 10000



Total Size (GB) with 10% Buffer 7124.19

DW Estimated IOPS Data# of Agents Estimated IOPS

1-250 275

251-500 400

501-750 500

751-1000 600

1001-3000 750

3001-6000 1000

6001-10000 1300

Back to Scenarios



OpsMgr DW Disk Calculator The recommended disk configuration provided in scenarios secti

If the grooming interval is different, you can use the following gui

Step 1: Enter the estimated IOPS for your environment [From DW

Step 2: Enter the Estimated DW Disk Space in GB for you environ

Step 3: Choose the cost effective/best suited "Estimated # of Dis

Example: In the list below the cost effective configurati

Enter Estimated DW IOPS [From DWSize TAB]

Enter Estimated DW Disk Space in GB [From DWSize TAB]

Estimated # of RAID 10 147 GB Disks Needed




Back to Scenarios



ns assumes that the data is kept for 365 days on the Data Warehouse Server.

delines to calculate the optimal disk configuration for the Data Warehouse Serve

Size TAB]

ment [From DWSize TAB]

ks & Configuration" from the options listed below

n to meet the IOPS(1300) and Space(7124GB) is 34 Disk RAID 5 300GB Disk Con

1300

7124.19

106

52

53

34



r

figuration

operations manager 2007 r2 sizing helper

Documents