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 24 hours of Dependent on specific failure time of failure live data scenario Single database failure 4 hours from 5 minutes of 1.) Activate a passive database time of failure live data copy 2.) Recover from backup system Multiple database failure on 8 hours from 5 minutes of 1.) Activate a passive database single server time of failure live data per copy database 2.) Recover from backup system Single HUB server failure 15 minutes 5 minutes of 1.) Alternate server live data 2.) Build new server to replace failed server Multiple HUB server failure 4 hours 1 hour of live 1.) Build new servers to replace data 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 1.) Activate replicated database live data copies 2.) Build new server to replace failed server Multiple MBX server failure 4 hours 15 minutes 1.) Build new servers to replace of live data 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.
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.
467c984d85b41842e63287d5deafdbf7_MOFA%20Exchange%202010%20Design.docx