1. Gopal Ashok Program Manager Microsoft Corp

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

5. Defining HA and DR High availability is 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 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? Availability Class Acceptable Downtime (hrs/yr) OR RTO Acceptable Data Loss (time of last copy) OR RPO Tier 1 >99.99% (1 hr or less) 5 min or less Tier 2 99.9% - 99.99% (1- 8.5 hrs) 5 mins to 8.5 hrs Tier 3 (<99.9%) (Hours to days) Hours to days

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

7. 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?

8. Database Downtime Drivers

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

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

11. Always On Solution Characteristics No Data Loss (RPO=0) Failover UnitAuto Failover (RTO) InstDBTab + ** ReadMult- iple Write * * * Solutions Log Shipping DBMSync Async Cluster Transactional Replication Peer-Peer Replication RPOFailover Redundancy and Utilization Hard- ware App Perf Impact Manag- eability Low HighLow High***Low *** Low High Low High 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

12. 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

13. 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

14. ServiceU Disaster Recovery Architecture

15. Using Log Shipping to setup Mirroring

16. 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!!!!

17. Primary Site Upgrade Process Application Switch Over to temp cluster Block users Sync mirroring DBM Failover Redirection Remove DBM Temporary SQL Server 2008 Cluster On Windows Server 2008 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

18. Windows Server 2008 & SQL Server 2008 Better Together 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 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

19. Database Mirroring Compression Benefit Cost

20. Automatic Page Repair

21. Rolling upgrade using Mirroring

22. 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

23. 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

24. Scale Out and Availability Scenario 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  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)

25. Replication Topology Peer Nodes Read-Only Servers Asia1Asia2

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

27. 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.

28. HA Features Edition Support FeatureExpressWorkgroupStandardEnterpriseComments Database Mirroring 1 Advanced high availability solution that includes fast failover and automatic client redirection Failover Clustering 2 Backup Log-shipping Data backup and recovery solution Online System Changes Includes Hot Add Memory, dedicated administrative connection, and other online operations Online Indexing Online Restore Fast Recovery Database available when undo operations begin ₁Single thread redo ₂ Limited to 2 node cluster

30. www.microsoft.com/teched Sessions On-Demand & Community http://microsoft.com/technet Resources for IT Professionals http://microsoft.com/msdn Resources for Developers www.microsoft.com/learning 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.

31. 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 Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session. Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session.

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

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