DR practices that were designed for in-house computing are out of sync with the cloud world. If you haven’t already revised your DR plan for cloud computing, now’s the time.
If you haven’t already revised your DR plan for cloud-based computing, you need do it now.
“We really haven’t thought about modifying our DR plan until now,” said an IT manager at a west coast financial services firm. “When we went back over our contracts with cloud vendors, we discovered that almost all of the contracts contained disclaimer clauses saying that the cloud providers would not be responsible for service or data recovery SLAs if a disaster occurred. That really concerned us.”
The plot thickens further for companies using software as a service (SaaS) vendors that in turn rely on third party cloud providers to host their services.
What happens when the third-party cloud provider the SaaS company is using experiences an outage in its data center? “In that case, which is highly unlikely, we would simply put the client in touch with our cloud provider,” said one California SaaS company executive.
Unfortunately, finding yourself face to face with a third party you have no contract with and that you don’t even know, is not a good position to find yourself in if you are experiencing a disaster.
In the cloud, you have to think differently. DR practices that were designed for in-house computing are out of sync with the cloud world, where strategies such as replication of systems and data, cooperative testing with vendors, and even failover to alternate vendors need to be considered.