I have often seen many people get confused about High Availability[HA] and Disaster Recovery [DR]. HA and DR both serve the different purpose. However, the HA & DR features in SQL Servers can be used for the purpose. And, that is where the confusion happens. Back in December 2016, I talked about the same in my post Explaining High Availability and Disaster Recovery. When an HA & DR is to design one has to think RTO and RPO objectives. Always On Availability group is one such feature, a widely used one, that can be considered as HA and DR configuration. In this post today, I am going to explain two main Advantages of using Always On instead Mirroring. HA and DR are one of my core interest areas. I have often spoken on these topics under Surat User Group SQLPASS Chapter and CSI Surat Chapter. In past, I have also spoken at TechEd in Cities events. This time, I thought, let me step out of my comfort zone. And I have submitted a session abstract at Data Platform Geek Summit organized by Amit Bansal who is also an MVP and a friend since long. Data Platform Geek Summit is Asia’s biggest summit dedicated to SQL Server platform. Apart from this, I have submitted a session abstract at SQL Saturday # 712. Without wasting much of the time, let me tell you that I have recorded a short 5-minute video on my youtube channel where I have explained two main Advantages of using Always On Instead Mirroring. I hope you will like this video and the blog post. At the bottom section, I have mentioned few more links where you can browse through the previous blog post of mine where I have discussed troubleshooting tips and talked about patching sequence of Always On Availability Group.
So far, I have done total three blog posts on Always On Availability, two on troubleshooting and one on how to patch Always On Availability Group. They are:
- Fixing Always On Error 19432 severity 16 state 0
- How to Troubleshoot Always On Synchronization Issue
- Steps to patch Always On Availability Group of Primary and Two Replica