dep302 server consolidation strategies & best practices for reducing costs in windows...

44
DEP302 Server Consolidation Strategies & Best Practices for reducing costs in Windows Environments Troy Zaboukos [email protected] Product Manager Windows Server Division Paul O’Connell [email protected] om Principal Consultant Business Critical Services Microsoft UK

Upload: giles-park

Post on 26-Dec-2015

216 views

Category:

Documents


0 download

TRANSCRIPT

DEP302Server ConsolidationStrategies & Best Practices for reducing costs in Windows Environments

Troy Zaboukos

[email protected]

Product Manager

Windows Server Division

Paul O’Connell

[email protected]

Principal Consultant

Business Critical Services

Microsoft UK

Agenda

Approach to consolidation

Tools & resources

Consolidation Scenarios

The Process of consolidation

The Service to be consolidated

Design Considerations

Lessons learnt

Windows 2000 Consolidations

Reduces server staff 11%

Reduces TCO 17%, Reduces servers 50%

63% Consolidation in Domain ServersReduces TCO 26%

Reduces staffing 33%

Saved $1.4M

25% reduction in F/P$800K Savings

Reduces servers 30%Apps 30% faster

Reduced TCO 33%Increased trading

capacity 3X

Reduces staffing 80%

15% reduction in TCODowntime cut 41%

City of Hambur

g

20% Consolidation

70 servers reduced to 3

Saved $500KConsolidated sites 23-7

Payback in 6 mos

Reduces costs 57K in 5-2 consolidation

30% consolidation

25% consolidation

$1.2M saved

840K Savings

14-1 consolidation

12-1 consolidation

Microsoft’s Approach

File ServerFile Server

EmailEmail DatabaseDatabaseMigration/consolidation

Migration/consolidation

Operational Operational Excellence & Excellence & ManagementManagementIm

prove M

anagement

Impro

ve Management

Increasing Operational EfficiencyIncreasing Operational Efficiency

Stan

dard

ization

Stan

dard

ization

Consolidate by workload

Complexity & RiskComplexity & Risk

Single Single WorkloadWorkload

File/PrintFile/Print

DatabaseDatabase

MessagingMessaging

DomainDomain

WebWeb LOB AppLOB App

Multiple Multiple WorkloadsWorkloads

LOB AppLOB App

LOB AppLOB App

Mixed Mixed WorkloadWorkload

Branch OfficeBranch Office

Tools & ResourcesIf you need to cost justify:

TCO Calculator

Rapid Economic Justification

If you’re not sure where to start:

Microsoft Services QuickStart for Server Consolidation

Microsoft End to End Consolidation Services

If you’re looking for prescriptive guidance:

Microsoft Systems Architecture

What’s the problem?

IT Budgets under pressure

Demands of IT by the business

Quality of Service

Manageability of a multitude of IT systems

What’s the answer?

Business Value of Technical Solutions

Costs and Risk

Consolidation ScenariosScenarioScenario Business ChallengeBusiness Challenge

DatabaseDatabaseToo many servers Too many servers

running at low running at low capacity.capacity.

Multiple databases, Multiple databases, Single Server Single Server

DSUDSU

MessagingMessagingMessaging server Messaging server farms growing to farms growing to

ensure scaleensure scale

5000 concurrent 5000 concurrent users on a single users on a single Exchange server Exchange server

File & PrintFile & PrintSprawl of servers Sprawl of servers without consistent without consistent

managementmanagement

Clustered File Clustered File Server InstancesServer Instances

FSUFSU

Windows AdvantageWindows Advantage

DomainDomainNT 4.0 DomainsNT 4.0 DomainsNumber in the Number in the

hundredshundreds

Windows Active Windows Active Directory Directory ScalabilityScalability

Web Web ApplicationApplication

Application Application Servers at low Servers at low

capacitycapacity

IIS 6.0 - .Net IIS 6.0 - .Net Application Application

domains ASUdomains ASU

Server Consolidation

The Process

StandardStandardConfigurationConfiguration

ScalableScalableReliableReliableSecureSecure

ConfigurationConfigurationMSAMSA

ManagementManagementBestBest

PracticesPracticesMOF/ITILMOF/ITIL

Delivery Tools

DeliveryTools

