DEP 371 Server Consolidation with MSA And Partner Technologies

1. DEP 371Server Consolidation with MSA And Partner Technologies Fred Baumhardt David L. JonesConsultant Enterprise Architect Microsoft UK Unisys Corporation

2. Agenda • The Datacenter Problem • What MSA is • Server Consolidation Approach • MSA Consolidation Guidance • Unisys’ Consolidation Scenarios • Exclusions • Windows Resource Manager • Microsoft Virtual Server

3. Some Core Systems Extranets Internet Systems Project 1…n System Branch Offices Departments The Datacenter Problem • Systems organically grown under a “Project” context • Different areas commissioned systems independently • Security often bolted on as an afterthought if at all • The sticky tape thing sort of works – so lets not touch it ! • The answer to everything used to be: whack another box in

4. Security Consolidation Management Server Sprawl Underutilized Servers Business/IT Shared Priorities Resources Risk Cost Poor Management & Processes Increasing Headcount Reqs

5. Consolidation – Taking Back Control • Consolidation lets us change the organic – sporadic unmanaged growth and revert it to a purpose built Datacenter • Consolidation can reduce operational risk, lower cost, and free resources • The consolidation process looks at all areas of running and operating application infrastructures – rationalises and merges where appropriate

6. META Group Analysts Driving Consolidation • 30% consolidating today • 40% considering – 3 yrs • Server infrastructure consolidation will become mandatory in TCO-optimized shops • 69% consolidating • 25% considering • 6% not consolidating • 30-40% cost reduction possible

7. What Is MSA? • Prescriptive and Architectural technical guidance designed to help in • Planning • Building • Deploying • Operating • In Consolidation – MSA is the blueprint for the end-state – It is what you consolidate to

9. Sample Business Requirements Planning Guide (Design Choices and how we arrived at them) for sample instantiation Test guides, scripts, and test results for sample instantiation Solution Operations Guide for sample instantiation Build Guides (How-to) for sample instantiation What Ships? Architectural & Service “Blueprints” (Planning Information) Since your requirements will be different, your instantiation will be different

10. MSA Assists in Consolidation Projects Plan Build Deploy Evaluate Operate • Evaluate • Assess Current Infrastructure • Identify Goals • Plan • Design New Environment • Plan Migration • Build • Build, Test, Implement Pilot • Plan User/Data Migration • Deploy • Implement Production • Migration Users/Data • Evaluate and Review • Operate • Operations Partners

11. Key Tradeoffs • Less physical devices to manage • Potential cost savings in hardware, software, and support • Simpler solution that will enable managed growth • Isolation of services • For security or administrative reasons • Incompatibilities with other services • Servers belong to separate departmental budgets • Different SLA requirements for applications • Business Need to locate resources closer to the users • Political Pressure that is insurmountable

12. Key Scenarios – Branch Office Branch Office Consolidation of some services from multiple branch offices to a central office, leveraging increased bandwidth availability Branch Office Centralized Facility Branch Office EDC 1.5 & MSA 2.0

13. Scenario - Switch Consolidation Consolidation of multiple switches to centralized multi-blade switches EDC 1.5 & MSA 2.0

14. Windows NT 4.0 File And Print Server Consolidation Consolidation of multiple file and/or print servers to higher-end servers running Windows Server 2003 EDC 1.5 & MSA 2.0

15. Windows NT 4.0 Domain Consolidation Consolidation of multiple Windows NT 4.0 domains to less or a single domain running Windows Server 2003 Active Directory EDC 1.5 & MSA 2.0

16. SQL Server Consolidation Consolidation of multiple data stores to centralized SAN storage using Windows 2000 and Server 2003 Data Center Server and Unisys ES7000 EDC 1.5 & MSA 2.0

17. Exchange 5.5 +2000 Consolidation Consolidation of multiple Exchange Servers to less Exchange 2003 servers running multiple databases Microsoft is doing this worldwide on our internal infrastructure EDC 1.5

18. Technology Enablers Improved, lower cost network bandwidth Gradually Reducing cost Nearly Ubiquitous in Europe Increasingly Reliable with strong SLAs Highly Available High capacity Extensible storage capacity Storage Area Network Network Devices Higher speed and port density Layer 2 and 3 switches Windows Advanced & Datacenter Server Support for 8 partitions Scale: 32 processors, 64GB Memory Workload Management Windows Powered NAS Terabytes of Storage Snapshot backup and Replication for data availability Storage scalability with DFS

19. Technology Enablers Exchange 2003 Unlimited storage/multiple databases Excellent Clustering support on WS2003-EE AD Unifies enterprise administration SQL Server 2000 Support for up to 16 instances in SQL 64GB RAM/32 CPUs, failover clustering No single point of failure Windows Server 2003 Better Performance, more scaleable and secure Features designed to enable consolidation scenarios

20. Partners Are Key To MSA • Extend the MSA guidance • Adapt MSA guidance for globalization • System Integrators • Language • Hardware • Cover Scenarios that are tailored to their specific markets using MSA as base • Open invitation to all partners – hardware, software, services to join programme

21. The Unisys Enterprise RoadmapUnisys adds value to the MSA baseline • Consolidation – • From 74 servers to 46 to 2 • From 74 instances of the operating system to 46 to 40 • Disaster Recovery – global site load balancing, geographic clustering and fail over • Extended applications testing – Microsoft Exchange, Business Intelligence, OLTP database • Secure heterogeneous consolidation tier – Exchange, SQL, ISV applications • Single console management – servers, applications, OS (Sentinal) • End-to-end services – business blueprints, applications development, infrastructure planning, and implementation

