Presentation is loading. Please wait.

Presentation is loading. Please wait.

Symon Perriman Program Manager Microsoft Corporation WSV316.

Similar presentations


Presentation on theme: "Symon Perriman Program Manager Microsoft Corporation WSV316."— Presentation transcript:

1

2 Symon Perriman Program Manager Microsoft Corporation WSV316

3 Multi-Site Clustering Benefits Deployment Replication Networking Faster Failover Quorum Best Practices

4 Benefits of a Multi-Site Cluster Protects Against Loss of an Entire Datacenter Power outage, fires, hurricanes, floods, earthquakes, terrorism Automates Failover Reduced downtime Lower complexity of disaster recovery plan Reduces Administrative Overhead Automatically synchronize application and cluster changes Easier to keep consistent than unclustered servers What is the primary reason why disaster recovery solutions fail? Dependence on People

5 Multi-Site Clustering Checklist Organized multi-site cluster deployment guide

6 Multi-Site Clustering Benefits Deployment Replication Networking Faster Failover Quorum Best Practices

7 Site B Multi-Site Clustering Basics 2+ physically separate sites 1+ node at each site Storage at each site with data replication Application moves during a failover Site A SANSANSANSAN

8 Redundancy Everywhere 2 or more computers (nodes) 2 NICs 3rd NIC for iSCSI HBA Fibre Channel (FC) Serial Attached-SCSI (SAS) Multipath IO (MPIO) Redundant Storage Interconnects Replicated Storage OS, Service or Application HA Roles

9 Mix and Match Hardware You Can Use Any Hardware Configuration if Each component has a Windows Server 2008 / R2 logo Servers, Storage, HBAs, MPIO, 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 run Validate again Details:

10 FCCP Failover Cluster Configuration Program Windows Server 2008 / R2 Buy validated solutions “Validated by Microsoft Failover Cluster Configuration Program” Not required for Microsoft support, must be logo’d More information: g-program.aspx g-program.aspx

11 Introduction to Multi-Site Clustering

12 Cluster Validation and Replication Multi-Site clusters are not required to pass the Storage tests to be supported Validation guide and policy: fwlink/?LinkID=119949

13 Multi-Site Clustering Benefits Deployment Replication Networking Faster Failover Quorum Best Practices

14 Why is Replication Needed? Loss of a site won’t cause complete data loss Data must exist on other site after a failover Different storage needs than local clusters Multiple storage arrays, independent on each site Nodes usually access local site’s storage first Site A Changes are made on Site A and replicated to Site B Site B ReplicaReplica

15 Replication Solutions Replication Levels Hardware (block level) storage-based replication Software (file system level) host-based replication Application-based replication Exchange Server 2007 CCR Replication Types Synchronous Asynchronous A data replication mechanism between sites is needed

16 Synchronous Replication Host receives “write complete” response from the storage after the data is successfully written on both storage devices Primary Storage Secondary Storage Write Complete Replication Acknowledgement Write Request

17 Asynchronous Replication Host receives “write complete” response from the storage after the data is successfully written to the primary storage device Primary Storage Secondary Storage Write Complete Replication Write Request

18 Synchronous vs. Asynchronous

19 What About DFS-Replication? DFS-R performs replication on file close Some file types stay open for a very long time VHDs for Virtual Machines Databases for SQL Server Data could be lost during a failover if it had not yet replicated Using DFS-R to replicate the cluster disk’s data in a multi-site Failover Cluster is not supported

20 Disk Resource Resource Group Custom Resource (manages replication) IP Address Resources* Network Name Resource Establishes start order timing Group determines smallest unit of failover Resource Dependencies Workload Resource (example File Server) “ depends on ”

21 Multi-Site Clustering Benefits Deployment Replication Networking Faster Failover Quorum Best Practices

22 Site B Network Considerations Cluster nodes can reside in different subnets (2008/R2) No need to connect nodes with VLANs Site A Public Network Separate Network

23 Stretching the Network Longer distance means greater network latency Too many missed health checks can cause false failover Fully configurable in 2008/R2 Failover Clustering has NO DISTANCE & NO SUBNET LIMITATIONS Check if your vendor’s hardware / replication has limitations SameSubnetDelay (default = 1 second) Frequency heartbeats are sent SameSubnetThreshold (default = 5 heartbeats) Missed heartbeats before an interface is considered down CrossSubnetDelay (default = 1 second) Frequency heartbeats are sent to nodes on dissimilar subnets CrossSubnetThreshold (default = 5 heartbeats) Missed heartbeats before an interface is considered down to nodes on dissimilar subnets Command Line: Cluster.exe /prop PowerShell (R2): Get-Cluster | fl *

24 Security Over the WAN Improved Security Prevent Clients from Connecting to Networks Encrypt Intra-cluster Traffic 0 = clear text 1 = signed (default) 2 = encrypted

