dougdog
asked on
best way to implement hyper v on a dell poweredge t320
I have a Dell PE T320 with
24gig ram
1TB RAID1 partition using 2 x 7.2k sata disks
its using the following cpu Intel Xeon E5-2407 v2 2.40GHz, 10M Cache, 6.4GT/s QPI, No Turbo, 4C, 80W, Max Mem 1333MHz
I need to run 1 DC and 1 Exchange 2013 server for around 15 users
could anyone please give some advice on the best way to achieve this or any tips when it comes to running hyper v
I was thinking of doing the following so please correct any mistakes im making
on physical host create a c drive partition of around 60gig
create a D drive partition of the remaining 940 gig to store my virtual server disks
Install only the hyper v role and the backup role on the physical server
Use 1 nic for management and the other nic for VM traffic
create 1 Virtual DC with 1 cpu and 8 gig ram and say 500 gig disk space
create 1 Virtual exchange 2013 server with 1 cpu and14 gig ram with 400 gig drive space
use the remaining 2 gig ram for the physical hyper v host
backup both servers to usb disk from hyper v host
would this be ok?
24gig ram
1TB RAID1 partition using 2 x 7.2k sata disks
its using the following cpu Intel Xeon E5-2407 v2 2.40GHz, 10M Cache, 6.4GT/s QPI, No Turbo, 4C, 80W, Max Mem 1333MHz
I need to run 1 DC and 1 Exchange 2013 server for around 15 users
could anyone please give some advice on the best way to achieve this or any tips when it comes to running hyper v
I was thinking of doing the following so please correct any mistakes im making
on physical host create a c drive partition of around 60gig
create a D drive partition of the remaining 940 gig to store my virtual server disks
Install only the hyper v role and the backup role on the physical server
Use 1 nic for management and the other nic for VM traffic
create 1 Virtual DC with 1 cpu and 8 gig ram and say 500 gig disk space
create 1 Virtual exchange 2013 server with 1 cpu and14 gig ram with 400 gig drive space
use the remaining 2 gig ram for the physical hyper v host
backup both servers to usb disk from hyper v host
would this be ok?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Then follow the guidance presented in my article for your setup.
+ 90GB partition for host OS
+ Balance GB for Hyper-V guest files
Networking:
+ Team two NIC ports
+ Bind vSwitch to the team leaving Host OS shared
Guests:
+ 90GB VHDX OS
+ 250GB-400GB VHDX Data
+ DC: 2 vCPUs and 6GB vRAM
+ Exchange: 3 vCPUs and 16GB vRAM
Backup:
+ ShadowProtect Virtual in-guest backup to shared folder on USB attached to host.
We don't do host based backups. That's not a good thing to do. In-Guest is best unless Veeam becomes an option.
+ 90GB partition for host OS
+ Balance GB for Hyper-V guest files
Networking:
+ Team two NIC ports
+ Bind vSwitch to the team leaving Host OS shared
Guests:
+ 90GB VHDX OS
+ 250GB-400GB VHDX Data
+ DC: 2 vCPUs and 6GB vRAM
+ Exchange: 3 vCPUs and 16GB vRAM
Backup:
+ ShadowProtect Virtual in-guest backup to shared folder on USB attached to host.
We don't do host based backups. That's not a good thing to do. In-Guest is best unless Veeam becomes an option.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
many thanks its a great help
I know I messed up on the disks being 7.2k sata
for 10 users would these disks be ok for now
I know I messed up on the disks being 7.2k sata
for 10 users would these disks be ok for now
I wouldn't recommend it, especially if you'll be using the same disks for the Hyper-V host. You're not going to get very good performance but you're more than welcome to try it to see it first hand.
The good thing about VHD files is that they can simply be moved to another location should you invest in some proper enterprise grade SAS drives.
The good thing about VHD files is that they can simply be moved to another location should you invest in some proper enterprise grade SAS drives.
Since Exchange 2013 is a lot more happy with RAM than disk (it was designed to run on a single 7200 RPM SATA disk) you should be okay with the 16GB assigned to that VM.
Note: Would, could, should. ;)
We've tested a lot of configurations and so far anything around 12GB and up seems to make Exchange 2013 happy.
Note: Would, could, should. ;)
We've tested a lot of configurations and so far anything around 12GB and up seems to make Exchange 2013 happy.
ASKER
great thanks for all the advice
much appreciated
should have been asking the question before making the purchase :(
much appreciated
should have been asking the question before making the purchase :(
The box should allow for more disks to be added?
You could always purchase four more disks, set up a RAID 6 array, configure Logical Disks on the RAID controller for the OS and Hyper-V files, and go from there. You'd get a better end user experience.
Is this box for lab, in-house use, or client facing?
You could always purchase four more disks, set up a RAID 6 array, configure Logical Disks on the RAID controller for the OS and Hyper-V files, and go from there. You'd get a better end user experience.
Is this box for lab, in-house use, or client facing?
ASKER
client facing for 10 users
For a lab setup two 7200 RPM SATA Disks would suffice though performance would really suck.
For a client facing setup? No way. Points mentioned in my blog post indicated above.
SAS is preferred. 10K 2.5" SAS gives great performance. Six of them in a RAID 6 array would give enough IOPS and throughput to work with 10 users unless they are hurtling CAD/CAM around all day. Then go for eight 10K SAS disks in RAID 6.
For a client facing setup? No way. Points mentioned in my blog post indicated above.
SAS is preferred. 10K 2.5" SAS gives great performance. Six of them in a RAID 6 array would give enough IOPS and throughput to work with 10 users unless they are hurtling CAD/CAM around all day. Then go for eight 10K SAS disks in RAID 6.
ASKER