Page 1 of 1

v6 - Windows Server 2012 Nic Teaming and network design

Posted: Tue Aug 21, 2012 4:49 pm
by peter.auchincloss
ANy general recommendations for usage of Server 2012 Teaming vs. stand alone multiple nics for data, hearbeat or replication channels?
originally teaming was recommended (several years ago) more recently non teamed - any change or recommended best practices for server 2012 and pending new starwind release?

from figure on Beta site - Also looks like 3 node cfg has iscsiA,icsiB data channels from each node + 3 replication net. channels. Is this recommended cfg?

P

Re: v6 - Windows Server 2012 Nic Teaming and network design

Posted: Wed Aug 22, 2012 6:30 am
by anton (staff)
NIC teaming sucks for SAN traffic. Don't do it. Use MPIO @ initiator and StarWind takes care itself of multiple channels in the best way.

With 3-way replication there are too many ways to go - you don't really need to triple network paths, doubling is an option as well.
peter.auchincloss wrote:ANy general recommendations for usage of Server 2012 Teaming vs. stand alone multiple nics for data, hearbeat or replication channels?
originally teaming was recommended (several years ago) more recently non teamed - any change or recommended best practices for server 2012 and pending new starwind release?

from figure on Beta site - Also looks like 3 node cfg has iscsiA,icsiB data channels from each node + 3 replication net. channels. Is this recommended cfg?

P