Requirements for virtualizing Exchange Server 2010

Transcription

1 Requirements for

2 Exchange : Hardware Microsoft Exchange Server is one of the most mission-critical IT services for many enterprises. Yet while isn t difficult, it must be done properly to ensure success. This e-guide, from SearchServerVirtualization.com, explores the hardware, storage and memory requirements for Exchange virtualization. Also, discover other important considerations for such as how to select the right hypervisor. : Hardware requirements and By: Brien M. Posey When, administrators must provision servers with adequate resources, while at the same time adhering to Microsoft s requirements. It s something of an art form. Hardware requirements only scratch the surface. also requires attention to storage requirements, memory considerations and fault tolerance. Hardware requirements for The hardware requirements for Exchange vary greatly depending on the server roles installed on the anticipated workload. As such, the minimum hardware requirements on Microsoft s website are often completely inadequate. Determining the hardware requirements for most Exchange Server roles is fairly straightforward. There are numerous TechNet articles that can guide you through the planning process. Hardware planning for the mailbox server role is the most difficult, especially in large deployments. The best way to accurately estimate the role s hardware requirements is to use the Exchange 2010 Mailbox Server Role Requirements Calculator. Page 2 of 9

3 Exchange : Hardware As you plan hardware allocation for virtualized Exchange servers, it is important to remember that Microsoft does not differentiate between physical and virtual deployments of Exchange. The hardware requirements are the same regardless of whether you run Exchange on physical hardware or in virtual machines (VMs). Storage requirements for Storage requirements are also a consideration when. You can configure Exchange to use virtual hard disks that reside locally on the server, or you can connect to a remote storage mechanism through iscsi. Exchange also supports SCSI pass-through disks. If you use virtual hard drives for Exchange Server storage, they must be a fixed size. Microsoft does not support dynamically expanding virtual hard drives with Exchange Server. (This isn t really an issue with VMware, because VMware uses fixed-length virtual hard disks by default.) If you plan to use iscsi connectivity, make sure the virtual Exchange server uses a full-featured network stack. If the server does not support the use of jumbo frames, for example, then storage performance may be greatly diminished. Memory considerations when Exchange has always been an I/O intensive application, but one of Microsoft s major design goals in Exchange was to drive down the I/O requirements. With fewer I/O requirements, it is practical to virtualize Exchange mailbox servers. But in order to achieve decreased I/O levels, Exchange 2010 is designed to use large amounts of memory. That means efficient memory use is critical to the server s performance. You should avoid using memory overcommit or Dynamic Memory when. Memory overcommit works well for servers that occasionally need extra memory to perform an operation and release that memory when the task is complete. Exchange, however, is a Page 3 of 9

4 Exchange memory-hungry application, and the Mailbox Server role usually consumes all the memory that it can. : Hardware No snapshots allowed One of the most important things to know about Server 2010 is that it doesn t support VM snapshots. Snapshots make a point-intime copy of the VM to be used for backup and recovery. In Exchange, the Mailbox Server, Hub Transport Server, and Edge Transport Server roles all use highly transactional internal databases. Using snapshots to revert a virtualized Exchange server to a previous state could therefore have disastrous consequences, especially in organizations that use multiple Exchange servers. Fault tolerance Before the release of Service Pack 1 (SP1), Microsoft didn t support combining Exchange Server database availability groups with hypervisorlevel clusters. Exchange SP1 supports this configuration, but with some limitations. VMs must be configured so that their state is never saved or restored when the VM is taken offline or when a failover occurs. With all the hardware resource-allocation considerations, can be a juggling act. VMware (PDF) and Microsoft have released best practices for on their hardware platforms. By: Greg Shields Microsoft Exchange Server is one of the most mission-critical IT services for many enterprises. When mail servers are down, so is the entire business communication infrastructure. combines the server s high-availability features with all of the benefits that virtualization brings to Windows servers. Page 4 of 9

5 Exchange : Hardware The steps involved in creating a virtual Exchange 2010 server aren t all that different from those used to create a physical one. The primary difference lies with the creation of a virtual machine (VM). The real planning takes place in these five steps you need to do before you even click New -> Virtual Machine. Step 1: Select and verify a hypervisor Microsoft doesn t support every configuration of Exchange Server running on a hypervisor. The company recognizes that Exchange is a high-priority workload that consumes a lot of resources, so it places limits on what it allows you to virtualize. Microsoft supports Exchange 2010 on hypervisors that have been validated by the Windows Server Virtualization Validation Program. Microsoft hasn t validated every virtual platform, but most major products have been approved, including Microsoft Hyper-V R2, VMware vsphere ESXi 4.1 and XenServer 5.6. Verify that your hypervisor is on the list. Step 2: Determine your virtual Exchange design Even if you re using an approved hypervisor, not all Exchange designs are supported in virtual environments. Microsoft will support Exchange Server 2010 on production hardware only when the following conditions are true: The VM is running Windows Server 2008 SP2 or Windows Server 2008 R2. Microsoft will likely recommend Windows Server 2008 R2 SP1 once it has been released. The VM is not running the Unified Messaging (UM) server role. Microsoft supports each of Exchange s other server roles in a virtual environment, but has concerns about performance for virtualized UM. A UM server requires substantial processing power with little tolerance for processing latency, which may not be guaranteed in a virtual environment. In short, keep your UM servers physical -- at least for now. The virtual machine is not using dynamically expanding virtual hard disk files such as VHD or VMDK files. Disk files can be either SCSI pass- Page 5 of 9

