Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a question about the best design for site redudancy when using vSphere clusters. A bit of background info about our situation first though.

We are a medium-sized company with two main offices, located in different countries. Our networks are linked by a Layer2 150Mbps leased line which is currently underused. We have a variety of services running for internal use within the company, some on physycal servers and some on existing vSphere clusters. In our department we also run several services (almost all running under various forms of Linux) like NTP, Syslog, jump servers, monitoring servers and so on.

We have now the requirement that those servers need to be redundant within each location (which they are not at the moment) and also site redudant (which they are to some extent, the servers are duplicated in the 2nd location with configurations kept in sync via various methods at the application layer). There is no SAN available for us, at least not something that we can use at the moment.

Cost is also an issue. While we do have some budget available for this, we can't afford to buy SANs for both locations for example.

I looked at the VSA feature and it seems that this could be something for us but I am unsure how to solve the site-redudancy requirement.

At the moment for testing purposes I am setting up in a lab a vSphere 5 with VSA on two ESXi hosts. I am currently using the Essentials Plus kit with VSA license, which allows me to build a VSA cluster on up to 3 hosts, together with a vCenter license to manage them. The hosts each have two dual-port network cards and two 600GB drives, running in Raid1. Hardware-wise this will be enough for us to run the all the services we need as VMs and will provide redundandcy within the site.

At the moment I see only two option to have site redundancy:

  1. build an identical VSA cluter in the second location and keep the various services sync'ed at application layer (database sync, rsync and so on).
  2. simply move one of the hosts from the existing cluster to the second location, basically having the VSA cluster span the 150Mbps link between the sites.

I would very much prefer the second option but I am unsure how well it'll work, if it can work at all. Technically it should, we can span the needed VLANs across the leased line and have them available in the second location. The advantage would be that we don't need to worry at all about sync'ing databases and the like. But I have the feeling that the bandwidth will not be enough, I have no way of knowing how much traffic will the VSA cluster generate between the hosts. I realize that this will most likely depend on the individual usage of the VMs but still, I have no idea how VSA replicates data between the ESXi hosts.

Are these my only options or can my goals be achieved in some other way ? Is there perhaps a way to have some sort of "cold stand by" cluster in the second location where the VMs would be sync'ed once per night from the main location ? The idea is that in case the first site becomes unavailable, we would be able to bring all those VMs online there. We would be ok with the data being 1 day old.

Any answers are appreciated.

Best regards, Stefan

share|improve this question

1 Answer 1

up vote 7 down vote accepted

I would simply recommend maintaining two separate clusters and handling replication at the virtual machine level with the vSphere Replication product. This is available to you with your vSphere Essentials Plus license and allows you to maintain an RPO between 15 minutes and 24 hours (adjustable per-VM), as well as the ability to replicate to dissimilar datastore types. vSphere Replication is a component used in VMware's larger Site Recovery Manager disaster recovery suite.

I use the replication to handle offsite protection of some critical virtual machines. The newest revision of the software allows you to keep point-in-time snapshots at the destination.


enter image description here


enter image description here

share|improve this answer
    
Thanks for the answer and for the detailed explanation, Edmund. Let me see if I understood you correctly. So I setup a VSA cluster based on two ESXIi hosts in location 1. The VSA will in the end present me with two data stores on which I set up my VMs. Then I create another VSA cluster in location 2 with no VMs, but with the same two datastores. By using using the vSphere Replication feature, the VMs will be kept in sync with the ones on the cluster in location 1. Is that correct ? Will the VMs always be offline in location 2 ? –  Stefan Radovanovici Nov 2 '13 at 10:09
    
And another question: will my Essentials Plus license allow this, considering the cluster in location 2 is a totally different cluster, with its own Essentials Plus license ? Or is that not relevant ? –  Stefan Radovanovici Nov 2 '13 at 10:12
1  
The destination is not relevant. It can be in your cluster, it can be outside of it. It just needs to be a visible target. There's a vSphere replication appliance that you'd probably install on each cluster. The VMs will be off on the destination side. But in a pinch, you can enable them, or just register them on the destination's host server. The datastore names do not need to be the same. –  ewwhite Nov 2 '13 at 10:16
    
Ok, then this seems to be what we are looking for. Thanks a lot for the info. –  Stefan Radovanovici Nov 2 '13 at 10:38

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.