Data is the lifeblood of business. You use it to build products and interact with customers. Data is valuable which means that every company should have a disaster recovery (DR) plan to ensure continuous operations. Why? Disasters are no longer just hurricanes, tornados, and floods. Systems fail, people make mistakes, bad people do bad things, and health pandemics come out of nowhere.
The need for business continuity has never been more important than now. In a recent study on enterprise IT’s response to COVID-19, Evaluator Group found that “those IT organizations that had developed and tested worst-case disaster recovery scenarios were in the best place to manage through the pandemic.”1
So about now you’re saying “I get it. But DR is time consuming, expensive, and equivalent to buying a life insurance policy.” Generally, these are all true statements which explains why DR was reserved for mission-critical applications. But like so many other things, the cloud has disrupted the economics of DR.
Partnering with AWS, Druva delivers simple disaster recovery at prices that everyone can afford. It’s easy to set up. Recover failed VMs in less than 30 minutes. Test as often as you want.
Disaster recovery-as-a-service (DRaaS)
Druva’s DRaaS allows you to failover virtual machines from the Druva Cloud into a customer-owned Amazon Virtual Private Cloud (VPC) to maintain business continuity without dedicated software, storage, or hardware. Druva DRaaS delivers the following benefits:
Built on AWS high-performance infrastructure, Druva eliminates the need for a secondary physical data center that’s dedicated to DR. This drastically reduces costs making DR affordable for any size organization.
Traditional DR solutions limit geographical distance between primary and recovery sites to 30-60 miles. Druva supports over 14+ AWS regions which means your recovery site can be anywhere, even a continent away from your primary site.
Preconfigured failover settings
Built-in templates guide the configuration of production and test infrastructure, mapping of your primary network to the VPC, subnet, AWS accounts and replication frequency. They also help configure the infrastructure and network for production and pretest environments.
Dev/test configurations that match production environments can also benefit from Druva DRaaS automated set up while saving costs and overhead from setting up separate labs within your on-premises data center.
How does it work?
1) Using a CloudFormation template, a small Druva proxy is deployed into the VPC to establish IAM roles and policies.
2) The latest VM snapshots are restored into the VPC, then changed into Amazon Elastic Block Storage (EBS) snapshots, aka DR copies. These copies will be used to set up failover and recovery.
3) When a disaster is declared, the DR copies are used to launch Amazon Elastic Compute Cloud (EC2) instances and all virtual machines are restored simultaneously. As soon as the VMs are up, your data is available to access.
Druva is unique in the industry with single-click failback to the primary site, once the event has been mitigated. Simple mirror the configuration of your primary VMs to match the failover VMs. Then virtual machine disks are attached and data transfer begins. When transfer is completed, primary VMs are rebooted and DNS connections redirected.
Data is fuel for your business and needs to be protected. At a time when threats are increasing, especially for remote worker data, now is the time to establish your DR strategy by leveraging the scalability and global reach of Druva, built on AWS.
1Evaluator Group, “Enterprise IT’s Response to COVID-19,” April 2020