Windows Server 2008 R2 Feature Roadmap Clustering & High Availability Failover Clustering Network Load Balancing

1. Windows Server 2008 R2 Feature RoadmapClustering & High AvailabilityFailover Clustering Network Load Balancing

2. Agenda • Clustering Vision in Windows Server 2008 R2 • Validate Enhancements • Migrating to R2 • Improved Management • New Role Support • Cluster Shared Volumes & Hyper-V • Network Load Balancing

3. Clustering Goals in R2

4. Mix And Match Hardware • You can use anyhardware configuration if • Each component has a Windows Server 2008 R2 logo • Servers, Storage, HBAs, MPIO, DSMs, etc… • It passes Validate • It’s that simple! • Connect your Windows Server 2008 R2 logo’d hardware • Pass every test in Validate • It is now supported! • If you make a change, just re-run Validate • Details: http://go.microsoft.com/fwlink/?LinkID=119949

5. FCCP Failover Cluster Configuration Program • Windows Server 2008 R2 • Buy validated solutions • Microsoft recommends FCCP solutions • Not required for Microsoft support, must be logo’d • “Validated by Microsoft Failover Cluster Configuration Program” • More information: http://www.microsoft.com/windowsserver2008/en/us/clustering-program.aspx

6. Enhanced Validation • Cluster Validation Tool now includes additional “best practices” tests • Included automatically when Validation Tool is run on an existing cluster • Examples of best practices tests: • Quorum configuration • Status of cluster resources • Network Name settings in a multi-site cluster • Offers prescriptive guidance to achieve higher availability • Also collects information about the configuration for supportability and documentation

7. Migration – Our Upgrade Path • Built-in migration wizard • Supports most networking configurations • IPv4, IPv6, IPv6 tunnel, DHCP IPs, Static IPs, different subnets • Reuse storage or copy data and use new storage • Migrate resource groups between clusters • Enhanced Pre- and Post- migration reports • Guide: http://go.microsoft.com/fwlink/?LinkID=142796 2003 2008 R2 2008 2008 R2 2008 R2 2008 R2

8. Migration • Migrate every in-box workload • DFS-N, DHCP, DTC, File Server, Generic Application, Generic Script, Generic Service, iSNS, MSMQ, NFS, Other Server, Remote Desktop, WINS • All other workloads have their own cluster-aware upgrade process • DFS-R • Exchange • Hyper-V • Print • SQL • Everything has an upgrade path

9. "In Place Migration" – Reuse Hardware Migrate to me HA Apps HA Apps Cluster Cluster Cluster

10. PowerShell Support • Command line, scripting language, and programmatic interface • Improved manageability • Run Validate • Easily create clusters & HA roles • Manage Hyper-V and CSV • Generate dependency reports • Server Core, Hyper-V Server 2008 R2, & RSAT Client • Replaces cluster.exe as the cluster CLI tool

11. Read-Only Cluster Access • Cluster API read-only access • Reduced privileges • View the cluster • No action • Minimizes risk • Improved security • Useful for 1st tier support, cross-team collaboration, admins and investigation • Supported by PowerShell

12. Performance Counters • Troubleshoot Performance Problems • Monitor & Optimize Cluster Performance • Resources • Groups • CSV • API Calls • Handles • Service • Cluster DB • Network • More …

13. Enhanced Logging • Capture UI pop-ups & Messages • Even before cluster creation • New debug logging channels • Disabled by default • Enabled for advanced troubleshooting • Cluster.log converted to an ETW channel, now also appears in Event Viewer • Tip: Click on View  Show Analytic and Debug Logs

14. Monitoring Cluster Events • Save event query results as EVTX files • Failover Cluster Management Packs for: • System Center Operations Manager 2007 • http://go.microsoft.com/fwlink/?LinkID=147087 • Microsoft Operations Manager 2005

15. Network Enhancements • More resilient inter-node communication • Self-healing logic • Network prioritization for customizability • Plan your internal cluster networks • Helps enable CSV • Lower “metric” (cost), higher importance

16. HA Roles and Features • Common • Hyper-V • Exchange • File Server • Print • SQL • New for R2 • DFS-Replication • Remote Desktop • 3rd Party • Many different roles • Other • DFS-Namespace • DHCP • DTC • iSNS • MSMQ • NFS • WINS • Generic Containers • Generic Application • Generic Script • Generic Service • Other Server

17. DFS-Replication Cluster Support • High availability of data using clustered DFS-R without having a redundant copy • Tight integration with DFS-R management tools • Multi-Master Replication Engine • Any replication group (RG) member can form its own cluster • Replicate to other RG members NOT in the cluster • All members of the RG can form an independent Failover Cluster

18. Remote Desktop Failover Cluster Redundant Connection Broker Connection Broker Server Farm VHD

19. Remote Desktop • Remote Desktop Connection Broker • Keep clients connected in server farms • Local VHD location • TS / RDS Sessions • Load Balancing

20. Print Server HA Improvements • Print drivers and processors are now isolated and run in independent process from spooler process • Each Print Spooler cluster resource runs it’s own sandbox • Configurable granularity • Drivers can be set to run in their own sandbox • Periodic recycling of sandboxes • Helps mitigate leaky drivers Key Takeaway: Single bad driver no longer takes down entire print server!

