MOFA is in the process of upgrading their email systems from Exchange 2007 to Exchange 2010. This document outlines the infrastructure solution for the Exchange 2010 project. Purpose The purpose of this document is to detail the solution concept for MOFA’s Exchange 2010 environment. It provides an overview of the solution as well as a more detailed description of server configurations that must be implemented to meet MOFA’s solution requirements. Key issues that this design addresses include: To develop an Exchange Server 2010 Infrastructure capable of providing stable, high available and reliable Messaging Services for the next 3 years to MOFA’s user population. To design a high performance cost effective messaging foundation that will support the business requirements for 3 years. To develop an Exchange 2010 environment that addresses the needs of the users within the existing MOFA Exchange 2007 environment. To co-exist with MOFA’s current Exchange 2007 system during a migration period. This includes providing the ability for users on both systems to send messages to each other, find users, schedule appointments, and determine free/busy status. The requirement to provide a consistent user experience throughout the migration for all users The ability to extend the Exchange 2010 design to support future requirements, e.g. Unified Communication or Site Resilience or for rapid growth in user count. Audience This document is intended for personnel associated with MOFA’s Exchange 2010 deployment, including: MOFA Staff Microsoft Account Team Vendor’s providing hardware to MOFA’s Exchange environment This document has been prepared for a technical audience.
(FC) SANs. FC disks are available in a variety of speeds and capacities. In general, choose FC disks for Exchange 2010 mailbox storage when you have the following design requirements: Moderate capacity High performance SAN connectivity use 512-byte emulation, are currently not supported. Physical disk-write caching must be disabled when used without a UPS. Solid-state drive (SSD) (flash disk) An SSD is a data storage device that uses solid-state memory to store persistent data. An SSD emulates a hard disk drive interface. SSD disks are available in a variety of, speeds (different I/O performance capabilities) and capacities. In general, choose SSD disks for Exchange 2010 mailbox storage when you have the following design requirements: Low capacity Extremely high performance Supported: 512 byte sector disks only. 4KB sector disks, including those which use 512-byte emulation, are currently not supported. Physical disk-write caching must be disabled when used without a UPS. In general, Exchange 2010 Mailbox servers don't require the performance characteristics of SSD storage. Factors to Consider in Choosing Disk Types There are several trade-offs when choosing disk types for Exchange 2010 storage. The correct disk is one that balances performance (both sequential and random) with capacity, reliability, power utilization, and capital cost. The following table of supported physical disk types provides information to help you when considering these factors. Disk speed (RPM) Disk form Capacity Random I/O I/O Power utilization 5,400 SATA Average Poor Poor Excellent
class Best Practice for Supporting Storage Configuration Redundant Array of Independent Disks (RAID) is often used to both improve the performance characteristics of individual disks (by striping data across several disks) as well as to provide protection from individual disk failures. With the advancements in Exchange 2010 high availability, RAID is no longer a required component for Exchange 2010 storage design. However, RAID is still an essential piece to Exchange 2010 storage design for stand-alone servers as well as high availability solutions that require either additional performance or greater storage reliability. The following table provides guidance for the common RAID types that can be used with the Exchange 2010 Mailbox server. Data type Stand-alone: supported/best practices High availability: supported/best practices OS/System/Pagefile Volume All RAID types supported. Best practice: RAID 1/10. All RAID types supported. Best practice: RAID 1/10. Exchange Mailbox Database File (EDB) Volume All RAID types supported. Best practice: 5,400/7,200 disks = RAID1/10 only. All RAID types supported. Just a bunch of disks (JBOD)/Raidless supported (3 or more database copies). Best practice: 5,400/7,200 disks = RAID1/10 only or JBOD. Best practice: When lagged, database copies should have either two or more lagged copies or lagged copies should be protected with RAID. Exchange Mailbox Database Log Volume All RAID types supported. Best practice = RAID1/10. All RAID types supported. JBOD/Raidless supported (3 or more database copies). Best practice = RAID1/10. Best practice: When lagged database copies should have either two or more lagged copies or lagged copies should be protected with RAID.
Log truncation method The process for truncating and deleting old database log files. There are two mechanisms: Circular logging, in which Exchange deletes the logs. Log truncation, which occurs after a successful full or incremental Volume Shadow Copy Service (VSS) backup. Best practice: Use backups for log truncation (for example, circular logging disabled). Provision for three days of log generation capacity. Best practice: Enable circular logging for deployments that use Exchange data protection features. Provision for three days beyond replay lag setting of log generation capacity. More information can be found in this URL:
MOFA SLA & MOFA SLA Currently MOFA does not have an SLA for E-Mail Services. The following table lists the failure conditions for Microsoft Exchange Server 2010 deployment @ MOFA and the actions that can be taken to mitigate these failures. Failure Scenario RTO RPO Recovery Approach Overall Messaging Service 12 hours from time of failure 24 hours of live data Dependent on specific failure scenario Single database failure 4 hours from time of failure 5 minutes of live data 1.) Activate a passive database copy 2.) Recover from backup system Multiple database failure on single server 8 hours from time of failure 5 minutes of live data per database 1.) Activate a passive database copy 2.) Recover from backup system Single HUB server failure 15 minutes 5 minutes of live data 1.) Alternate server 2.) Build new server to replace failed server Multiple HUB server failure 4 hours 1 hour of live data 1.) Build new servers to replace failed servers Single CAS server failure 15 minute NA 1.) Alternate server behind load balancer 2.) Build new server to replace failed server Multiple CAS server failure 4 hours NA 1.) Build new servers to replace failed servers Single MBX server failure 15 minute 5 minutes of live data 1.) Activate replicated database copies 2.) Build new server to replace failed server Multiple MBX server failure 4 hours 15 minutes of live data 1.) Build new servers to replace failed servers MOFA High Availability Design Mailbox Databases high availability will be achieved by using DAG in MOFA, MOFA will have three copies of each database hosted in three mailbox servers. Windows Network Load Balancing will be used to achieve high availability for CAS Services. The HUB server role is load balanced internally through Exchange.
Exchange 2010 Backup To back up and restore Exchange 2010, you must use an Exchange-aware application that supports the VSS writer for Exchange 2010, such as Windows Server Backup (with the VSS plug-in), Microsoft System Center Data Protection Manager, or a third-party Exchange-aware VSS-based application. Be aware of these limitations when using VSS for backup and restore of Exchange data: The VSS plug-in that ships with Exchange 2010 can be used to back up volumes containing active mailbox database copies or standalone (non-replicated) mailbox databases only. It can't be used to back up volumes containing passive mailbox database copies. To back up passive mailbox database copies, you need either Microsoft System Center Data Protection Manager or a third-party Exchange-aware VSS-based application. Passive mailbox database copies are backed up using a separate VSS writer in the Microsoft Exchange Replication service. The Microsoft Exchange Replication service VSS Writer doesn't support restores. Although you can back up a passive mailbox database copy using Microsoft System Center Data Protection Manager or a third-party Exchange-aware VSS-based application, you can't perform a VSS restore directly to a passive mailbox database copy. However, you can perform a VSS restore to an alternate location, suspend replication to the passive copy, and then copy the database and log files from the alternate location to the location of the passive database copy in the file system. MOFA will utilize its NetBackup solution to take backups of its Exchange 2010 Databases. A daily incremental and weekly full backup’s strategy will be used. Backups can be taken from the database passive copy. Below is the suggested backup strategy for MOFA databases For more information about Exchange 2010 Backups, please go to this URL