MMS 2013 Service Manager Scalability

Report
Orchestrator
Runbook Servers
Windows Server 2012
4 vCPUs, 8 – 16 GB RAM
60 GB OS
DR: RTO 24 hours
SM Connection Servers
Windows Server 2012
4 – 8 vCPUs, 8 - 16 GB RAM
60 GB OS
80-100 concurrent sessions/server
DR: RTO 30 minutes
SM Portal
SharePoint / WCS
Windows Server 2012
4 – 8 vCPUs, 8 – 16 GB RAM
60 GB OS, 1 TB+ Data
2-4TB of disk for 1095 days
DR: RTO 24 hours
Datawarehouse DB
SQL 2012
First is failover for Primary
Scale as workloads demand
RTO: Globally Coninuously Available?
SM Management
Servers
Windows Server 2012
4 vCPUs, 16 GB RAM
First is failover for Primary
Scale as workloads demand
RTO: Globally Coninuously Available?
Orchestrator
Management
Windows Server 2012
4 vCPUs, 16 GB RAM
60 GB OS
RTO: Not clear
Windows Server 2012
8 vCPUs, 16 GB RAM
60 GB OS
Scale as workload demands
RTO: 15 min
SM ORCH Target
Server
SM Orchestrator
Server
Windows Server 2012
8 vCPUs, 16 GB RAM
60 GB OS
Scale as workload demands
RTO: 15 min
Windows Server 2012
8 vCPUs, 16 GB RAM
60 GB OS
Scale as workload demands
RTO: 15 min
Windows Server 2012
2 vCPUs, 8 GB RAM
80 GB OS
Scale number as
workloads demand
RTO: 30 min?
Windows Server 2012
2 vCPUs, 8 GB RAM
80 GB OS
Scale number as
workloads demand
RTO: 30 min?
Windows Server 2012
4 vCPUs, 16 GB RAM
Windows Server 2012
24 – 48 vCPUs, 32 – 192 GB RAM
80 GB OS, 600 GB Data
Service Manager DB
SQL 2012
Windows Server 2012
24 – 48 vCPUs, 32 – 192 GB RAM
80 GB OS, 600 GB Data
Service Manager DB
SQL 2012
Active Directory
SCOM, SCCM,
Other Systems
ALTER DATABASE ServiceManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE
ALTER DATABASE ServiceManager SET ENABLE_BROKER
ALTER DATABASE ServiceManager SET MULTI_USER
http://msdn.microsoft.com/en-us/library/ms181007(v=SQL.105).aspx
SELECT name, is_read_committed_snapshot_on FROM
sys.databases where name = 'ServiceManager‘
ALTER DATABASE ServiceManager SET READ_COMMITTED_SNAPSHOT ON
http://blogs.technet.com/b/babulalghule/archive/2013/02/17/how-to-install-service-manager-2012sp1-with-a-sql-2012-alwayson-availability-groups.aspx
http://blogs.technet.com/b/servicemanager/archive/2010/12/02/faq-why-is-my-custom-incident-view-so-slow.aspx
http://blogs.technet.com/b/servicemanager/archive/2011/09/19/new-change-request-type-projections-management-pack.aspx
http://technet.microsoft.com/en-us/library/cc753179(v=WS.10).aspx
http://blog.concurrency.com/infrastructure/service-manager-request-query-result-filtering/
http://blogs.technet.com/b/servicemanager/archive/2013/01/14/troubleshooting-workflow-performance-and-delays.aspx
http://blog.concurrency.com/infrastructure/scsm-notifications-with-orchestrator-roll-up/
http://blogs.technet.com/b/mihai/archive/2012/11/30/configuration-manager-connector-s-dcm-rulecan-cause-massive-performance-issues-in-service-manager.aspx
http://blog.concurrency.com/featured-post/how-to-sync-other-properties-from-active-directory-toservice-manager-using-orchestrator/
http://blog.concurrency.com/infrastructure/virtualization/manually-clearing-orchestrator-logs/
The transform module default batch size is 50,000 items. The batch size can be adjusted by inserting rows into
the DWRepository.ETL.Configuration table as follows:
insert into DWRepository.ETL.Configuration(
ConfigurationFilter,
ConfigurationPath,
ConfiguredValueType,
ConfiguredValue
)
values (
'etl.Transform',
'BatchSize',
'Int32',
'100000'
)

similar documents