Home > Exchange Server, Hyper-V R2 & virtualization > Conditions to support Exchange Server 2007 on hyper-V Server

Conditions to support Exchange Server 2007 on hyper-V Server

November 14, 2010 Leave a comment Go to comments

Conditions to support Exchange Server 2007:

  • In Microsoft virtualization environment, it must be Windows Server 2008 Hyper-V x64 (Not Virtual Server NOT virtual PC)
  • The Virtualization software other than Microsoft Hyper-V must pass the Server Virtualization Validation Program SVVP (at this moment only Hyper-V passed this test)
  • Exchange Server 2007 must be with SP1 or later
  • Exchange Server 2007 with SP1 must be installed on a guest operating system running Windows Server 2008 x64
  • Support high availability and Exchange clustering Local Continuous Replication, Cluster Continuous Replication, Single Copy Cluster and Standby Continuous Replication. However when using Quick Migration with Hyper-V the CCR and SCC will not be supported.
    Exchange Server 2007 installed without the Unified Messaging Server role, the UM server role is not yet supported
  • If you will use virtual hard disks, Only Fixed Size Disks are supported. Differencing, dynamically expanded or any virtual storage are not supported, ONLY FIXED SIZE HARD DISK is supported as virtual disk type
  • The Root Server (the one that run the Hyper-V components) must be dedicated server for that purpose, it’s not supported to install any other software on the Root server, it should function only as Hyper-V Server
  • Hyper-V include a feature called snapshots that you can revert the system back to this captured state, but it’s not supported with Exchange Server 2007 Virtual Guest as the Snapshot is not Exchange-Aware
  • The virtual processor-to-logical processor mapping must not exceed 2:1 otherwise it’s not supported, that’s mean if you have server with two processors with dual core, that’s make total of 4 logical processors, the maximum supported is 2:1 which is 8 CPUs in this case, note that these 8 CPUs is the maximum allowed per ALL guests on the same root
  • hardware-based VSS solutions is not supported to back up virtualized Exchange Server

Guidelines, Recommendations and best practices:

  1. Use pass-through SCSI storage disks or internet iSCSI storage for better performance
  2. Before creating virtual disk, it’s recommended to start disk defragment on the root server to reduce disk fragments
  3. Install the integration services on the guest operating system
  4. Ensure that an enforced Data Execution Prevention (DEP) must be available and enabled on the hardware level
  5. Keep in mind that if you will use Windows Server 2008 datacenter Edition, you physical memory can support up to 1 TB (TERABYTE) of memory, with enterprise edition you limited to 64 GB, and for standard only 32 GB of memory
  6. Hyper-V is supported on physical computers with up to 16 logical processors.
  7. You can use TPM chip with Bit Locker ® security feature of Windows Server 2008 to secure your virtual hard disks
  8. The virtual fixed size hard disk is limited in size to 2040 Gigabyte of disk space, while the pass-through physical disks are not limited to a space
  9. You can take up to 50 snapshots of per guest, it’s supported only to make your backup solution for a recovery of Exchange disasters
  10. When allocating the number of virtual processors don’t forget the root server share of the
    Use Windows System Resource Manager WSRM to control the resources utilization
  11. When calculating the total number of virtual processors required by the root machine, you must also account for both I/O and operating system requirements. In most cases, the equivalent number of virtual processors required in the root operating system for a system hosting Exchange virtual machines is 2. This value should be used as a baseline for the root operating system virtual processor when calculating the overall ratio of physical cores to virtual processors. If performance monitoring of the root operating system indicates you are consuming more processor utilization than the equivalent of 2 processors, you should reduce the count of virtual processors assigned to guest virtual machines accordingly and verify that the overall virtual processor-to-physical core ratio is no greater than 2:1.
  12. The Exchange server guest machine’s storage and network design requires additional considerations for the root machine, specifically, the impact to the CPUs on the root machine. In some hardware virtualization environments (such as Hyper-V), all I/O requests that are made by guest virtual machines are serviced through the root machine. In these environments, we recommend that no other I/O intensive applications (for example, Microsoft SQL Server) be deployed on guest machines that are hosted on the same root machine as Exchange server guest machines.
  13. Use multiple network adapters for network-intensive VM workloads, and management
  14. Ensure your storage hardware has I/O bandwidth and capacity to meet current and future needs of the VMs.
  15. Consider Placing VMs with highly disk-intensive workloads on different physical disks will likely improve overall performance
  16. If using clustering, make one Exchange cluster node on one Root, and the other node on another Root to truly achieve high availability
  1. June 18, 2014 at 8:42 am

    Wow that was unusual. I just wrote an incredibly long comment but after I clicked submit my comment didn’t appear.
    Grrrr… well I’m not writing all that over again. Anyways, just wanted to say excellent blog!

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: