Should I build a DR strategy in public clouds, as they tend to be resilient, or use the backup? If so, what is the best DR strategy for me? Let’s discuss…
First, let’s briefly discuss the difference between Disaster Recovery and Backup, as the majority see no difference or even misuse the terms. Backup is when you replicate some state of your data to some storage (tape, NAS, cloud storage, etc.) and then have a way to restore a missing item or items from the restore points. According to some retention settings and policies, it protects from data loss, ransomware, or system failure. The best backup solution is the one that stores data efficiently and provides various recovery options like granular file/folder recovery, restores to a database, etc. Usually, recovery is supposed to run in the same or a similar environment. In the meantime, Disaster Recovery is about fast replication and recovery of the applications and the entire infrastructure; storage consumption is essential, but the main focus is on low RPO (Recovery Point Objective – the time between replications) and RTO (Recovery Time Objective – time to restore the entire system after a disaster). Data is stored in a ready-to-use format; granular file/folder recovery is an advantage, but not a core aspect. An ideal DR solution should be able to restore to another cloud or region and have a smooth failback (returning apps when the disaster is fixed) functionality.
Now that we know the difference, what technology should be used? Well, I would say that you need to have a backup functionality. It’s better than nothing and will help you recover after a failure or a disaster. You can use standard public cloud capabilities to take volume snapshots or use a vendor for that. Just be sure that you understand how long it takes to recover, where the data is stored, how much you need to pay for the backup (not just for licenses if it’s not for free, but also for storage and data transfer), and how to restore data or VMs.
Backup is excellent when you need to restore some piece of your information, but it doesn’t help a lot when the whole data center or availability zone is down.
A few years ago, companies considered public clouds insecure and unstable. Now there is an opposite trend – people tend to think that public clouds are highly reliable, store all the data in a few copies, and provide up to 100% uptime. Of course, sometimes it’s like that, but the truth is in between.
Public clouds do have issues from time to time – their regions or specific services may be down, affecting their customers, including you, as their customer. You can see the public cloud status of AWS, Azure, or GCP. For example, let’s say you run your VMs in AWS in the US-West region. If it has issues due to connectivity, your apps and VMs are in trouble. You may say it happens too seldom, and you don’t need to worry about that. I don’t remember a month without any cloud services issues for one of the Big Three. If up to 6 hours of the outage is ok for you, you can skip it; public clouds do an excellent job of restoring their services in this timeframe.
