Soliciting recommendations for optimizing Network Performance using multiple NIC's in Server 2012 R2

Setting up a new Server 2012 R2 Box.

4 Dual Port nic's

Windows Server 2012 R2 as Hyper-V Host

1st Hyper-V Image as Domain Controller & File Server for 30 users

2nd Hyper-V image runs SQL Server 2014 for 7 users

3rd Hyper-V image runs CAD Server for 3-5 users


I originally wanted each VM to have 2 mapped Nic's available to it, but I am now wondering if there is a better way to do that. The Domain Controller will use the most bandwidth, then SQL, then the CAD Server.

Am I better to team 4 ports for the Domain Controller/File Server? Or am I better to link 7-8 ports together?

Thankyou for reading!
LVL 2
MJCSAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MJCSAuthor Commented:
After some more reading, I'm leaning towards:

1 port for the Hyper-V Host

4 Ports for the Domain Controller/File Server

1 Port for SQL Server

2 Ports for CAD Server

Anybody have thoughts?
0
MJCSAuthor Commented:
To clarify, not looking for redundancy as much as higher bandwidth.
0
Cliff GaliherCommented:
This really depends on environment and hardware. A SQL server with light demand but that requires low latency may benefit more from no team at all, but SR-IOV. Whether you turn on VMQ. Or if the switch supports LACP. Is the file server a bunch of small files written to often? Or large files from the CAD server? So many factors it is really not possible to give a credible answer here.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Why does your DC using high bandwidth? Is it same as a file server?
0
MJCSAuthor Commented:
Files are a mixture of sizes. Office Documents, photos, PDF's of CAD drawings etc.

I was going to put the files on the DC VM as well, however I could put them with the CAD Server VM as well i guess
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would team at least 4 ports from each physical nic, in a LACP trunk for Virtual Machines.

and have at least 2 ports from 2 physical nics for the host.
0
MJCSAuthor Commented:
Why does the host need 2, won't there be very low traffic over it's ports if the VM's have their own group of nic's?
0
MJCSAuthor Commented:
If I understand correctly, you are saying that out of 4 dualport Nic's, I'd be better off to say use port A on each NIC bundled into a virtual switch then using ports A&B on 2 Nic's.
0
Greg HejlPrincipal ConsultantCommented:
Andrew has the right Idea.

do the VM's reside on the same network?

if so, Team as many nics as you can into the virtual switch.

I would also startup a separate VM for the File Server - attach VHDx's for shares.

It's best to run AD as a standalone service - you should also have a DC that lives outside of your hyperV environment.
0
MJCSAuthor Commented:
VM's on same network

So build the biggest switch that I can and conenct all VM's to it?

You recommend create a 4th VM for File Server? And attaching each share (4-6) as a separate Virtual drive?

Do you recommend running secondary DC on the host?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would not bundle more than 4 physical ports together in a trunk to a single physical switch, unless your are "LAGGING" or "TRUNKING" across different switches in a stacked configuration.

I would then "monitor" your network performance, and check if your network bundle of 4 ports is being saturated!

I would also build the TEAM at the OS Layer which is now available in Windows 2012.
0
Greg HejlPrincipal ConsultantCommented:
one vhd for fileshares,  this will allow you to move the vhd or grow it as needed.

this should also be done on the sql server, run the OS on a separate vhd, run the DB on its own vhd and sql log files on a separate vhd.  this will allow you to scale.
0
MJCSAuthor Commented:
Is it too much to do a separate VHD for each major share?

We've got a few legacy shares that will be obsolete in a year or two and then some other shares that will be for small groups of a half-dozen users or so.
0
Greg HejlPrincipal ConsultantCommented:
absolutely not, VHD's are awesome that way!  create as many as you want,  expand and contract them as needed, etc.

here is some reading on File Server services:

http://technet.microsoft.com/en-us/library/hh831487.aspx

Don't forget to run the BPA for file services
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MJCSAuthor Commented:
This ended up being a bit of a wandering thread. I think I will tag all comments that I felt were beneficial.
0
MJCSAuthor Commented:
I believe that a bunch of helpful advice and even helpful questions were asked. Probably not enough for a definitive resource on this topic. More for a pointing in the right direction.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.