{"id":10286,"date":"2019-05-09T00:00:00","date_gmt":"2019-05-09T05:00:00","guid":{"rendered":"https:\/\/threecloud.wpengine.com\/post\/disaster-recovery-in-azure-sql-data-warehouse\/"},"modified":"2023-05-01T21:57:28","modified_gmt":"2023-05-02T02:57:28","slug":"disaster-recovery-in-azure-sql-data-warehouse","status":"publish","type":"post","link":"https:\/\/3cloudsolutions.com\/resources\/disaster-recovery-in-azure-sql-data-warehouse\/","title":{"rendered":"Disaster Recovery in Azure SQL Data Warehouse"},"content":{"rendered":"<p>What is your disaster recovery plan for your Azure SQL Data Warehouse? <strong>Today I\u2019d like to talk about disaster recovery in Azure SQL Data Warehouse, more specifically, about a feature that was released with Azure SQL Data Warehouse Gen2 called Geo-backup policy.<\/strong><\/p>\n<p>The image below shows my configuration of an Azure SQL Data Warehouse. I have a menu shown here for the Geo-backup policy and you\u2019ll see my selection says it\u2019s enabled but I don\u2019t have the choice of turning it on and off. In Gen2 this is turned on by default and cannot be turned off.<\/p>\n<p><img decoding=\"async\" style=\"width: 930px;\" src=\"https:\/\/3cloudsolutions.com\/wp-content\/uploads\/2021\/09\/DisasterRecoveryAzureSQLDWGen2_02.jpg\" alt=\"DisasterRecoveryAzureSQLDWGen2_02\" width=\"930\" \/><\/p>\n<p>If you\u2019re using Gen1, although it is turned on by default so the Geo-backup policy is enabled automatically, you can opt out of this feature unlike Gen2.<\/p>\n<p><strong>What Geo-backup policy does is it automatically creates backups of our Azure SQL Data Warehouse to store in a different region or in a region other than where our data warehouse is hosted.<\/strong> This means my <strong>backups are automatically taken and stored in the other region in a region pair.<\/strong><\/p>\n<p><strong>Microsoft has created these region pairings<\/strong>\u00a0so if I have a data warehouse hosted, for example, in East US, then the Geo-backups will be taken and stored in the West US. A partial list of the region pairings is below; you can view the full list on Microsoft\u2019s website.<\/p>\n<p><img decoding=\"async\" style=\"width: 652px;\" src=\"https:\/\/3cloudsolutions.com\/wp-content\/uploads\/2021\/09\/DisasterRecoveryAzureSQLDWGen2_03.jpg\" alt=\"DisasterRecoveryAzureSQLDWGen2_03\" width=\"652\" \/><\/p>\n<p><strong>The regions in a pair are generally more than 300 miles apart from each other with the idea being that any outage impacting your home region should not impact the Geo-backup region.<\/strong> A few more interesting points about Geo-backups:<\/p>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li><strong>Geo-backups are performed only once per day, so don\u2019t get this confused with backups that are happening on the original or local copy.<\/strong> Those are still happening via snapshots more frequently throughout the day.<\/li>\n<li><strong>If I must do a restore, I can restore that Geo-backup anywhere I want to any other region that supports the Azure SQL Data Warehouse product<\/strong>. So, I\u2019m not limited to restoring it to the paired region that Microsoft has determined for me.<\/li>\n<li><strong>The solution with these backups is not a high availability or an automatic fail over type solution. It\u2019s much different than some of the features we have available for redundancy and high availability with Azure SQL Database.<\/strong> This is not any type of synchronous replication and there\u2019s no automatic failover to point to the backup data center \u2013 it\u2019s strictly a backup process.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><iframe loading=\"lazy\" src=\"https:\/\/www.youtube.com\/embed\/Gd2b6kQv48s\" width=\"560\" height=\"315\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<p>The Geo-backup policy as part of Azure SQL Data Warehouse Gen2 is an interesting feature and can be very helpful.<\/p>\n<p><strong>Need further help? Our expert team and solution offerings can help your business with any Azure product or service, including Managed Services offerings. Contact us at 888-8AZURE or\u00a0 <a href=\"mailto:sales@3cloudsolutions.com\">sales@3cloudsolutions.com<\/a>.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>What is your disaster recovery plan for your Azure SQL Data Warehouse? Today I\u2019d like&mldr;<\/p>\n","protected":false},"author":32,"featured_media":9331,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":""},"categories":[260,297],"tags":[],"class_list":["post-10286","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-data-ai","category-data-platform","topics-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/posts\/10286","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/comments?post=10286"}],"version-history":[{"count":0,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/posts\/10286\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/media\/9331"}],"wp:attachment":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/media?parent=10286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/categories?post=10286"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/tags?post=10286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}