It’s self-explanatory when you hear what you get for the money that you are going to spend. Disaster recovery comes with many services for a number of objectives depending on the tier of data and applications your organization is dealing with. We review these objectives in here.
A hot cloud site – a recovery cloud running replica VMs to the production site using real-time replication. Recovery time objective would be 0 to 2 hours and the recovery point objective is zero to twenty-four hours for the hot cloud site.
You want to get everything up and running anywhere between 1 minute and 2 hours, everything have to be back online and you can’t lose data from more than 0 to 24 hours. That is about as good as it is going to get from a DR or a business continuity plan perspective.
There are a lot of things to be taken into consideration, availability, dedicated bandwidth, dedicated server and others when thinking about a disaster recovery in the cloud solution.
A Warm cloud site – recovery cloud containing offline copies of VMs that can be spun up during disasters or tests, so the recovery time objective is 2 to 6 hours, but their recovery point objective is between 0 and 24 hours.
A cold cloud site – the recovery cloud contains backups the production systems that must be first rehydrated (you have to do another update) and then turned into VMs before recovery can occur. The recovery time objective here would be 4 to 24 hours and the recovery point objective can be 24 to 48 hours.
If you think about risk and you think about continuity and disaster recovery from a risk perspective, those mission critical applications may need to be online on a hot cloud site. But maybe we are talking about the low risk system, systems that don’t consider the impact of employees, customers, partners and things like that, simply may not have to get up on-time, those we can put in a cold cloud site. So, you can grade DR services based on the tier of the application that you are dealing with.