Disaster recovery to the Cloud Part 2: Between VMware clouds
In our last post we covered issues relating to using the cloud as a disaster recover site from an in-house IT environment. If you missed it you can read it here. So in part two we’ll look at disaster recovery from a cloud to cloud perspective.
If you’re using the cloud, you’re probably well aware of the many benefits it offers and all the different possibilities of private, public, and hybrid options. And though the cloud approach has solved or improved many of the issues with traditional IT infrastructure, there are still many challenges for disaster recovery:
Storage based replication
Many existing DR applications or solutions need to replicate the storage type, LUN, and protocols used in the production environment. This means the DR cloud site needs to have the same storage configuration as the production site. This limits the options you have for using the cloud and negates some of the benefits of being able to move from a private to a public cloud, or vice versa. The situation can get even trickier for hybrid clouds.
ultiple site management
Larger enterprises often have more than one datacentre. Operations may be spread across different infrastructures. Disaster recovery becomes more of a challenge when these sites need to be linked. Usually it requires coordination of activities between the various datacentres. This human in the loop portion of the recovery process introduces errors, delays, and may not make the most efficient use of available resources.
vCloud Director integration
For those using VMware vCloud Director (vCD) to manage their virtual datacentres, vApps, and networks, there hasn’t been any DR solution that integrates well, or is vCD “aware” enough to know about the entities. So DR plans and processes must work around them for proper replication.
There are also other issues such as multi-tenancy, data mobility, and a general lack of central management. As we mentioned in the part 1 of this series, we’ve found that Zerto Virtual Replication is a tool that helps solve the issues mentioned above for our customers. Movement between clouds, whatever the configuration, becomes straightforward because Zerto was designed to handle the challenges:
A true cloud to cloud-ready DR solution
Replication at the hypervisor
Because Zerto replicates at the hypervisor layer, and not the storage layer like traditional solutions, it is storage independent. You don’t have to recreate the exact configuration at the DR site. You can recover a private cloud in one datacentre into a public cloud using vCloud resources. Or you can recover the public cloud applications into your private cloud until the public cloud is available again. Any configuration can be moved around without concern for storage compatibility.
ne to many, or many to one
However many sites you have, Zerto supports multi-directional replication for all of them. Moving many sites into one normally would be a nightmare of network mapping and debugging to eliminate conflicts. The entire process is simple and conflict free because of centralized management.
Fully integrated with vCD
Zerto is the first DR solution integrated with vCD. It knows about your virtual data centres, vApps, networks, datastore settings and more. And because of this close integration, protection, failover and failback of your applications are automated and centrally managed.
We’ve found that Zerto’s approach to DR offers our clients tremendous flexibility and a streamlined process providing recovery within minutes for protected applications. In the end that’s what DR is all about – minimizing downtime so you can keep your business moving forward.
Are you facing particular challenges in creating or implementing a disaster recovery plan for your business? We’d love to hear what you have to say in the comments below, or give us a call and we’ll be happy to answer your questions.