21. The Virtual Datacenter Vision • Virtualize your workloads • Consolidate Servers • Reduce Costs • Space/facilities • Cooling • Physical Hardware • Maintenance • Smaller OS footprint • Easier Management • HW Flexibility • Quicker Installations / Deployments • Legacy OS / Apps • Incompatible Apps on same server • “We’ve reached a point of virtualization awareness where customers clearly understand the risk of single point of failure and the importance of employing a high availability solution. To that end, we see almost 100% adoption of Failover Clustering  with Hyper-V in production environments.” • -Jeff Woolsey, Senior Program Manager Lead, Virtualization, Microsoft

22. What is Live Migration? • Move a running Virtual Machine from one computer to another computer with no perceived downtime for the VM • VM is not aware of the migration • Maintain TCP connections of the guest OS • Building block for virtual data center through business agility, cost reduction and increase in productivity • Clients stay connected • How is it different from Quick Migration? • VM is saved and restored on destination • Results in downtime for applications/workloads running inside VMs • Both leverage same storage infrastructure – easy to move from QM to LM • Guide: http://technet.microsoft.com/en-us/library/dd446679.aspx • Whitepaper: http://www.microsoft.com/downloads/details.aspx?FamilyID=fdd083c6-3fc7-470b-8569-7e6a19fb0fdf&displaylang=en

23. Live Migration Entire VM memory copied Memory content is copied to new server Live Migrate SAN May be additional incremental data copies until data on both nodes is essentially identical VHD

24. Live Migration Session state is maintained No reconnections necessary Clients stay connected to “live” VM Client directed to new host SAN ARP issued to point routing devices to new node Old VM deleted after success VHD

25. Failover Clustering Today • Failover Clustering has implemented a “shared nothing” storage model for the last decade • Placing VHDs on same volume or LUN requires that VMs run on same host cluster node Only one node accesses a LUN at a time SAN SAN

26. SAN Management Complexity

27. Delivering Innovation

28. Cluster Shared Volume Overview Concurrent access to a single file system Single Volume SAN Disk5 VHD VHD VHD

29. CSV Compatibility • CSV is fully compatible with what you have deployed today in Windows Server 2008! • No special hardware requirements • Same requirements as standard cluster disk • iSCSI, Fibre Channel, SAS • No file type restrictions • No directory structure or depth limitations • No special agents or additional installations • No proprietary file system • Uses well established traditional NTFS • Simple migrations to CSV

30. CSV Benefits • Easier Storage Management • Individual VMs can failover from a shared LUN • Optimized Capacity Planning • VMs use shared pool of free space • Improved Performance • Dynamic I/O Redirection • Network Prioritization • Higher Availability • Node Fault Tolerance • Network Fault Tolerance • SAN Fault Tolerance • Lower Total Cost of Ownership 99.9% 99.99% Availability 99% 99.999%

31. Independent VM Failover VMs running on Node 1 are unaffected SAN Node owns the CSV disk (Coordinator Node) Same LUN VHD 2 VHD 3 VHD 1

32. I/O Connectivity Fault Tolerance I/O Redirected via network VM running on Node 2 is unaffected Coordination Node SAN Connectivity Failure SAN VM’s can then be live migrated to another node with zero client downtime VHD

33. Optimized Capacity Planning • 1 LUN for many VMs • VM smallest unit of failover • VMs share the pool of unused space • Flexible utilization and easy management Free Space Used VHD Space Free Space VHD VHD VHD VHD VHD VHD VHD VHD VHD VHD VHD

34. NLB Enhancements • Full PowerShell support • Create/destroy clusters • Add/remove/control cluster nodes • Add/edit/remove cluster VIPs and node DIPs • Replacing NLB.exe as the command line tool • NLB support for Direct Access servers • Health Awareness • Extended Affinity

35. NLB Health Awareness • Application health awareness for IIS • System Center Operations Manager 2007 • Windows Server 2008 NLB Management Pack

36. Extended Affinity • Longer affinity between client and cluster node • Admin-specified timeout for connection state • Updating the NLB configuration now maintains affinity • Scenarios: • Universal Access Gateway (UAG) – SSL VPN • IIS and ASP.NET

37. Session Summary • Windows Server 2008 R2 Failover Clustering is delivering substantial value • Hyper-V deployments will want to upgrade immediately • Expanded support for several new roles • No special requirements – it just works Innovation Manageability Supportability • Cluster Shared Volumes • Live Migration • PowerShell • Migration • Improved integration with Cluster Management UI • Improved Logging • Enhanced Validation • Performance Counters

38. Resources Cluster Team Blog: http://blogs.msdn.com/clustering/ Cluster Information Portal:http://www.microsoft.com/windowsserver2008/en/us/clustering-home.aspx Clustering Technical Resources: http://www.microsoft.com/windowsserver2008/en/us/clustering-resources.aspx Clustering Forum (2008): http://forums.technet.microsoft.com/en-US/winserverClustering/threads/ Clustering Forum (2008 R2): http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2highavailability/threads/ Clustering Newsgroup: https://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.clustering Failover Clustering Deployment Guide: http://technet.microsoft.com/en-us/library/dd197477.aspx TechNet: Configure a Service or Application for High Availability: http://technet.microsoft.com/en-us/library/cc732478.aspx TechNet: Installing a Failover Cluster: http://technet.microsoft.com/en-us/library/cc772178.aspx TechNet: Creating a Failover Cluster: http://technet.microsoft.com/en-us/library/cc755009.aspx Webcast (2008 R2): Introduction to Failover Clustering: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032407190&Culture=en-US Webcast (2008 R2): HA Basics with Hyper-V: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032407222&Culture=en-US Webcast (2008 R2): Cluster Shared Volumes (CSV): http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032407238&Culture=en-US

39. Q & A

40. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.