Disaster Recovery Options for Azure SQL Databases | Data Exposed: MVP Edition
Вставка
- Опубліковано 25 лип 2024
- Planning a proper disaster recovery solution is a critical piece of any infrastructure design, even when working in the cloud solutions like Azure SQL Database. Thankfully, the Azure architecture provides a solution that with only clicks of the mouse a DR plan can be implemented. In this episode with MVP John Morehouse, we’ll take a look at how easy it is to set up and configure a disaster recovery solution for Azure SQL Database.
0:00 Introduction
0:37 About John Morehouse
1:27 Demo: Backups
4:42 Demo: Active geo-replication
10:39 Demo: Failover groups
15:20 Getting started
✔️ Resources:
Backups: docs.microsoft.com/en-us/azur...
Active Geo-replication: docs.microsoft.com/en-us/azur...
Auto Failover groups: docs.microsoft.com/en-us/azur...
About John Morehouse:
John Morehouse is currently a Consultant with Denny Cherry & Associates living in Louisville, Kentucky. With over 2 decades of technical experience in various industries, John now focuses on the Microsoft Data platform and specializes in Microsoft SQL Server. He is honored to be a Microsoft Data Platform MVP, VMWare vExpert, 2016 Idera Ace, Friend of Red Gate, Sentry One PAC member & Community Ambassador. John has a passion for speaking, teaching technical topics, and giving back to the technical community as much as possible. He is a user group leader, SQL Saturday organizer, and former PASS regional mentor. He is also a blogger, avid tweeter, and a frequent speaker at SQL Saturdays as well as other conferences. If you want to find John, you can find him on Twitter (@sqlrus) or on his blog, sqlrus.com.
About MVPs:
Microsoft Most Valuable Professionals, or MVPs, are technology experts who passionately share their knowledge with the community. They are always on the "bleeding edge" and have an unstoppable urge to get their hands on new, exciting technologies. They have a very deep knowledge of Microsoft products and services, while also being able to bring together diverse platforms, products, and solutions, to solve real-world problems. MVPs make up a global community of over 4,000 technical experts and community leaders across 90 countries/regions and are driven by their passion, community spirit, and the quest for knowledge. Above all and in addition to their amazing technical abilities, MVPs are always willing to help others - that's what sets them apart. Learn more: aka.ms/mvpprogram
📌 Let's connect:
Twitter: John Morehouse, / sqlrus
Twitter: Anna Hoffman, / analyticanna
Twitter: AzureSQL, aka.ms/azuresqltw
🔴 To watch other MVP Edition episodes, see our playlist: aka.ms/dataexposedmvps
To check out even more Data Exposed episodes, see our playlist: aka.ms/dataexposedyt
🔔 Subscribe to our channels for even more SQL tips:
Microsoft Azure SQL: aka.ms/msazuresqlyt
Microsoft SQL Server: aka.ms/mssqlserveryt
Microsoft Developer: aka.ms/microsoftdeveloperyt
#MVPTuesday #AzureSQL #SQLServer #MVPBuzz #DataPlatformMVP - Наука та технологія
Excellent!! Thanks!! Very funny the Star Wars theme for the episode. Keep up the good work!
Very cute! Loved it. Great presenation.
Love the Star Wars theme! Great work!
perfect demo, thank you!
Good work. Thank you.
Great video! Thank you
Excellent ! Thanks much
Excellent Video
Great demo...
Hi Can we have a secondary replica ( sync commit ) in the same region as the primary sql server alongside with DR in another region ?
How do we ensure both are configured with read only intent the Secondary and DR
So we can clearly perform failover tests as well as dr tests
Also if we configure the Azure Sql server as business critical do we still have to manually configure Secondary replicas as per the definition azure service itself creates us upto 4 replicas
How much is the potential extra cost of using geo-replication with 1 different az region?
I have two questions.
1. There is a "Failover" button and a "Forced Failover" button. What is the difference between the two?
2. During an outage, there is a grace period of at minimum of one hour. My understanding for the Automatic Failover Policy is that the fail over won't be complete until the grace period has passed so does that mean my application will be down for at least an hour? What is the best practice on how the application should behave during that hour? Should we redirect to 'Site Down for Maintenance' page?
Hi Rick - The Failover button will perform a failover in which the things are flipped to synchronous commits and then actually do the failover. This allows for things to get fully synchronized. Forced Failover will immediately failover the database thus potentially loosing any transaction that isn't hardened to the secondary.
You are correct regarding the grace period. If the failover is initiated by the Azure service itself then it'll wait for the amount time specified in the grace period. Since Azure doesn't really have any idea on the workloads running, the grace period allows time for any transaction in flight to get hardened to the secondary. It's a way for them to ensure data safety. I would manually failover at that point and/or even force the failover, depending on your tolerance for potential data loss.
@@johnmorehouse2373 Thank you for the valuable feedback.
Im obviously missing something can someone clarify exactly who is the empire in this
🤗
Default RP is 7days if u increase you need to pay more