So you have made the move to the cloud, or you’re on the cusp of your migration. Now, here’s the question you need to address: Do you have a disaster recovery plan in place?

Failure can happen in the cloud and it is critical that you have a mutual agreement between you and your cloud service provider to ensure that you have a plan in place in the event of a service interruption. The availability and efficiency of your Oracle, Microsoft SQL Server, or MySQL applications are essential to your day-to-day operations. If and when disaster strikes, you need to to know that business operations will continue with minimal disruption.

Regulatory compliance mandates also address DR in the cloud and you will need an SLA from your cloud provider that spells out how they are meeting those guidelines. Your cloud provider should also provide you with a clear understanding of the policies and practices they have in place to address any regulatory changes.

Disaster Recovery and Business Continuity Planning

The best disaster recovery plans are specific and actionable. There should be clear protocols in place to address any disruption in service.

The following are some steps to take when creating your disaster recovery plan:

  • Determine a Recovery Point Objective (RPO) and Recovery Time Objective (RTO) for every application. These metrics will help to both test and measure your success. While these metrics may need to be adjusted with time and experience, RPO and RTO will provide you with your starting guidelines.
  • Set priorities. Which applications need to be up and running first? Some applications are more critical to your business operations than others. Rank them in order of importance so that your team will know where to focus their energy in the event of the disaster.
  • Consider the whole infrastructure. Applications and processes are integrated and have interdependencies so you need to consider your entire infrastructure as a whole. If one application is offline, how does that affect the whole ecosystem? Prioritize based on mission critical processes and customer-facing applications.
  • Test, test, and test again. There’s no telling how your disaster recovery plan will hold up in a real-world scenario without extensive—and regular testing. These simulations can help you to refine your strategy.
  • Backup your data. The minimum requirement is to backup your data at least once every 24 hours — it may be necessary to back up data even more frequently based on whether you have a transactional system or need to meet a compliance requirement.

What role should disaster recovery play in my choice of a cloud provider?

Ultimately Disaster Recovery should be part of the conversation while you’re making the critical cloud provider decision. However, if you have already made your move to the cloud and don’t have a DR plan in place – you will need to address it immediately.

There are several factors to look to consider when looking for a Disaster Recovery partner. First and foremost – experience matters. Look for an organization who has experience in your industry and with a company of a similar profile. Geography is important – even if the cloud is everywhere, it’s best to select a cloud provider with geographic diversity. If your business is planning for growth, your provider should supply a plan to ensure they can scale along with you, as well as be flexible to your needs.

Disaster Recovery in the Cloud

Ntirety provides hybrid cloud DR services that supports users in cold, warm, and hot disaster recovery protocols, allows block-level replication changes to the cloud or to a database instance in a warm standby mode in the cloud, targets DR location to a dormant virtual machine (VM) instance, a standby instance, or an active-read-accessible instance, and more. Contact us to find out how we can help you on your cloud migration journey.