22. The BIG Picture

23. Unisys MSA 1.5 ConsolidationConsolidation Using PCI Blade Appliance • Server on a PCI card • Intel Pentium III 700 MHz processor • 512MB, 1GB or 2GB memory • Low environmental requirements • 1 - 3 network connections 10/100/1000 (Ethernet over PCI Gigabit ) • Shares ES7000 disk resources • High availability (RAID or SAN over PCI support) • Simplified management • Consistency of software

24. Unisys MSA 1.5 ConsolidationHeterogeneous Application Consolidation • Consolidated Applications and Services • Exchange • 16,000+ Users per site • GeoClustered for HA/DR • BizTalk • GeoClustered for HA/DR • File and Print • GeoClustered for HA/DR • SQL • Single Instance supporting BizTalk and Analysis Services DBs • GeoClustered for HA/DR • Internet Information Server (IIS) and Commerce Server 2000 • DHCP • 2 local site clusters with split address range scopes

25. Unisys MSA 1.5 ConsolidationSQL Server 2000 Consolidation • One instance of Windows 2000 DC • 6 SQL Instances • Instance 1 – OLTP • 1TB DB Size • 1000’s of transactions a second • Instance 2 – Business Intelligence • 2TB DB Size • Instance 3 – Analysis Services • Multiple 280GB Cubes • Instances 4, 5, 6 – Database Consolidation • 36 DB’s per Instance • DB sizes from 100MB to 35GB • All 6 SQL Instances are GeoClustered for HA/BC • 200KM Distance with real fibre – no simulation • Synchronous SRDF replication

26. Site 1 – Server 1

27. Site 2 – Server 1

28. Site 1 – Server 2

29. Site 1 – Server 2

30. Consolidation Tools • Application Asset Manager (AAM): Process Discovery and Analysis • Agent invoked to non-invasively discover running databases, applications, associated dependencies and performance characteristics on standalone servers • Validates runtime applications revision levels and system resource utilization • Generates reports that highlight opportunities for application/database consolidation and application co-existence • Consolidated Server Sizer (CS Sizer) • Provides an automated means to estimate system component/configuration requirements • Facilitates the definition of systems, partitions, and workloads in order to arrive at an estimate of system configuration • Addresses sizing issues for several types of business needs

31. Allenbrook Aurum/Miser BEA WebLogics Biztalk Business Objects Cold Fusion Commerce Server Compass Cool ICE Crystal Reports CSS DEPCON DMR/Maximus Eastern EasyPhone Entelagent Erisco (Healthcare app) Exchange File/Print Services IIS Dedicated Consolidation Engineering • Engineering team dedicated to consolidation solutions: • Pre-testing applications and developing best practices, sizing and configuration guidelines, storage configuration guidelines, optimization practices, technology integration practices, etc. • INSCI • J.D. Edwards • Potomac • Lotus Domino • NetIQ • Norton Anti-Virus • PeopleSoft • Proclarity • PTFS • R2K • Remedy • RightFax • SAP • SAS • Siebel • SQL 6.5, 7.0, 2000 • SQL Analysis Services • Telnet 3270 • Terminal Services • Trend Micro Antivirus • XML 3.0

32. Exchange 2000 Server • General Considerations • Memory limitations • Storage Group and Mailbox Store hierarchy • Clustering • Failing to an active node: NOT RECOMMENDED • Keep SG limitation in mind when planning! • Tuning and Performance • Disk Cache Usage • Disk Layout Planning • Database Cache • See http://www.microsoft.com/exchange/techinfo/deployment/2000/e2ksp2_cluster.asp for detailed deployment info

33. SQL Server 2000 • Take advantage of SQL Server’s built-in processor affinity • Set each SQL Server instance’s Maximum memory limit so that memory is left for other applications • AWE and SQL Server • See http://ntlab.unisys.com/cmpguide/oltpsql.htm for more deployment guidelines

34. BizTalk Server 2000 • Dedicate a separate SQL Server instance to BizTalk, especially when in a cluster • If clustered, put SQL Server, MSDTC, and BizTalk all in same cluster group • Or change registry to set dependencies • See: http://www.microsoft.com/biztalk/techinfo/deployment/2000/DeplyCon.doc for more deployment guidelines

35. Resources Available today We welcome your feedback, E-Mail your comments to msafdbk@microsoft.com • MSA EDC 1.5 • MSA IDC 1.5 • MSA 2.0 Technical Preview Links:At http://www.microsoft.com/systemsarchitectureIn Technet, under IT SolutionsAt Unisyse-mail: david.l.jones@unisys.comhttp://unisys.com/products/es7000__servers/hardware/microsoft__systems__architecture__/index.htm

36. Ask The ExpertsGet Your Questions Answered • Talk one-on-one with a community of your peers • Community Experts: Microsoft product teams, consultants, and Tech*Ed speakers • Resources: Whiteboards, Internet, etc. • Location: In the middle of the Exhibit Hall • Hours: At least 12-3:30 P.M. every day Fred and David will be available in the ATE area after this session

37. Community Resources • Community Resources http://www.microsoft.com/communities/default.mspx • Most Valuable Professional (MVP) http://www.mvp.support.microsoft.com/ • Newsgroups Converse online with Microsoft Newsgroups, including Worldwide http://www.microsoft.com/communities/newsgroups/default.mspx • User Groups Meet and learn with your peers http://www.microsoft.com/communities/usergroups/default.mspx

38. evaluations

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