StandardStandardProcessProcess

QuickStartQuickStart

Fixed-time,Fixed-time,fixed-pricefixed-price

assessmentassessmentserviceservice

Legacy & Future

ForwardForwardConsolidationConsolidation

BackwardBackwardConsolidationConsolidation

Microsoft/PartnersMicrosoft/PartnersEnd to end Consolidation ServicesEnd to end Consolidation Services

Assessment service

Fixed time/fixed price packaged offering

Integrates Microsoft/partner best practices

Prescriptive content focused on…First pass design

Capacity planning

Identifying business drivers

Identifying targets for consolidation

Deliverable: Detailed execution planDeliverable: Detailed execution plan Design/deploy by MCS, partner or customerDesign/deploy by MCS, partner or customer

Microsoft End to End Server Consolidation Methodology

Datacentre Advisory Council Best practice approach for Server Consolidation.

http://www.microsoft.com/windows2000/server/evaluation/

business/overview/scalable/bpdcac.asp

Plan Build Deploy

Evaluate1. Assess Current Infrastructure2. Identify GoalsPlan

3. Design New Environment

4. Plan MigrationBuild5. Build, Test, Implement Pilot6. Plan User/Data Migration

Deploy7. Implement Production8. Migration Users/Data9. Evaluate and Review

Operate10. Operations

PartnersPartners

OperateEvaluate

Project Delivery

Business GoalsTCO Analysis

Additional business drivers

Systems ArchitectureArchitected Technical Solution

Systems ManagementService Monitoring

Capacity Management

Software/Patch Deployment

Inventory

Service ManagementOperational Process

Systems Architecture

(Technology)

Service Management

Systems Management

Business Value

The Business process

Initial assessment of business driversTotal Cost of Ownership – using TCO Analyst Tool from GartnerITIL analysis by cost type e.g. hardware, software, accommodation etc.

Future StateTCO figures recalculated to show predicted benefitCost reduction by server type

Measure the successHow will improved quality of service be measured?

Costing the service – The IT Infrastructure Library (ITIL) way

The overall cost of a service can be subdivided into cost types

Cost type Example

Hardware Depreciation cost of servers - negative

Software Licenses for management agents, OS

People Support engineers

Accommodation Data centre provision costs such as racking

External Consulting Support, outsourcing

Transfer Payroll services cross charged within the organisation

Systems Management

• Key areas of systems management for consolidated environment Service Monitoring and Control

MOM, http://www.microsoft.com/solutions/msm/

Capacity Management right amount at the right time at the right costs

Software Distribution and Patch Management SMS 2.0, http://www.microsoft.com/solutions/msm/

Hardware and software inventory SMS 2.0

Microsoft Operations Framework

Security AdministrationSecurity AdministrationSystem AdministrationSystem AdministrationNetwork AdministrationNetwork AdministrationService Monitoring & ControlService Monitoring & ControlDirectory Services AdminDirectory Services AdminStorage ManagementStorage ManagementJob SchedulingJob SchedulingPrint/Output ManagementPrint/Output Management

Service Level ManagementService Level ManagementCapacity ManagementCapacity Management

Availability ManagementAvailability ManagementFinancial ManagementFinancial Management

Workforce ManagementWorkforce ManagementService Continuity MgtService Continuity Mgt

Change ManagementChange ManagementConfiguration ManagementConfiguration ManagementRelease ManagementRelease Management

Service DeskService DeskIncident ManagementIncident ManagementProblem ManagementProblem Management

Release Release ReadinessReadiness

ReviewReview

Release Release Approved Approved

ReviewReview

SLASLAReviewReview

OperationsOperationsReviewReview

ChangingChanging

OperatingOperatingSupportingSupporting

OptimizingOptimizing

MicrosoftOperationsFramework

Operations • Key areas of systems management

for consolidated environment (1)• All of them……but………

Capacity Management• Is the environment unconsolidated?

• How do you know?

• How did the environment become unconsolidated?

Change Management• Greater dependence on fewer systems

• Increased impact of poor change procedure

Operations

• Key areas of systems management for consolidated environment (2)

Configuration Management• Cornerstone for change management

• Start with achievable targets

Incident/Problem Management

