2ndFloor
asked on
Hyper V Configuration Question
Hi Everyone, just wanted to put this question out there.
I have a physical server running Server 2012 R2 with Hyper V. Hyper V has 3 VMs, TS, Exchange 2016 and SQL 2008.
I want to do fail over cluster with a second box.
Can I just buy a second physical box, put 2012 R2 on it, install Hyper V on it and sync all the VMs over?
My searching online seems to say no, but there seems to be some that say you can.
I'm guessing I need a NAS or a SAN to put the Data on like Exchange store (DAG) and SQL Databases along with a dedicated IP network to run the replication data over, am I wrong?
Any input or ideas (clarification) would be appreciated!
I have a physical server running Server 2012 R2 with Hyper V. Hyper V has 3 VMs, TS, Exchange 2016 and SQL 2008.
I want to do fail over cluster with a second box.
Can I just buy a second physical box, put 2012 R2 on it, install Hyper V on it and sync all the VMs over?
My searching online seems to say no, but there seems to be some that say you can.
I'm guessing I need a NAS or a SAN to put the Data on like Exchange store (DAG) and SQL Databases along with a dedicated IP network to run the replication data over, am I wrong?
Any input or ideas (clarification) would be appreciated!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you want a cluster on 2012 R2 you are going to need shared storage. You can configure a 2 node iSCSI cluster on the cheap, but please be careful about what you use for your shared storage appliance because this is going to be your most important piece. I wrote up a step by step on setting up a 2 node Hyper-V cluster on 2012 R2 using iSCSI here: http://alexappleton.net/post/44748523400/step-by-step-configuration-of-2-node-hyper-v
Alternatively, if you update your hosts to 2016 (Datacenter license) you can do S2D hyper-converged cluster. I think this would be more along the lines you are looking for. Check that out here: https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/hyper-converged-solution-using-storage-spaces-direct
Alternatively, if you update your hosts to 2016 (Datacenter license) you can do S2D hyper-converged cluster. I think this would be more along the lines you are looking for. Check that out here: https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/hyper-converged-solution-using-storage-spaces-direct
ASKER
Thank you for the quick responses!
ASKER
So there are three options:
1) Hyper V replication - cheap (no need for NAS or SAN) but no auto fail over. Just need 2nd Server + OS with Hyper V
2) 2 Node Cluster - needs a SAN, dedicated secondary IP Network but has auto fail over
3) DAG - Needs a second copy of Exchange and SQl Server on second Server Virtual Machines, does not need SAN/NAS or secondary IP network