25 IP Address Resource B IP Address Resource A Enhanced Dependencies – OR Network Name resource stays up if either IP Address Resource A OR IP Address Resource B is up Network Name Resource OROR

26 Disk Resource Workload Resource (example File Server) IP Address Resources A Network Name Resource Resource Dependencies IP Address Resources B Comes online on site A Comes online on site B OROR Custom App (replication)

27 Multi-Site Clustering Benefits Deployment Replication Networking Faster Failover Quorum Best Practices

28 DNS Updates Nodes in dissimilar subnets Failover changes resource’s IP Address Clients need that new IP Address from DNS to reconnect DNS Server 1 DNS Server 2 DNS Replication Record Updated Record Created Record Obtained FS = Record Updated FS = Site A Site B

29 Network Name Properties RegisterAllProvidersIP (default = 0 for FALSE) Determines if all IP Addresses for a Network Name will be registered by DNS TRUE (1): IP Addresses can be online or offline and will still be registered Ensure application is set to try all IP Addresses, so clients can come online quicker HostRecordTTL (default = 1200 seconds) Controls time the DNS record lives on client for a cluster network name Shorter TTL: DNS records for clients updated sooner Exchange Server 2007 recommends a value of five minutes (300 seconds)

30 Local Failover First Local failover first No change in IP Address Cross-site failover for disaster recovery DNS Server 1 DNS Server 2 FS = Site A Site B FS =

31 Failover Order Preferred Owners Local failover first Possible Owners Always Enforced Resource will not start on non-possible owner AntiAffinityClassNames Groups with same AACN try to avoid moving to same node library/aa369651(VS.85).aspx

32 Virtual LAN (VLAN) Deploying a VLAN minimizes client reconnection times Can be harder to configure Required for SQL & live migration DNS Server 1 DNS Server 2 FS = Site A Site B VLAN

33 Multi-Site Clustering Groups and Settings

34 Multi-Site Clustering Benefits Deployment Replication Networking Faster Failover Quorum Best Practices

35 Quorum Overview Node majority Node and File Share majority Disk only (not recommended) Node and Disk majority Vote Majority is greater than 50% Possible Voters: Nodes (1 each), Disk Witness (1 max), File Share Witness (1 max) 4 Quorum Types

36 Node and Disk Majority Nodes get 1 vote each and Disk gets vote Loss of disk or node OK if majority is maintained Do not use in multi-site clusters unless directed by vendor Vote Replicated Storage from vendor ?

37 Node Majority Site B Site A Cross site network connectivity broken! Can I communicate with majority of the nodes in the cluster? Yes, then Stay Up Can I communicate with majority of the nodes in the cluster? Yes, then Stay Up Can I communicate with majority of the nodes in the cluster? No, drop out of Cluster Membership Can I communicate with majority of the nodes in the cluster? No, drop out of Cluster Membership 5 Node Cluster: Majority = 3 SAN Majority in Primary Site

38 Node Majority Site B Site A Disaster at Site 1 We are down! Can I communicate with majority of the nodes in the cluster? No, drop out of Cluster Membership Can I communicate with majority of the nodes in the cluster? No, drop out of Cluster Membership SAN Majority in Primary Site 5 Node Cluster: Majority = 3

39 Forcing Quorum Always understand why quorum was lost Used to bring cluster online without quorum Cluster starts in a special “forced” state Once majority achieved, no more “forced” state Command line: net start clussvc /forcequorum (or /fq) PowerShell (R2): Start-ClusterNode –FixQuorum (or –fq)

40 Site A Multi-Site With File Share Witness Site B WAN Site C SANSAN SANSAN \\Foo\Cluster1 Complete resiliency and automatic recovery from the loss of any 1 site File Share Witness Replicated Storage from vendor

41 WAN Site A Multi-Site With File Share Witness Site B Site C SANSAN SANSAN Complete resiliency and automatic recovery from the loss of any 1 site File Share Witness Replicated Storage from vendor \\Foo\Cluster1

42 WAN Site A Multi-Site With File Share Witness Site B Site C SANSAN SANSAN Complete resiliency and automatic recovery from the loss of the File Share Witness File Share Witness Replicated Storage from vendor \\Foo\Cluster1

43 FSW Considerations Simple Windows File Server Needs to be in the same forest Running Windows Server® 2003, 2008 or 2008 R2 Recommended to be at 3rd separate site Single file server can serve as a witness for multiple clusters Each cluster requires its own share Can be clustered in a second cluster FSW cannot be on a node in the same cluster It is an additional voter for free (almost)

44 Quorum on a Multi-Site Cluster

45 Quorum Model Summary No Majority: Disk Only Note Recommended Only use as directed by vendor Node and Disk Majority Only use as directed by vendor Node Majority Odd number of nodes Node and File Share Majority Best availability solution Recommended for Exchange Server 2007 CCR

46 Multi-Site Clustering Benefits Deployment Replication Networking Faster Failover Quorum Best Practices