What are the events/alerts Operations need to be aware of in advance of a system going live?

Service Improvement Program

Server Consolidation

The services

Consolidated Service Utility What is a Consolidated Service Architecture

An internal consolidated hosting architecture for a specific IT service. Objective: A shared server environment that supports application concurrency and provides High Reliability, Availability and Scalability, and decrease time to market to support business growth. Consolidation !!!!!!!!!!!!!!!!!!

“Elements of a Consolidated Service Architecture:Hosts a single service (Database, File and Print, Web Applications, LOB Applications)Provides a chargeback mechanism.Includes Managed or consolidated storage.Single Site clustering or multi site clustering.Built with Headroom and Growth in mind.Managed as a service Utility - SLA’S.MOF Principles/Processes embedded

File Service Hosting Service Hosting Virtual File ServersKey architectural components:

Windows Powered NASServer OEM selectionStorage Area Network

MSCS - ClustersMultiple Site Asynchronous ReplicationSnapshot Copy integration

Capacity Planning MethodologyData Backup and RecoveryVolume size planning SRM Integration for reportingPerformance Testing/ User modeling

Chargeback accountingBased on Disk, single charge for a virtual server

File Consolidation Questions

Determine data requirementsWhat data/files are active?Where is the data?Who owns the data?What is the business value of the data?

Consolidate Storage Resources –SAN or NAS?Migrate data from multiple sources to few

Consolidate File ServersMove from multiple single host/DAS configurations to central source

Enables consolidation of backup and print serversDo you have tools/process to manage many as one

File: Moving the file store

First step – assess your environmentSRM solutions allow you to see actual usage

Report on what users use which filesCan find duplicate and redundant filesReports can predict growth- use to determine size of NAS solution

Consolidate from multiple file servers or DAS environment to single NAS

Tools available to aid in migration with little disruptionConfigure system to enable sharing amongst appropriate users

File: Staying Consolidated

Continuous use of SRM solution will ensure effective utilization of resources

Restrict certain filesOption: set quotas on individual users

Determine if files that are aged, not accessed recently should be removed

Reports help determine growth requirements

Employ additional featuresReplication solutions (SNAP, Mirroring) for data availability

Clustering for high availability and reliability

File directory services for ease of use and management of files

Application Hosting Service Hosting LOB/Web ApplicationsKey architectural components:

WSRM Resource ManagerDevelopment Environment

COM.NETJava

Application IsolationLoad Balancing Storage Area NetworkChargeback accounting

Based on CPU, Memory, Disk or charge for % Server used

Application Consolidation – no magic bullet!!!

ToolTool

LimitLimit

Best Best forfor

Hardware Hardware

partitioningpartitioning

(HP, IBM, Unisys)(HP, IBM, Unisys)

Very high-throughput Very high-throughput applicationsapplications

Complete isolation of Complete isolation of applications applications

Re-sizing partitions Re-sizing partitions requires a rebootrequires a reboot

Capacity in 4-procCapacity in 4-proc incrementsincrements

Resource Resource Management Management

(WSRM)(WSRM)

Medium-high Medium-high throughput throughput applicationsapplications

Manages resource Manages resource usageusage

All applications All applications must run on same must run on same OS levelOS level

OS/HW single point OS/HW single point of failureof failure

Virtualization Virtualization

(Virtual Server)(Virtual Server)

More complex More complex managementmanagement

Performance “tax”Performance “tax”

Low-throughput Low-throughput applicationsapplications

Legacy applications Legacy applications

AC: What Does WSRM Do?

Allows an administrator to set application resource consumption policies (CPU and memory)

Select processes to be managed

Set resource consumption targets or limits

Manage computer resources according to policies

Percentage of CPU use

Process working set size (physical resident pages)

Committed memory (page table and page file usage)

Apply policies based on a date/time schedule

Generate, store, view, and export accounting records

Generate email notification for events

AC: What is the WSRM Service?

WSRMWSRM includes two components, one for administration and one for managed computers

Written in C++, runtime check ensures it is running on the appropriate OS, preventing confliction problems

How it worksWSRM service polls system, examines %CPU usage of processes by Process Match Criteria

Base priority of managed processes is dynamically modified

On a busy system with CPU-bound processes, consumption matches allocations closely

