High Availability & Disaster Recovery withSQL Server 2012 AlwaysOn Availability GroupTurgay SahtiyanMicrosoft – Senior SQL...
Turgay SahtiyanMicrosoft – Senior SQL Server Premier Field EngineerFounder and Former President of SQLPass Turkey ChapterF...
SQL Server High AvailabilitySQL Server High Availability TodayDatabase MirroringFailover Cluster InstanceLog ShippingToday...
Failover Cluster3PublicSharedStorageSQL ServerInstanceSQL ServerInstance
Database Mirroring4Principal DatabaseClientPrincipal Server Mirror ServerMirror DatabaseTransaction Log StreamWitness Server
Log Shipping5
Failover Clustering and Database Mirroring6PrimaryData CenterSecondaryData CenterSQL Server 2008 R2Failover ClusterSQL Ser...
Database Mirroring and Log Shipping7PrimaryDatacenterDisaster RecoveryDatacenter2SQL Server 2008 R2Database MirroringSQL S...
Limitations of Current HA/DR SolutionsSolutions are fragmentedDatabase mirroring does not allow multiple secondariesMultip...
SQL Server AlwaysOn: Features9Availability Groups and Failover Cluster Instances rely on Windows Server failoverclustering...
AlwaysOn Availability Groups10PrimaryData CenterReportsAAAASecondaryData CenterReplica 1Replica 3Replica 2Replica 4Reports...
Client Failover using Virtual NameAvailability Group Virtual Name allow applicationsto failover seamlessly on availability...
Readable SecondaryReadable secondary allow offloading read queries to secondaryClose to real-time data, latency of log syn...
Active Secondary : Read-only RoutingApplicationIntent – A New Connection PropertyUsed to get access to secondaryApplicable...
Active Secondary : Read-only Routing14
Backup on Secondary ReplicasBackups can be done on any replica of a databaseLog backups done on all replicas form a single...
Availability Group Scenarios16Availability Group provides redundancyfor databases on both standaloneinstances and failover...
Demo17Synchronize AsynchronizeAAA
Real Customer Scenario18Synchronize AsynchronizeAAPrimaryData CenterSecondaryData CenterReportsBackupsBackupsAFCI
Microsoft Confidential19www.turgaysahtiyan.com@turgaysahtiyan
Upcoming SlideShare
Loading in …5
×

High Availability & Disaster Recovery with SQL Server 2012 AlwaysOn Availability Group

1,568 views

Published on

The AlwaysOn Availability Groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in SQL Server 2012, AlwaysOn Availability Groups maximizes the availability of a set of user databases for an enterprise. In this session we will talk about what’s coming with Always On, and how does it help to improve high availability and disaster recovery solutions.

Published in: Technology
1 Comment
5 Likes
Statistics
Notes
No Downloads
Views
Total views
1,568
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
1
Likes
5
Embeds 0
No embeds

No notes for slide

