Hey all,
I'm trying to optimize a client's HyperV virtual servers and I'm hoping to get some advice.
The environment is as follows.
Host Server:
Windows Server 2008 R2 Standard
64 bit
32 GB RAM
Hyper-V role
4 network adapters
Virtual Machines
Server 1 - Domain Controller 1048 MB RAM
Server 2 - Database server 1 8192 MB
Server 3 - RDS / Application Server 1 16384 MB
Server 4 - Database server 2 2048 MB
Currently there is one virtual network configured on the HyperV server, using physical LAN port 1. All VM network adapters use this virtual network.
All users only connect to the Virtual servers, mostly to the RDS.
I'd like to optimize the network traffic and hopefully speed up the user experience, particularly between RDS server 1 and Database server 1.
I'm looking for suggestions on the best way to do this and I'm convinced there is a better way to set this network up, possibly utilizing physical LAN adapter 2,3 and 4 on the HyperV host.
Hope this makes sense, I'm relatively new with virtual machines. Any help would be appreciated.
I'm sure I'm missing some information, questions are welcome.
Yes this makes sense and is what I was thinking. But how would the network addressing work on the VM's. I can't conceptualize it.
All the VMs are on 192.168.1.x (the HyperV host is actually also on this subnet) Internet Gateway is 192.168.1.1 ans is also running DHCP.
If I add another NIC to database 1 and RDS (bound to a new virtual network, I'll assume you meant an internal virtual network) how would I address them on the VMs.
Put another way, I don't want to confuse things by adding a NIC to the virtual OS, but if I did, would I address them to get another address on the subnet 192.168.1.x? and then have multiple gateways?