• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

My failover Lab setup

M

MarkedOne

Limp Gawd
Joined
Aug 1, 2011
Messages
398
Hi everyone, I start to build my Failover Lab that consist of :
2 x 2008r2 server with Hyper-V ( host 1, host 2)
1 x 2008r2 server setup as ADDC
1 X 2008r2 Server with Hyper V with SCVMM and SCPDM
I will use a Synology DS111 for the ISCSI target
2 x Lab PC
Ok, this is only for lab test suppose; I have a dedicated DSL FIX Ip connection for test stuff like Exchange Server. So did I miss something in my setup? Do you think I can save a network card on each host, and use the Mydomain.admin network also for the SAN ( performance is not an issue here )

I’m still thinning if I’m gone isolate the mydomain.admin from the rest of Internet. But if you think I need connectivity, I can connect it to my other Lab internet connection. I don’t want to use the same as the VM, as I will not have anti-virus protection on few of them. ( I will not pay for an Exchange Server anti-virus just for a lab, especially that I want to have few version )

That’s it for now if you have questions, especially with my English it may not be clear …lol


vm-1.jpg
 
Even though they say you can run without a standard heartbeat network, i'll tell you from experience that this is not the way to go. You should have a heartbeat network for your Hyper-V Failover Cluster. I've seen first hand that it cause problems without it and Microsoft recommends that you still have it on any support call that i've been on.

Why do you have a separate connection for CSV's?
 
Hi what do you means by an heartbeat network ? 1 gb/s is not enough ? for the CSV, it's because every setup I check on the web have one , and I read some place that if the netwrok is busy it can trigger a false failover, so it's why I want keep it dedicated.
 
Ya I have this Simon blog on my favorit , and also the video he make, and it's from him that I learn that if I don't have a dedicated patch for communication, it will trigger a false failover, but from my understanding the CSV is use for the heartbeat too ?

from the link
"Additionally, we recommend a dedicated network for CSV, internal communication and 'heartbeat' traffic, "

P.S. that I see the face of Simon, I remeber what is the heartbeat.
 
I use a dedicated Heartbeat network. When I didn't have it, I had problems. Of course this is with two 7 node Hyper-V Failover Clusters..but as long as you have a network with Cluster Network Setting of Internal on a separate segment, that should take care of it.

My network setup consists of:

1. Network Team Mangement- Cluster Use
2. Network Team VM Traffic-Cluster Use
3. Heartbeat Network- Internal Cluster Use
4. 2 x 10Gbe iSCSI HBA's- Disabled for Cluster Use

This handles everything nicely and also handles the CSV redirect extremely well.
 
You must log in or register to reply here.
Back
Top