Microsoft Exchange Disaster Recovery with Site Resilience
Messaging services are mission-critical or business-critical to all organizations. If the messaging system is not available, productivity can be lowered, and business and revenue opportunities can be lost. Even though site resilience is only one means of Exchange Server Disaster Recovery, in this post, we are focusing on the site resilience part of the Exchnange 2007 Disaster Recovery strategy. Site Resilience is highly important for organizations with multiple offices in different locations and all offices are relying on the same Exchange Servers, which will be the typical setup involved in most of the organizations. Site resilience will be useful in situation where the Primary datacenter is down or lost connectivity for a long duration which is not acceptable for the business to go with out Email.
Exchange 2007 SP1 has a very much avaited feature, named Standby Continuous Replication (SCR), which was only available with third party products. In Exchang 2007 SP1, microsoft has intgrated the Disaster Recovery feature to the Microsoft Exchange product itself. By integrating the Site Resilience in Exchange Server itself, Administrators has the advantage of managing the Exchange Server disaster recovery with in Exchange Server framework and avoiding third party support overheads.
SCR allows you to replicate your Exchange database information from your production servers to a standby server that can be brought online should the production servers be lost. Although existing Exchange 2007 technologies such as Clustered Continuous Replication (CCR) offer high availability, site resilience is something currently best achieved via SCR.
SCR enables a separation of high availability and site resilience. For example, SCR can be combined with CCR to replicate storage groups locally in a primary datacenter (using CCR for high availability) and remotely in a backup datacenter (using SCR for site resilience).
Sources and Targets
Messaging services are mission-critical or business-critical to all organizations. If the messaging system is not available, productivity can be lowered, and business and revenue opportunities can be lost. Even though site resilience is only one means of Exchange Server Disaster Recovery, in this post, we are focusing on the site resilience part of the Exchnange 2007 Disaster Recovery strategy. Site Resilience is highly important for organizations with multiple offices in different locations and all offices are relying on the same Exchange Servers, which will be the typical setup involved in most of the organizations. Site resilience will be useful in situation where the Primary datacenter is down or lost connectivity for a long duration which is not acceptable for the business to go with out Email.
Exchange 2007 SP1 has a very much avaited feature, named Standby Continuous Replication (SCR), which was only available with third party products. In Exchang 2007 SP1, microsoft has intgrated the Disaster Recovery feature to the Microsoft Exchange product itself. By integrating the Site Resilience in Exchange Server itself, Administrators has the advantage of managing the Exchange Server disaster recovery with in Exchange Server framework and avoiding third party support overheads.
SCR allows you to replicate your Exchange database information from your production servers to a standby server that can be brought online should the production servers be lost. Although existing Exchange 2007 technologies such as Clustered Continuous Replication (CCR) offer high availability, site resilience is something currently best achieved via SCR.
SCR enables a separation of high availability and site resilience. For example, SCR can be combined with CCR to replicate storage groups locally in a primary datacenter (using CCR for high availability) and remotely in a backup datacenter (using SCR for site resilience).
Sources and Targets
The starting point for SCR is called the source, which is any storage group on any of the following:
- Stand-alone Mailbox server
- Clustered mailbox server in a single copy cluster (SCC)
- Clustered mailbox server in a CCR environment
The endpoint for SCR is called the target, and the target can be either of the following:
- Stand-alone Mailbox server that does not have LCR enabled for any storage groups
- A standby cluster, which is a failover cluster where the Passive Clustered Mailbox role is installed, but no clustered mailbox server (e.g., no Active Clustered Mailbox role) has been installed in the cluster
Cheers
EDB recovery owns all necessary facilities, which allowing to parse corrupted edb files and repair theirs. It doesn't modify damaged email database during the process of recovering. The program using contemporary methods of restoration edb files.
ReplyDelete