Unsolved
This post is more than 5 years old
7 Posts
0
7966
May 10th, 2010 05:00
Nead some advices regarding HyperV and HA using two hosts
I've just bought two PE R710 and 1 MD3000i. This is all connected in HA using two NIC's on each server on two dedicated 6424 switches.
I first started to install Win2008 HyperV Core on both servers, but got management problems using my Laptop with Windows 7. I therfore decided to install WIndows 2008 Datacenter Edition R2 on both servers. This works just fine. I then tryed to add those into a cluster, but the the installer wanted a AD controller. So, I set one of the R710 up as an AD controller. Then the Best Practice wanted me to put up a backup domain controller, and so I did. The second Host is now the backup controller. This mean that both hosts now hosts both AD controller and DNS server. (at this point i'm beginning to wonder where I went wrong). So now I could install CLustering and it looks like this is working as it should. All Validating tests reports that everythign is well. I tehn decided to install Hyper-V on Host 1. This went well. But when I tries to install HyperV on Host-2 things starting to happend, the hosts looses theyr connection becasue the HyperV is taking one of the NIC's. I therfore are starting to wonder, should I perhaps have a small server nbr 3 to act as an AD controller?
Whats best practice here?
Just to repeate things:
I have :
Two PowerEdge R710,
One MD3000i with 7x140GB SAS disks and 3x500GB SATA drives,
Two Dell PowerConnect 5420,
I want tho use those as the base of my virtualisation in a HA environment.
Do I nead a second server? or can I virtualize the AD?
Please folks...
Nead some advice here
Dev Mgr
6 Operator
•
9.3K Posts
0
May 10th, 2010 07:00
For this kind of setup I'd recommend to start with at least 6 NICs (NIC ports):
- at least 1 for the host's management (plugged into the LAN and assign a LAN IP)
- at least 2 for iSCSI (each in a different subnet)
- at least 1 for the heartbeat/CSV connection (yet another subnet and easiest is just to connect the 2 NICs via a patch cable)
- at least 2 (in a team) for the guests' network access (once you assign this in hyper-v to be the guest network I think by default it takes the IP address off, so don't worry about the IP on this, or maybe just uncheck IP4 and IP6 to prevent clustering from complaining about DHCP).
You then also want a 3rd physical server to be your AD/DNS server (NEVER virtualize all AD servers, especially when trying to run a hyper-v-based cluster).
You set static IP addresses on everything on both servers and match the naming on the network connections to be identical between the 2 servers, then you join the 2 hyper-v (host) servers to the AD.
Now you install the hyper-v role and the clustering feature. You then set up the servers to connect to the SAN (so you install MDSM (typical option is a good choice unless you opt to play around with "core")). Make sure you make a Quorum/witness disk. Now you create the 2-node cluster. You enable CSV, you add the virtual disks you want to store VMs on to the CSV disks.
hdsoftware
7 Posts
0
May 10th, 2010 09:00
Thank you very much for your answer. I have just a few follow up questions I would appreciate it if you would take the time to answer them
1. What is CSV Connection? Is it just the same as the heartbeat?
2. You say that I should not virtualize all AD servers. Does that mean that first should be normal and the other can be virtualized?
3. Is it recomended to install just HyperV Core to the hosts or would you recomend installing full Win2008 Datacenter R2 on both?
Thanx
hdsoftware
7 Posts
0
May 10th, 2010 11:00
Sounds great. I have allready installed the hosts, so keeping those and just add a new AD control would save me a lot of work. Thanx for all info. Its much appreciated..
regards
Ole
Dev Mgr
6 Operator
•
9.3K Posts
0
May 10th, 2010 11:00
Check Microsoft's site on CSV. In a non-hyper-v cluster, on the heartbeat you generally disable everything except IP4, but on a hyper-v cluster, you need to have file and printer sharing and the Microsoft client enabled on the heartbeat for CSV to work properly.
You can run 1 or more virtual AD servers as long as you have at least 1 physical AD server. The reason is that if you have a complete poweroutage and the hosts come up, to start the cluster services they need to authenticate on the domain, which wouldn't be possible yet if all your AD servers were virtual (cluster starts first, and only then could hyper-v VMs start up).
That's your own choice. I'm not a fan of "core" as Windows wasn't designed for the command line (though R2 is much better than the original 2008), and I usually just use the remote management tools that Microsoft offers (only compatible with Windows 7 though).