Disaster Recovery or DR for short, is a hot topic for many companies and with the spate of hacks and natural disasters and incredible storms, i.e. the snowstorm that hit Buffalo, NY just a few weeks ago, has many companies revisiting their disaster recovery solutions. Today’s blog will talk about DR for your applications running in Azure.
Just because you are storing your app in the cloud doesn’t mean you don’t need a DR strategy, should something like mentioned above happen; are you fully prepared for a temporary or even large scale failure? Before you answer that question, let me ask you another question. Does your company rehearse these failures? Has your company determined what applications, should they go down, what your tolerance level is for that app(s)? Some things to consider when creating your cloud DR plan:
- Test your recovery of databases to ensure you have the correct process in place
- High Availability
- Fault Tolerance
DR is a key component to every company’s long-term success. Taking a short-sighted approach to a DR strategy isn’t sound business. As more and more companies put more and more business critical applications in the cloud, the attention paid to DR needs to be evaluated with each application that goes into the cloud, the impact its failure can have on a company and the impact it can have as it is recovered.
In addition to dealing with unexpected disasters, rolling back failed changes and handling data corruption issues are key considerations that sometimes get forgotten when deploying to cloud platforms with greater than 99.99% uptime.
Microsoft Azure services have a number of ways that you can meet this challenge. For more detailed information on how to setup your Azure DR strategy for your applications running in Azure you can check out a white paper Disaster recovery and high availability for applications built on Microsoft Azure