6 Exchange through or iscsi, but must be block-level storage. Microsoft does not support the use of network-attached storage (NAS) for Exchange Server. : Hardware The VM does not use differencing disks, delta disks, linked clones or hypervisor-layer snapshots. These mechanisms link virtual hard disks to create dependencies that could affect Exchange functionality and possibly cause it to fail down the road. Pay particular attention to the lack of support for disk snapshots; you should never create hypervisor-layer snapshots of an Exchange server s disks. The number of assigned virtual processors should never exceed two times the number of logical processors on the physical host. This 2:1 ratio refers to the number of virtual processors that have been assigned to all colocated VMs on the host. In this calculation, logical processors represent the number of processors per core times the number of cores on the server. Step 3: Provision storage for Exchange data stores Exchange needs processing and memory resources to accomplish its job, but storage provisioning is another important consideration. You ll not only need to determine how much storage to provision, but also how that storage will be presented to the server. Two mechanisms are common among essentially all hypervisors. 1. The creation and presentation of a virtual hard disk: This encapsulated storage brings the benefits of virtualized disks to your Exchange design. It can, however, introduce complexities with your backup schemes and incur a slight loss of performance over raw disks. Encapsulation also tends to create extremely large virtual hard disks that become difficult to manage in the long run. 2. The creation and presentation of raw storage such as a SCSI passthrough disk or Raw Disk Mapping: Raw disks do not see the benefits of virtual hard disks, but they may be easier for backup and restore, depending on the capabilities of your backup solution. Additionally, they don t experience the same complexities that virtual hard disks do as they grow. Microsoft supports both types of disks Page 6 of 9

7 Exchange for Exchange storage; however, it recommends the use of raw storage when it s feasible. : Hardware 3. With Exchange Server 2007, Microsoft did not support the direct connection of iscsi storage into the VM. The official support guidelines have changed with Exchange 2010, now allowing iscsi direct connections into virtual machines. However, even though it now allows this configuration, Microsoft does not recommend using it because the network stack inside the VM isn t fully featured. It does not include the kinds of network accelerations enjoyed by physical hosts. You will get optimal performance and full supportability when iscsi storage is configured on the host machine and presented to the VM as a pass-through disk. 4. For information, check out Microsoft s full storage support statement under the section titled Hardware Virtualization. 5. Step 4: Design Exchange Server for high availability High-availability options are built into Exchange Server with database availability groups (DAGs). They are also internal to the hypervisor via live migration. Microsoft doesn t support the use of both high-availability approaches in combination. More importantly, DAG cluster node failures during a live migration have been reported. 6. Live migration and DAGs are complementary technologies; both aim to accomplish the same task but do so at different levels of the application stack. Live migration works at the level of the entire VM. DAGs, on the other hand, are application-specific instances of database clustering. 7. DAGs provide a superior level of service specific to Exchange. You can create multiple DAGs for each data store. DAGs can also be tiered to support failover and disaster recovery situations as well as the additional requirements of data archival. Thus, experts often suggest that virtualized Exchange environments leverage DAGs over and above live migration as a solution for database high availability. 8. Step 5: Guarantee Exchange Server performance Virtualization makes financial sense because it allows multiple VMs Page 7 of 9

8 Exchange to share physical server resources. However, the laws of physics always apply. : Hardware 9. Exchange s various server roles can require substantial processing power and memory to accomplish their tasks without taking a performance hit. On the other hand, combining too many VMs on the same server can create contention as they vie for resources. 10. Your virtualized Exchange design should effectively monitor server performance to ensure that resource contention does not occur. Make sure Exchange has a minimum service level by setting resource reservations -- minimum levels of resources guaranteed to specific servers. 11. And since Exchange is memory-intensive, ensuring that hypervisor memory overcommitment doesn t affect the server s memory needs will also preserve its service levels. Don t overcommit host memory until Exchange s memory usage stabilizes and you have a good understanding of how much memory it actually needs. 12. Once you ve completed these five planning steps, you can begin clicking through the virtual Exchange installation. Choosing New -> Virtual Machine is, for the most part, the only extra step you need. Page 8 of 9

9 Exchange : Hardware Free resources for technology professionals TechTarget publishes targeted technology media that address your need for information and resources for researching products, developing strategy and making cost-effective purchase decisions. Our network of technology-specific Web sites gives you access to industry experts, independent content and analysis and the Web s largest library of vendor-provided white papers, webcasts, podcasts, videos, virtual trade shows, research reports and drawing on the rich R&D resources of technology providers to address market trends, challenges and solutions. Our live events and virtual seminars give you access to vendor neutral, expert commentary and advice on the issues and challenges you face daily. Our social community IT Knowledge Exchange allows you to share real world information in real time with peers and experts. What makes TechTarget unique? TechTarget is squarely focused on the enterprise IT space. Our team of editors and network of industry experts provide the richest, most relevant content to IT professionals and management. We leverage the immediacy of the Web, the networking and face-to-face opportunities of events and virtual events, and the ability to interact with peers all to create compelling and actionable information for enterprise IT professionals across all industries and markets. Related TechTarget Websites Page 9 of 9