According to a recent survey, 96% of IT professionals are increasingly concerned about their company being hit with ransomware. Given the current economic climate, the ability to recover quickly and without paying the attackers has never been more critical.
Cloud-native Disaster Recovery (DR) solutions have converted complex, legacy, manual DR processes into a simple, cost-effective, SaaS-based approach. Scott Stricker, VP of Sales, and Ben Oken, Sr. Systems Engineer, at Datrium recently discussed cloud-native DR and how IT professionals are implementing it to protect their businesses from ransomware and other disasters:
- Getting started with cloud-native DR in 10 minutes
- Achieving instant recovery time objectives (RTO) for ransomware or any other type of disaster
- Cost-optimizing their data protection and DR plans to get 10x savings on DR with an on-demand model using the public cloud
Q: What’s the biggest advantage Datrium offers over other vendors who offer backup to the cloud?
A: Being able to back up to the cloud is just table stakes now. You need to have out-of-region backup – whether that’s your on-premises backup vendor, your storage vendor, or a cloud-native backup vendor. Datrium’s biggest differentiator is our ability to live-mount data directly out of S3 into a full running workload without having to rehydrate it before startup.
Q: It’s great that you can start workloads directly from S3, but what’s the application performance like when using S3 to store the data?
A: We restart all the workloads on S3 to ensure that we can have your workloads up and running instantaneously. Let’s look at specific cases where you have applications that require high IOPS, or it’s a prolonged disaster, and you need to be running for a longer period. While the workload is up and running instantly, we will vMotion workloads in the background in idle time, into a faster version of storage, let’s say an EBS flash, so you get the application-level performance that you want. But that’s not required to start your workloads.
Q: You mentioned runbook configurations. How in-depth do those go?
A: You can map source and destination resources for both your compute layer, networking, and any IP address changes that need to be made. Plus, you can orchestrate the order of operations, so the correct resources come up in the appropriate order, allowing for additional scripting to be added. If you’ve got additional scripts that sit outside the Datrium envelope, you can kick off other processes as part of that runbook. And, having compliance checks every 30 minutes gives you confidence that if something does change, you can address it quickly versus every six months when you run your DR test. You can fix issues in small intervals instead of finding a lot of big problems that require a couple of days to fix.