1 / 33

Building a High Availability Strategy for Your Enterprise Using Microsoft SQL Server 2008 DAT301

Building a High Availability Strategy for Your Enterprise Using Microsoft SQL Server 2008 DAT301. Gopal Ashok Program Manager Microsoft Corp. 24x7 Global Business. Compliance. Growth. Revenue. What is this talk about?. Ensuring IT services and operational continuity in the enterprise

biana
Télécharger la présentation

Building a High Availability Strategy for Your Enterprise Using Microsoft SQL Server 2008 DAT301

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. Building a High Availability Strategy for Your Enterprise Using Microsoft SQL Server 2008DAT301 Gopal Ashok Program Manager Microsoft Corp

  2. 24x7 Global Business Compliance Growth Revenue

  3. What is this talk about? Ensuring IT services and operational continuity in the enterprise Protect mission critical SQL Server databases using Always On Technologies Deployments and Best Practices

  4. Defining HA and DR Recovery Time Objective (RTO) guided by availability requirements How much downtime can you tolerate? Recovery Point Objective (RPO) guided by criticality of application data How much data can you lose? • High availabilityis a system design protocol and associated implementation that ensures a certain absolute degree of operational continuity during a given measurement period • Disaster Recovery involves processes and procedures designed to restore business operations due to a natural or human-induced disaster • Typically involves providing redundancy spanning multiple sites or across geographic regions • Availability defined in terms of service level agreements (SLA) • Recovery Time • Data loss during unplanned downtime

  5. Protection Levels Regional DR Protection against resource failures • Machine • Database Corruption • Disk • Resource Bottlenecks Location Redundancy • Building • < 10 miles Geographic DR • Protection against • Natural Disasters • Location Redundancy • State, Country • > 100 miles Local HA • Protection against • Network Outages • Site Failures • Location Redundancy • City, County • < 100

  6. SQL Server High Availability Planning • Analysis • Application tiers serviced by the databases • Protection levels: Local HA, Regional DR, Geographic DR • Causes of database downtime • Solution Design • Need to understand what solutions exists? • What are the characteristics and cost of the solution? • Implementation • What are the deployment steps and best practices?

  7. Database Downtime Drivers

  8. Solution Design • Understand the available technology options and characteristics before making a decision

  9. Always On Technologies • Provides a full range of options to minimize operational downtime and maintain appropriate levels of application availability.

  10. Always On Solution Characteristics Redundancy and Utilization RPO Failover Cost * Database Mirroring and Log Shipping can provide point in time read capability using STANDBY or database snapshots respectively ** Database Mirroring provides fastest failover to hot secondary *** Depends on SAN technology

  11. Increasing Availability: ServiceU • Unplanned downtime: • Loss of a database server: • RPO = 0; that is, no data loss • RTO = 60 seconds maximum • Loss of the primary data center, or the entire database storage unit in the primary data center: • RPO = 3 minutes maximum; • RTO = 15 minutes total, including evaluation of the issue; • Planned downtime: • RPO = 0 (no data loss) • RTO = 60 seconds maximum; some database changes may require a longer downtime than 60 seconds; in those cases every effort is made to minimize the service interruption Provide solutions for reserved seat ticketing, box office management, event management and online Payments No Service = No Revenue

  12. ServiceU High Availability Architecture • Basic Principle: Redundancy for all components • 3-node cluster • Redundancy during single node failure, patching etc • No Majority: Disk Only Quorum Model • Availability during multi-node failure • No automatic failback to preferred node

  13. ServiceU Disaster Recovery Architecture

  14. demo Using Log Shipping to setup Mirroring

  15. Upgrading to SQL Server 2008 • Windows Server 2003\SQL Server 2005 • Upgraded both OS and SQL Server to 2008 • Had to do this with very little downtime • How much? Let’s find out!!!!

  16. Primary Site Upgrade Process • Application Switch Over to temp cluster • Block users • Sync mirroring • DBM Failover • Redirection • Remove DBM Establish async DBM from 2005 to 2008 • Total end user down-time • 10 minutes • Upgraded primary cluster to 2008 • Repeated steps above • Downtime 6 minutes Temporary SQL Server 2008 Cluster On Windows Server 2008

  17. Windows Server 2008 & SQL Server 2008 Better Together Database Mirroring Automatic recovery from page corruption Log stream compression Faster recovery on failover Log Shipping Sub-Minute Log Shipping Backup compression Replication Peer-Peer Replication: Hot add new nodes Improved performance over WAN links • Failover Clustering • Rolling upgrade and patching • 16 nodes • Resource Governor • Manage SQL Server workloads and resources by specifying limits on resource consumption • Backup Compression • Reduce backup and restore time

  18. Database Mirroring Compression Benefit Cost

  19. demo Automatic Page Repair

  20. Rolling upgrade using Mirroring

  21. Failure is not an option: bWin • Environment • 100+ TB Data • 850+ DB’s • 100 Instances • 450K SQL Statements\Sec • Sports betting, Soft & skill games • 1 million bets per day on > 90 Sports • The Mission: • Failure is not an option & Money is not a problem • Rather lose availability and performance than data

  22. bWin High Availability Architecture • Principal: 32 IA64 Dual Core CPU’s   • Mirror 32: IA64 Single Core • 64 Network Ports (1 Gbps) • 400 local SAS drives on 16 • RAID controllers (for OS, TempDB and Log files – low latency) • 16 HBA’s for 256 Disk / 256GB cache SAN system

  23. Scale Out and Availability Scenario • Requirements • Geo Redundancy • Data Locality • High Availability • Local Read-Scale • Workload Characteristics • Mainly reads • Few writes • Application Characteristics • Each user logging in connects to a particular server • Partitioned based on user-id and region • Writes from a user always happen on one server regardless of the region the user log in from • All reads redirected to the closest geo-location • Reasonable tolerance for latency (5-10 minutes) • Adventureworks is building a new web based order management system that allows customers from all over the world to access the system and place orders • The core group of customers are in Western Europe, South East Asia and North America

  24. Replication Topology Asia1 Asia2 Peer Nodes Read-Only Servers

  25. Key to Success It’s not the vendor! It’s not the technology! It’s not the features!

  26. Licensing Facts • Passive servers are mirror, log shipped secondary and clustering passive node • No license required on passive if it is truly passive • A passive server does not need a license if the number of processors in the passive server is equal to or less than the number of processors in the active server. • The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly.

  27. HA Features Edition Support ₁Single thread redo ₂ Limited to 2 node cluster

  28. question & answer

  29. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online. Resources • www.microsoft.com/teched Sessions On-Demand & Community • www.microsoft.com/learning • Microsoft Certification & Training Resources • http://microsoft.com/technet • Resources for IT Professionals • http://microsoft.com/msdn Resources for Developers

  30. Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session. Related Content Breakout Sessions DAT312 All You Needed to Know about Microsoft SQL Server 2008 Failover Clustering Hands-on Labs DAT12-HOL Microsoft SQL Server 2008 Database Mirroring, Part 1 DAT12-HOL Microsoft SQL Server 2008 Database Mirroring, Part 2 DAT05-HOL Microsoft SQL Server 2008 Data Snapshots DAT07-HOL Microsoft SQL Server 2008 Peer-to-Peer Replication DAT06-HOL Microsoft SQL Server 2008 Online Operations

  31. Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

  32. Required Slide © 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.

More Related