47 Cluster your Branch Offices Cluster several standalone File Servers from branch offices Keep network traffic low High-Availability for the files Redundancy for the data Site B Site A Clients primarily accessing applications in Site A Clients primarily accessing applications in Site B

48 Multi-Site Across the Enterprise More distributed cluster nodes & clusters gives higher availability Complete resiliency and automatic failover Remember your quorum model Loss of any single site should not bring down the cluster File Share Witness 1 File Server hosts all File Share Witnesses for multiple clusters Make it highly-available Separate site Not a node in that same cluster Cluster 1, Site 1 Cluster 2, Branch 1 Cluster 2, Main Office Cluster 2, Branch 2 Cluster 1, Site 2 Cluster 3, Many FSWs

49 WAN Site A Multi-Site Clustering Review Site B Site C SANSAN SANSAN 4, 6, 8… nodes + FSW = odd # votes Local failover first (preferred owner) Site failover second (possible owner) AntiAffinityClassNames File Share Witness Replicated Storage from vendor Faster DNS Updates Register all IPs for a Network Name Shorten client’s DNS record TTL Ensure application tries all IPs Encrypt WAN traffic for security Adjust health checks for latency Configure ‘OR’ dependencies

50 Session Summary Multi-Site Failover Clustering has many benefits Variety of hardware options & configurations Redundancy is needed everywhere Understand your replication needs Compare VLANs with multiple subnets Plan your quorum model & nodes before deployment Follow the checklist and best practices

51 Become a Cluster MVP! Passion for High Availability?

52

53 Sessions On-Demand & Community Resources for IT Professionals Resources for Developers Microsoft Certification and Training Resources Microsoft Certification & Training Resources Resources Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online.

54 Related Content Breakout Sessions WSV310 Failover Clustering Feature Roadmap for Windows Server 2008 R2 WSV313 Innovating High Availability with Cluster Shared Volumes (CSV) WSV316 Multi-Site Clustering with Windows Server 2008 Enterprise VIR311 From Zero to Live Migration. How to Set Up a Live Migration DAT302 All You Need to Know about Microsoft SQL Server 2008 Failover Clusters DAT306 Building a HA Strategy for Your Enterprise Using Microsoft SQL Server 2008 DAT322 Tips and Tricks for Successful Database Mirroring Deployments with Microsoft SQL Server WSV311 High Availability and Disaster Recovery Considerations for Hyper-V WSV315 Implementing Hyper-V on Clusters (High Availability) UNC313 High Availability in Microsoft Exchange Server "14" UNC402 Microsoft Exchange Server 2007 HA and Disaster Recovery Deep Dive BOF52 Microsoft Exchange Server 2007 HA and Disaster Recovery: Are You Prepared? Interactive Sessions WSV01-INT Failover Clustering Unleashed with Windows Server 2008 R2 UNC02-INT Designing Microsoft Exchange Server "14" High Availability Solutions Hands on Labs WSV16-HOL Windows Server 2008 R2: Failover Clustering VIR03-HOL Implementing Windows Server 2008 Hyper-V HA and Quick Migration DAT12-HOL Microsoft SQL Server 2008 Database Mirroring, Part 1 DAT13-HOL Microsoft SQL Server 2008 Database Mirroring, Part 2 UNC12-HOL Microsoft Exchange Server "14" High Availability and Storage Scenarios

55 Track Resources Cluster Team Blog: Cluster Information Portal: Clustering Technical Resources: Clustering Forum (2008): Clustering Forum (2008 R2): US/windowsserver2008r2highavailability/threads/ US/windowsserver2008r2highavailability/threads/http://social.technet.microsoft.com/Forums/en- US/windowsserver2008r2highavailability/threads/ Clustering Newsgroup: us/default.aspx?dg=microsoft.public.windows.server.clustering us/default.aspx?dg=microsoft.public.windows.server.clusteringhttp://www.microsoft.com/communities/newsgroups/list/en- us/default.aspx?dg=microsoft.public.windows.server.clustering Failover Clustering Deployment Guide: TechNet: Configure a Service or Application for High Availability: TechNet: Installing a Failover Cluster: TechNet: Creating a Failover Cluster: Webcast (2008 R2): Introduction to Failover Clustering: Webcast (2008 R2): HA Basics with Hyper-V: Webcast (2008 R2): Cluster Shared Volumes (CSV):

56 Windows Server Resources Make sure you pick up your copy of Windows Server 2008 R2 RC from the Materials Distribution Counter Learn More about Windows Server 2008 R2: Technical Learning Center (Orange Section): Highlighting Windows Server 2008 and R2 technologies Over 15 booths and experts from Microsoft and our partners Over 15 booths and experts from Microsoft and our partners

57 Complete an evaluation on CommNet and enter to win!

58 © 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.


Download ppt "Symon Perriman Program Manager Microsoft Corporation WSV316."

Similar presentations


Ads by Google