1 / 38

Windows Server 2008 for SAP Customers

Windows Server 2008 for SAP Customers . Josef Stelzel Technical Evangelist Microsoft Corporation www.microsoft-sap.com. Agenda. What’s New in Windows Server ® 2008. Windows Server ® Hyper-V. Microsoft ® Cluster Server and Availability. (Source: Accenture et al.).

gryta
Download Presentation

Windows Server 2008 for SAP Customers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Windows Server 2008 for SAP Customers Josef Stelzel Technical Evangelist Microsoft Corporation www.microsoft-sap.com

  2. Agenda • What’s New in Windows Server® 2008 • Windows Server® Hyper-V • Microsoft® Cluster Server and Availability (Source: Accenture et al.)

  3. What’s New in Windows Server 2008

  4. TCO as a Decision Factor • Total cost of ownership (TCO) is under pressure – administrative and management costs associated with IT are gaining with the increasing number of physical or virtual servers used. The cost of server administration and management is growing four times as fast as annual server spending. • The number of servers a single administrator manages has grown between Windows NT 4.0 and Windows Server 2003 from about 15 to 45.

  5. Spend Less Time on Everyday Tasks Enhanced scripting and task automation More Control Web server management Windows PowerShell™ Internet Information Services (IIS) 7.0 Configuration and role management Policy-based networking Windows Server Manager, Server Core Windows® Firewall

  6. More Design Goals for Windows Server 2008 • Businesses are becoming more decentralized; subsequently, more employees work from remote locations. At the same time, requirements of the applications (ESA) are driving the interconnection of business applications across companies. These facts cause: • De-perimeterization of the network • Management of guests, vendors, and partners on the network • Extranet access to corporate applications and data • Explosive growth of mobile devices, which are managed by Active Directory®

  7. Enhanced clustering capabilities for high availability Enhanced security for mission-critical applications Improved identity and access management Enhanced Storage functionality for reliability Easy deployment for SAP landscapes Virtualization for flexible resource management Better integration and manageability Centralized access to applications Overall Value for SAP Infrastructures Storage management Identity and access management Availability Connectivity Deployment Resource management Security and policies Server administration

  8. Windows Server Core • Windows Server is frequently deployed for a single role • Must deploy and service the entire operating system in earlier Windows Server releases • Server Core is a new minimal installation option • Provides essential server functionality • Command Line Interface (CLI) only, no GUI Shell • Benefits • Fundamentally improves availability • Less code results in fewer patches and reduced servicing burden • Low surface area server for targeted roles • More secure and reliable with less management

  9. Windows Server Core GUI

  10. Windows Server Hyper-V Windows Server Virtualization

  11. Consolidation as TCO Improvement • Other driving factors for TCO are environmental factors such as power and cooling. Nearly half of every dollar for server spending today goes for power and cooling. The expectation is 70 percent for 2010. Typical answers are consolidation and improvements in server technology. • Another required feature is more flexibility to respond in the datacenter to the requirements of the business. Virtualization in general is capable of delivering this value.

  12. VirtualHard Disks (VHD) Windows Server Virtualization Greater Flexibility • Greater scalability and improved performance • x64 bit host and guest support • SMP support • Increased reliability and security • Minimal trusted code base • Windows running a foundation role • Better flexibility and manageability • Configurablevirtual resources (memory, CPU, NIC) • Quick operating system / application migration • New UI/Integration with Microsoft® System Center Virtual Machine Manager 2007. VM 2“Child” VM 3“Child” VM 2 VM 3 VM 1“Parent” Microsoft® Virtual Server 2005 R2 Windows Server 2003 Hardware Windows Hypervisor AMD-V / Intel VT

  13. WSV Requirements and Features • Requirements • x64 hardware support • AMD-V or Intel VT (IVT)-enabled processors • High-level features • Hardware virtualization enabled • 32-bit and 64-bit guests • Large memory support (64 GB of memory per virtual machine) • Guest multiprocessing (Up to four core virtual machines) • Virtualized devices • WMI management and control API • Save/Restore, Snapshotting • CPU and I/O resource controls • Tuning for NUMA • Easy transition of Microsoft® Virtual Server VMs

  14. Support tools • Benchmark • Best practice • SAP support Support Customer Use cases Operation • Business continuity • Flexibility and adaptability • Hardware consolidation • Resource optimization • Hardware abstraction WSV Ramp Up Process for SAP • Availability of bits • Documentation • Product support • License solutions • Interoperability • Specs Product H/W Partner • Support • Performance • Backup/recovery • High availability • Landscape design • Patching and security • Deployment and provisioning • Monitoring and administration Integration 14

  15. Business Continuance Utilization Server Consolidation Use Cases for Windows Server Virtualization Flexibility

  16. Virtual Machine Manager Arrangements Type-2 VMM Hybrid VMM Type-1 VMM(Hypervisor & Virtualization Stack=VMM) Guest 1 Guest 2 VMM Guest 1 Guest 2 Guest 1 Guest 2 Host OS Host OS VMM VMM Hardware Hardware Hardware Examples: JVMCLR Examples: Virtual PC & Virtual Server Examples: Windows Virtualization What we have today What we’re buildingfor the future

  17. The Hypervisor • Very thin layer of software • Highly reliable • Much smaller Trusted Computing Base (TCB) • No built-in driver model • Leverage the large base of Windows drivers • Will have a well-defined, published interface • Allow others to create support for their operating systems as guests • Hardware virtualization assists are required • Intel Virtualization Technology • AMD “Pacifica” or AMD-V

  18. Drivers Drivers Drivers Drivers Drivers Drivers Drivers Drivers Drivers Drivers Drivers Drivers Monolithic vs. Microkernelized • Microkernelized hypervisor • Simple partitioning functionality • Increase reliability and minimize TCB • No third-party code • Drivers run within guests • Monolithic hypervisor • Simpler than a modern kernel, but still complex • Contains its own drivers model VM 1 (“Admin”) VM 2 VM 3 VM 2 (“Child”) VM 3 (“Child”) VM 1(“Parent”) Virtual- ization Stack Hypervisor Hypervisor Hardware Hardware

  19. Virtualization Interoperability • Virtual Hard Disk (VHD) • VHD specification is freely available under Open Specification Promise (OSP) • VHD TestDrive program • Licensed by XenSource • Standards-based management APIs • DMTF defining model for management • Hypervisorhypercall API • Preliminary documentation available • Final version will be licensed at release to manufacturing (RTM)

  20. Interoperability and Support for Linux • Working with XenSource • Developing adapter layer to map Xenhypercall API to Windows Server Virtualization hypercall API • Developing disk and networking drivers to integrate with the new I/O architecture • Working with Novell • Interoperability and joint support for Windows Server and Novel SUSE Linux Enterprise Server 10 • Support for Linux on Windows Server Virtualization

  21. Windows Server Licensing and Virtualization • Windows Server® 2008 Standard • One physical installation • Right for one virtualization installation • Windows Server® 2008 Enterprise • One physical installation • Right for four virtualization installations • Windows Server® 2008 Datacenter • One physical installation • Right for unlimited virtualization installations

  22. Virtualization and High Availability • Traditional non-virtualized environment • Downtime is bad, but affects only one workload • Virtualized environment • Value of the physical server goes up • Downtime is far worse because multiple workloads are affected Virtualization and high-availability go hand in hand

  23. Purpose of High Availability • Providing solutions for both planned and unplanned downtime • Planned downtime • Quickly move virtualized workloads to service underlying hardware • More common than unplanned • Unplanned downtime • Automatic failover to other nodes (hardware or power failure) • Not as common and more difficult

  24. Quick Migration • Available at Windows Server Virtualization RTM • For planned downtime • Quick Migration means a few seconds of downtime • Can be as little as three seconds to move a VM • Downtime depends on storage connectivity and VM memory size • For unplanned downtime • Quick Migration allows a restart of the virtual machine on another physical server

  25. Quick Migration Functional Overview • Save state • Save entire VM state • Move virtual machine • Move storage connectivity from origin to destination host • Restore state and run • Restore VM and run • Done VHDs SAN Storage Network Connectivity

  26. Quick Migration for Planned Downtime Virtualization Servers (3 + 1 Servers) • Active server requires service • Move virtualized workloads to a standby server • ~4 seconds of downtime per VM Domain Controller System Center Virtual Machine Manager Storage Connectivity VHDs on SAN Ethernet

  27. Quick Migration for Unplanned Downtime Virtualization Servers (3 + 1 Servers) • Active server loses power • Virtual machines automaticallyrestart on the next cluster node • If there is not enough memory, the failover automaticallymoves to the next node until done Domain Controller System Center Virtual Machine Manager Storage Connectivity VHDs on SAN Ethernet

  28. How Fast Is Quick Migration?

  29. 2008 2005 2006 Server Virtualization Road Map Windows Server Virtualization within 180 days of Windows Server 2008 RTM • Windows Server 2008 • System Center Virtual Machine Manager • Virtual Server 2005 R2 SP1 • Virtual Server 2005 R2 SP1 Beta • Virtual Server Microsoft® Operations Manager Management Pack R2 • System Center Virtual Machine Manager Beta • Virtual Server 2005 R2 • Virtual Server Operations Manager Management Pack

  30. Improvements in Microsoft Cluster Server

  31. Windows Cluster Configuration Today

  32. Windows Server 2008 Step 1

  33. Windows Server 2008 Step 2

  34. Windows Server 2008 Step 3 It’s that easy!

  35. Geographically Dispersed Clusters • No more single-subnet limitation • Allow cluster nodes to communicate across network routers • No more having to connect nodes with VLANs! • Configurable heartbeat timeouts • Increase to extend geographically dispersed clusters over greater distances • Decrease to detect failures faster and take recovery actions for quicker failover

  36. Review • What’s New in Windows Server 2008 • Windows Server Hyper-V • Microsoft Cluster Server and Availability (Source: Accenture et al.)

  37. Questions and Answers • Submit text questions using the “Ask” button. • Don’t forget to fill out the survey. • For upcoming and previously live webcasts: www.microsoft.com/webcast • Got webcast content ideas? Contact us at: http://go.microsoft.com/fwlink/?LinkId=41781

More Related