Skip to main content

Microsoft Azure for Recovery Sites and Failover

Whether you are operating your servers on premises or in the cloud, a cloud service like Microsoft Azure, Amazon Web Services or Google Cloud Platform are ideal for supporting recovery of sites in case of hardware or communications failures.  If your servers are primarily at your data center, having additional servers at that facility may not help your users if access is cut off due to a natural disaster or other event.  Recent floods in North Carolina and South Carolina remind us of how infrastructure can be vulnerable to weather. 

Microsoft Azure provides you a resource for building failover and maintenance sites which will be up and running even when your data center cannot be.   Microsoft offers technical documentation and videos that take you through the steps of establishing recovery sites.


These techniques are based on several failover scenarios, including these:

FailoverSourceTarget
Azure to AzureAzure regionAzure region
VMware to AzureConfiguration serverAzure
Physical machines to AzureConfiguration serverAzure
Hyper-V managed by VMM to AzureVMM display nameAzure
Hyper-V without VMM to AzureHyper-V site nameAzure
VMM to VMMVMM friendly nameVMM display name

There are many combinations of service and server types which are supported for failover scenarios, including virtual machines (VMware and Hyper-V), Windows, Linux, and other servers as well as database services such as SQL Server and MySQL. 

Using Azure for recovery sites is a good way to become more familiar with cloud computing and learn about your costs based on actual workloads rather than models and simulations. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan