Support for Azure virtual machines availability sets has been a highly anticipated capability by many Azure Site Recovery customers. Today, I am excited to announce that Azure Site Recovery now supports creating failed over virtual machines in an availability set.
Disaster recovery is not only about replicating your virtual machines but also about end to end application recovery that is tested multiple times, error free, and stress free when disaster strikes, which are the Azure Site Recovery promises. If you have never seen your application run in Microsoft Azure, chances are that when a real disaster happens, the virtual machines may just boot, but your business may remain down. The importance and complexity involved in recovering applications was described in the previous blog of this series - Disaster recovery for applications, not just virtual machines using Azure Site Recovery. This blog covers how you can use the Azure Site Recovery construct of recovery plans to failover or migrate applications to Microsoft Azure in the most tested and deterministic way, using an example of recovering a real-world application to the public cloud.
Azure Site Recovery is Microsoft's single disaster recovery offering for applications that works with multiple native application-level replication technologies and provides in-built replication. With features like single and multi-tier application consistency, near continuous replication, extensible recovery plans with rich automation support, and advanced network management, Azure Site Recovery does the complex job of stitching together the application assuring full application recovery, and not just virtual machine boot up. To top it all, Microsoft tests and certifies many popular first and third-party applications and provides detailed Azure Site Recovery solution guidance for them.
We are pleased to announce the update to the resiliency technical guidance documentation for Microsoft Azure.
Announcing the availability of service-level guidance for disaster recovery.
The built-in active geo-replication has been generally available to the Premium databases for over a year. As a growing number of SaaS customers use the multi-tenant design pattern, including the use…
Points to new topics describing Linux containers, Docker VM Extension usage, CoreOS VM images for clusters of containers, and a wide range of Linux documentation on azure.microsoft.com.
In this final post in our series on Business Continuity I’m going to look at point-in-time restore, a self-service feature available for Basic, Standard, and Premium databases.
This post continues our series on the Business Continuity/Disaster Recovery (BCDR) capabilities of Azure SQL Database and focuses on geo-restore. In my previous post on standard geo-replication I discussed how the various business continuity features map to service tiers.
In this post, we will continue the conversation about the business continuity scenarios and discuss the newly released Standard Geo-Replication feature of Azure SQL Database. Before diving into the details, it would be useful to summarize the full range of the business continuity features now available in preview and discuss what you should use and why.