Allocation above what a group is able to consume (for any reason) will be reallocated to other groups in same proportion as defined in the policy

CPU resource above what all groups are able to consume is allocated via the normal kernel scheduler algorithm

AC: What are Resource Allocation Policies?

Resource Allocation Policy allocates resources to sets of processes

Sub-divides all of the managed resources of the computer

Order of allocation rules within the policy determines order of process matching

Many policies may be defined, however only one can be in effect at a given time

Resource Allocation Policies can be scheduled or manually activated

AC: Job Accounting Records

Process resource counters are periodically sampled

Accounting records are generated and stored on a slower interval (10 minutes, but modifiable)

No separate database required as WSRM implements a database in the service

Accounting records include:User, domain, file name/path, Process Matching Criteria, and Resource Allocation name, PID, Process start time, end time

Resource Statistics: kernel time, total CPU time, handles, thread count, I/O bytes, etc.

Full-featured retrieval interfaceAggregate, sort, and filter columns

Save and load views

Export formats: tab-delimited, .CSV, and SMF

Support charge-back and capacity planning

AC: Limitations in WSRM

No 64-bit client support until Whidbey (64-bit VS.NET, released first on Longhorn)

Does not manage key system services (including itself). This is by design.

Not for use on systems being managed by other RM tools

Proccon, ESS, or other Job Object oriented tools

Aurema, or other process-oriented tools

Does not manage other types of memory resources

AWE memory/Large page memory/Locked memory

OS Pool memory (paged or non-paged)

Does not manage I/O

AC: WSRM Availability

Timing WSRM final release shipped with Windows Server 2003 final release

WSRM is not built-in to Windows Server 2003Separate CD & separate installation processOnly Enterprise and Datacenter Editions (32 and 64 bit)

Correct platform is verified at install and startupAdministrative UIs are supported on back level platforms

W2K (all SKUs)XP ProfessionalWS3 (all 32-bit SKUs)

WSRM will be fully integrated into next major Windows release

DataBase Hosting Service Hosting Multiple Instances of a RDBMS Key architectural components:

Resource ManagerServer OEM selectionStorage Area Network

MSCS - ClustersData ReplicationMultiple Site Asynchronous ReplicationSnapshot Copy integration/VDS for Storage automation

Capacity Planning MethodologyDatabase Profiling (DSS, OLAP, OLTP)I/O and Network key performance FactorsPre and Post Consolidation analysisCapacity modeling tools (BMC Perform and Predict)

Chargeback accountingBased on Disk, CPU, Memory and Geosite Recovery

Server Consolidation

Design Considerations and lessons learnt

Consolidation PlanningDesign Considerations

Operational Mindset in a Consolidated Service environment

Services and Agent Glut

Pre Consolidation and Post Consolidation Capacity processes

Data Centre Operations Involvement early

Design should meet the stated goal: Save money, raise quality of service

Consolidation PlanningDesign Considerations

Capacity Planning is KingTo Cluster or not to ClusterUnderstand Granular Access Requirements Managed Storage Backup and Recoverability Role of a Resource ManagerDataCenter or Enterprise EditionManagement Infrastructure

Consolidation Lessons Learned

Backup and Recoverability Procedure walk through

Storage Area Network planning

There is no real prescribed method of doing chargeback for resource allocation

Enterprise Server Hardware selection

BMC Perform and Predict excellent tool for capacity management and modeling

Many software agents are not cluster aware

Consolidation Lessons Learned

Disk I/O and Network Utilization planningSelecting a Resource Manager

WSRM Windows Server 2003Aurema ArmTech (Windows 2000)Process ControlHP RPM Toolset

Create a Plan to move maxed resourcesTest, Test, Test

Q&A

Community Resources

Community Resourceshttp://www.microsoft.com/communities/default.mspx

Most Valuable Professional (MVP)http://www.mvp.support.microsoft.com/

NewsgroupsConverse online with Microsoft Newsgroups, including Worldwidehttp://www.microsoft.com/communities/newsgroups/default.mspx

User GroupsMeet and learn with your peershttp://www.microsoft.com/communities/usergroups/default.mspx

evaluationsevaluations

© 2003 Microsoft Corporation. All rights reserved.© 2003 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.