For around a year I have been working on the VMware vCloud Air Disaster Recovery offering, and have been giving a number of presentations, and writing articles about this topic. At a recent internal conference a number of people asked me if I could provide a list of all the recent articles I have written. Rather than keep sending emails with links, I thought it would make more sense to provide a list of links here so that I can refer back when needed. It may also help a few other people out in the blogosphere.
In no particular order I have grouped these articles in two categories. 1st category is vSphere based Disaster Recovery, and the 2nd is Application based high availability.
vSphere based Disaster Recovery
While most of the talk around cloud-based disaster recovery is on how you protect your workloads, a number of people are starting to look at this from a different angle. How do you connect to those workloads once they have failed over and are running in the cloud? You have literally moved all your applications and services to another datacenter, potentially in a different state or even country. “Great,” says the IT admin, “all our applications are running as expected, we don’t have any data loss.” “Fantastic job,” says the CIO, “now why can’t I open up our CRM tool? What’s this ‘not connecting’ error?”
Recently a new solution brief for VMware vCloud® Air™ Disaster Recovery was published on VMware.com. This solution brief talks specifically about how to build an end-to-end disaster recovery solution incorporating authentication and lookup.
A number of articles have been written in the past explaining how to setup and configure VMware vCloud® Air™ Disaster Recovery. These range from how to deploy the vSphere Replication Appliance, through initiating a full failover test. However some of the considerations involved in deploying a disaster recovery solution include how to protect your infrastructure virtual machines and how you can do this easily without significant cost.
Application based High Availability
VMware vSphere has always been a premier destination for virtualizing packaged applications like Microsoft SharePoint and Exchange. Being built on the same trusted foundation of vSphere, vCloud Hybrid Service continues to see the hosting of these packaged applications as one of the five common starting points to hybrid cloud.
Great Question!! This is a great use case for the hybrid cloud. One of the easiest answers is You could split up your exchange design however you see fit. Client Access Servers could be hosted on vCHS providing the public facing part of Exchange, with the backend Mailbox servers on Premise perhaps, or split across multiple clouds for DR? Anyone who knows exchange, will be thinking now of all the different possibilities you could have.