Upgrade to Native SAN for Hyper-V

[knip]

Hi:

I am running a 2 nodes Hyper-V 2.0 cluster using a Starwind 5.0 iSCSI target and would like to upgrade to Windows 2012 and also Native SAN for Hyper-V.

1. The two nodes have dual Xeon E5410 2.33Hz quad core CPU (totally 8 cores on each node). E5410 is below your recommended E5620. Is it still okay for the Native SAN for Hyper-V?

2. Does the two nodes need to have identical amount of RAM and hard disks? How about the 3 nodes active-active-active configuration?

3. How many nic cards in each nodes for 3 nodes active-active-active configuration?

4. Does Native SAN works in Windows Server 2012?

Thank you.

[anton (staff)]

1) Absolutely enough!

2) No need to be the same. Triple active-active-active is also supported.

3) It's recommended to have at least doubled infrastructure. So a pair of NICs for SAN traffic (MPIO configured) and a pair of switches. You can also run triplicated network infrastructure for performance.

4) Sure it does.

Hi:

I am running a 2 nodes Hyper-V 2.0 cluster using a Starwind 5.0 iSCSI target and would like to upgrade to Windows 2012 and also Native SAN for Hyper-V.

1. The two nodes have dual Xeon E5410 2.33Hz quad core CPU (totally 8 cores on each node). E5410 is below your recommended E5620. Is it still okay for the Native SAN for Hyper-V?

2. Does the two nodes need to have identical amount of RAM and hard disks? How about the 3 nodes active-active-active configuration?

3. How many nic cards in each nodes for 3 nodes active-active-active configuration?

4. Does Native SAN works in Windows Server 2012?

Thank you.

[knip]

Hi Anton:

Thank you for the answers. I am interested in 3 nodes configuration and have the following questions:

A. I found a diagram for a two nodes configuration (page 4 of StarWind Native SAN: Providing HA Shared Storage for Hyper-V). It seems that the heartbeat channel is using the same switch as the SAN traffic. Is that correct? Do we need a separate NIC card for heartbeat?

B. How many NIC card is required for nodes synchronization on each node?

C. What will be the purpose for the two switches? Is one for heartbeat (and/or SAN traffic) and the other one for synchronization?

D. Do you have a diagram for 3 nodes?

Thanks you.

[Anatoly (staff)]

A. I found a diagram for a two nodes configuration (page 4 of StarWind Native SAN: Providing HA Shared Storage for Hyper-V). It seems that the heartbeat channel is using the same switch as the SAN traffic. Is that correct? Do we need a separate NIC card for heartbeat?

Yes, this is correct. HeartBeat is simple ping signal, that have Node Health Status Check function, so it wont overload the network at all, but it will increase the fault-tolerance of the system. Moreover, you can put HB on the every data link that you have in your system.

B. How many NIC card is required for nodes synchronization on each node?

In 3 nodes configuration you need to have 2 NICs on each server for Synchronization channel purposes.

C. What will be the purpose for the two switches? Is one for heartbeat (and/or SAN traffic) and the other one for synchronization?

We recommend to have only directly connected NICs on the SyncChannel. Having everything doubled obviously increasing fault-tolerance of hte system since element B will pickup functionality of element A in event of its failure.

D. Do you have a diagram for 3 nodes?

Here it goes. This one is made by me and soon we will get the documents with similar config.

scheme.jpg (63.97 KiB) Viewed 6255 times

As you can see there is only one switch here, so this is really basic configuration, and it is recommended to have it doubled. Basically you have SyncChannel (Red), iSCSI client connection (Green) and Hyper-V traffic (blue). You can put hte HeartBeat on all the data links except SyncChannel.