Link to home
Start Free TrialLog in
Avatar of Haas71

asked on

Direction on Hyper-V 2012 R2 Multi-Site Cluster

I'm trying to find an answer to this, but I guess I'm not asking the right question. I've been reading "Windows Server 2012 Hyper-V Installation and Configuration" as well as forums and videos. But I still don't understand something. I'm sure one of you will know. Let me break it down. All servers Host servers are 2012 r2.

Main site:
10.96.0.X Subnet
IBM SAN 16 TB used
2 DC's at this site
Cluster 1: 2 servers, dual processor servers 9 TB for servers. One Quorum ( 1 GB disk witness). (One 9 TB shared volume).
Cluster 2: 3 servers, single six-way processors, 7 TB for servers. One Quorum (1 GB disk witness). (One 7 TB shared volume).

DR site: (On site but nothing configured)
10.96.74.X Subnet
DC at this site
Netapp ISCSI SAN 24 TB. No space carved out yet.
No cluster or anything created yet.
4, Dual processor Servers are loaded with 2012 R2

Servers to be replicated are a couple DB servers, Laserfiche, Finance, one file server

Here's my issue. The clusters were already in place. So they already had Quorums setup. They also have brokers setup for replication. But nothing is being replicated. It will be eventually going to the new DR site. I have another server loaded to place at a third site for a "File Share Witness". But will that work seeing there are already quorums on the clusters? Those quorums are set to dynamic by default. Also, since I also have two clusters at my main site, will I have to split up the DR servers and create two "File Share Witnesses"? One for each cluster? I guess my main concerns are with the physical quorums and FSW. Then how to setup to replicate.
Avatar of Philip Elder
Philip Elder
Flag of Canada image

Run the Quorum configuration wizard to set your new location on the FSW. Azure offers this service, that is Cloud FSW, too and it's already HA. It may be an option to eliminate the third site expense.
Avatar of Haas71


Will the FSW take the place of the current disk witnesses? Will I have to create multiple FSW for the two clusters at my main site?

No. You can create one FSW with enough space (not a lot required) to host all clusters. Each cluster would create a GUID based folder for its FSW needs.
Let's not jump the gun. You throw in the germ "replicate" with very little background. You have two different SANs, so I'll assume you don't mean storage replication. You also throw in having a broker, which at least *implies* byper-v replica. And you say "nothing" is being replicated.  So let's clear up a few things:

A file share witness is useful in a stretched cluster, but be aware that stretched clusters don't replicate anything. They act like any other cluster and access shared storage.

If you plan on using hyper-v replica, you have to configure replication yourself and the replica targets should *not* be nodes in your existing cluster. Doing so would wreak great havoc. And if only the destination is in another datacenter, disk witness for quorum is still probably better than file-share witness.

In short, k've read your initial post several times, and I get the impression you had different expectations and have inadvertently combined or attempted to combine two different scenarios that are not necessarily complementary.
Avatar of Haas71


Let me rephrase. This should help. Sorry.

I inherited a network that was half baked. So here's how things are setup.

There are two clusters at the main site. They are attached to an IBM SAN. Each cluster has its own disk witness and shared storage. One is a "cluster" of two server hosts. The other is a cluster of three server hosts. Because the servers are already in clusters, I went ahead and created the brokers for each cluster so I could replicate the data whenever we created our DR site. So the brokers are in place, but nothing is being replicated anywhere.

We recently bought a NetApp ISCSI device for a new DR site. We are not using any third party storage replication tools, so I will have to use what comes with 2012 R2. There are four servers and a NetApp at the new site. However, nothing is configured as of yet on the NetApp or the servers. Just the OS is loaded. But all hosts are running Server 2012 R2.

I'm looking to replicate the vm's listed to the DR site across a 300 MB connection via what comes with Hyper-V 2012 R2. Not any SRA's like EMC Recover Point or something. It's going across the wire. I've done this with VMware site recovery manager with hardware SRA's. But not using Hyper-V native at the new job. When I started reading about DR on Hyper-V for two sites, the articles mention needing a FSW at preferably a third site. This is where I got hung up and am trying to put all of it together. So I'm looking to get those servers out at the DR site with the ability to fail them over in case things go  foul at the main site. Once again, sorry about the confusion. Hope this helps.
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Haas71


Yes, this is not like VMware. I know how to do the replication. But I was probably reading more into it considering there were a few clusters involved. I will take the comments listed for review then award points.