Skip to main content

Don't Wait for a Natural Disaster to Move to the Cloud

Hurricane Arthur from NOAA.gov
Natural disasters create opportunities for heroic rescues, and this is true for cloud computing as well. My company serves many government agencies across the country, and over the years several have experienced flooding and prolonged power interruptions at their data centers.

One of the strongest business cases for cloud computing is to ensure continuity of operations, and natural disasters put this strategy to the test. I have had clients lose use of  their on premises computing facilities due to flooding and hurricanes, as well as being unable to reach their offices in blizzard conditions.

Hurricane Sandy in 2012 may have triggered the greatest level of a cloud computing response by flooding sections of New York City.  Administrators who were prepared with cloud resources moved their computing from Manhattan to Northern Virginia or even across the country to Oregon.



Services such as ylastic automate the process of moving cloud services from one zone to another in Amazon Web Services. It offers management consoles to simplify backups of Amazon Machine Instances (AMI).


BMC Truesight Pulse (formerly Boundary) works with data from AWS CloudWatch to provide insights on events and alerts.

Microsoft's Channel 9 offers a video series on building scalable, resilient cloud services in Azure. .




Whatever your disaster plan, the only way to be sure that it will work is to exercise it. Test your plan and make notes of the actions that failed or work so you can improve it.  Measure how long it takes to get the data from one place to another -- often underestimated.  

If you cannot afford to have your operation interrupted, moving to the cloud now will eliminate many of the most likely threats and open new options for operating at data centers that are in different regions.  A hybrid cloud approach brings some of the benefits of cloud migration and can provide a lifeline in case your data center is disabled or destroyed.

Don't wait for a natural disaster to adopt cloud computing.  Instead, ask yourself what you would do in case of disaster.

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/ by James Townsend 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