High Availability & Disaster Recovery with SQL Server 2012 AlwaysOn Availability Group

  1. 1. High Availability & Disaster Recovery withSQL Server 2012 AlwaysOn Availability GroupTurgay SahtiyanMicrosoft – Senior SQL Server PFEwww.turgaysahtiyan.com@ @turgaysahtiyan
  2. 2. Turgay SahtiyanMicrosoft – Senior SQL Server Premier Field EngineerFounder and Former President of SQLPass Turkey ChapterFormer SQL Server MVPSpeaker / Writer / Presenter at SQLSaturdays & Local EventsSocial MediaTwitter : @turgaysahtiyanBlog : www.turgaysahtiyan.com | http://blogs.msdn.com/turgaysLinkedin : http://aka.ms/turgaysahtiyan_li1
  3. 3. SQL Server High AvailabilitySQL Server High Availability TodayDatabase MirroringFailover Cluster InstanceLog ShippingToday customers demand moreBetter AvailabilityHigher ROISimplicity2
  4. 4. Failover Cluster3PublicSharedStorageSQL ServerInstanceSQL ServerInstance
  5. 5. Database Mirroring4Principal DatabaseClientPrincipal Server Mirror ServerMirror DatabaseTransaction Log StreamWitness Server
  6. 6. Log Shipping5
  7. 7. Failover Clustering and Database Mirroring6PrimaryData CenterSecondaryData CenterSQL Server 2008 R2Failover ClusterSQL Server 2008 R2Failover ClusterAsynchronous DatabaseMirroringAsynchronous Data Movement with Database Mirroring
  8. 8. Database Mirroring and Log Shipping7PrimaryDatacenterDisaster RecoveryDatacenter2SQL Server 2008 R2Database MirroringSQL Server 2008 R2Log ShippingDisaster RecoveryDatacenter1SQL Server 2008 R2Log ShippingWitnessLog ShippingSynchronous Data Movement with Database Mirroring
  9. 9. Limitations of Current HA/DR SolutionsSolutions are fragmentedDatabase mirroring does not allow multiple secondariesMultiple databases cannot fail over as a groupLog shipping might lose data and does not fail overautomaticallyPassive servers are mostly running idleOffloading of reporting and maintenance tasks from theprimary server is not easySAN is a single point of failure in failover clustering8
  10. 10. SQL Server AlwaysOn: Features9Availability Groups and Failover Cluster Instances rely on Windows Server failoverclustering, which provides a robust and reliable high-availability platformAlwaysOnAvailability Groupsfor Database Protection• New in SQL Server 2012 with:• Multiple database failover• Multiple secondaries• Active secondaries• Fast application failover• Integrated high-availabilitymanagementAlwaysOnFailover Cluster Instancesfor Instance Level Protection• Enhanced in SQL Server 2012with:• Multi-subnet clustering• Flexible failover policies• Improved diagnostics• Faster failover• TempDB on local drives
  11. 11. AlwaysOn Availability Groups10PrimaryData CenterReportsAAAASecondaryData CenterReplica 1Replica 3Replica 2Replica 4ReportsBackupsBackupsAsynchronous Data MovementSynchronous Data MovementAAPrimary ReplicaSecondary Replica
  12. 12. Client Failover using Virtual NameAvailability Group Virtual Name allow applicationsto failover seamlessly on availability group failoverApplication reconnects using a virtual name after afailover to a secondary11AGHRHRDB HRDBPrimary SecondaryHRVNN-server HRVNN;-catalog HRDBApplication retry during failoverConnect to new primary oncefailover is completeand the virtual name is onlinePrimary SecondarySecondaryHRDBServerA ServerB ServerC
  13. 13. Readable SecondaryReadable secondary allow offloading read queries to secondaryClose to real-time data, latency of log synchronization impact datafreshnessBackup ve DBCC CheckDB operations can be done on secondaryAuto-create statistics on the secondary replica but persist them inTempDB12DB2DB1SQLservr.exe SQLservr.exeInstanceADB2DB1Primary SecondaryDatabase Log SynchronizationInstanceBReports
  14. 14. Active Secondary : Read-only RoutingApplicationIntent – A New Connection PropertyUsed to get access to secondaryApplicable when Secondary Replica set withALLOW_CONNECTIONS =READ_ONLY or YES (ALL)Connection StringConnect directly to a secondary instanceServer=myListener; Database=DB1; ApplicationIntent = ReadOnlyRead-Only RoutingConnection behavior optimized for automatic routing of read onlyapplications to secondaryYou have to create the routes manually for this to work13
  15. 15. Active Secondary : Read-only Routing14
  16. 16. Backup on Secondary ReplicasBackups can be done on any replica of a databaseLog backups done on all replicas form a single log chainBackups on primary replica still worksSupported backup types on secondary:Full - COPY_ONLY method is only one supported Availability ReplicaTransaction LogDifferential - Not SupportedBackup PreferencePrefer SecondarySecondary OnlyPrimaryAny Replicasys.fn_hadr_backup_is_preferred_replica15
  17. 17. Availability Group Scenarios16Availability Group provides redundancyfor databases on both standaloneinstances and failover cluster instancesSynchronize AsynchronizeAADirect Attached Storage local, regional and geo secondariesAAShared Storage, regional and geo secondariesAAA
  18. 18. Demo17Synchronize AsynchronizeAAA
  19. 19. Real Customer Scenario18Synchronize AsynchronizeAAPrimaryData CenterSecondaryData CenterReportsBackupsBackupsAFCI
  20. 20. Microsoft Confidential19www.turgaysahtiyan.com@turgaysahtiyan

×