|Latest 7 Posts
| The Future of Exchange- The Next Eldorado|
Mon, Oct 15th 2012 290
| Does Exchange 2013 kill third party monitoring applications?|
Fri, Oct 5th 2012 169
| Is the Microsoft Exchange Admin Community still powerful? |
Tue, Oct 2nd 2012 103
| Microsoft Exchange Conference, Day One|
Tue, Sep 25th 2012 113
| Microsoft Exchange 2013: What’s New?|
Wed, Sep 19th 2012 166
| Exchange Server 2013, the Cloud, Exchange security, see you all at MEC 2012!|
Tue, Sep 11th 2012 106
| The MEC Returns...|
Fri, Sep 7th 2012 110
Sorry, no records were found!
||Exchange 2010 and Hyper-V
The GSX Blog
Well, after having attended TechEd last week and the Microsoft Management Summit in April it’s clear that virtualization, managed via the private cloud needs to be a critical part of a messaging administrator’s proficiencies. In this post I’m going to summarize some of the best practices when virtualizing your Exchange servers in a Hyper-V environment as referenced in a recent whitepaper released by Microsoft.
Scale-Up or Out?
The whitepaper generally recommends that organizations scale up (fewer server, more resources each) rather than out although both options are supported as it largely depends upon the customer’s environment.
Hyper-V Root Sizing
- For RAM calculations add an additional GB of RAM for Windows Server 2008 R2 management
- Dedicated management NIC for the Hyper-V root Server
- When using live migration dedicate a GB NIC
- Separate dedicated NICs for ISCSI
- Separate LUNs/Arrays for Management OS, Guest OS and VM storage
- RAID for data protection
- Blades with two local disks, host only. Guests on DAS or SAN
- BIN file planning, equal to the memory allocated for each VM, stored with the guest VHD
- 10% CPU overhead for hypervisor management of guests
Hyper-V Guest Configuration
- Sized according to physical deployments
- Disable dynamic memory adjustment
- Fixed VHD’s for the virtual OS
- Separate spindles for Exchange from guest OS
- Hub Transport, consider space for message queue database and logs
- Mailbox Role, consider databases, transaction logs, content index and other logs.
Determining Exchange Server Role VM locations
- Deploy the same roles across multiple physical server roots for HA and load balancing
- Do not deploy members of the same DAG or all CAS or HUB on the same root (defeats HA)
- Balance workload across guest VM’s
- Deployment Recommendations
- Design guest VMs according to standard Exchange 2010 deployment principles
- Balance all roles among the root servers in order to maximize physical resources
This is just a quick summary of some of the basic items to take into considering when virtualizing Exchange 2010 with Hyper-V. For full details I recommend reading the entire paper (39 Pages) which can be downloaded here.
Download our latest eBook about How to take the most out of your messaging private cloud environment?
Jun 22, 2012
Sorry, no records were found!
| Recent Blog Posts