Many of you have been wondering how continuous replication works in Exchange 2007. The Continuous Replication Deep Dive whitepaper discusses how log shipping, log inspection, and log replay work w...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Pesos,
Glad you were able to correct your issue and allow for all of your storage groups to replicate to the SCR target.
At this time we are not providing a means to perform an Exchange aware backup for SCR targets in Exchange 2007. What I highlighted in the paper (suspend replication, take backup, resume replication) is what you can do if you want to backup your SCR target copies.
Choosing to do SCR or geographically dispersed CCR requires a lot of thought and planning. Things to keep in mind when doing geographically dispersed CCR:
1. If using Windows 2003 as the base OS, you must span the subnet between the datacenters. If using Windows 2008, you can use different subnets (but now you must deal with DNS replication). Also, regardless of which OS you choose, you must span the AD site between the datacenters.
2. Hub Transport and CAS placement. You may have to move servers in and out of the AD site to ensure that the CMS only communicates with local HT and CAS boxes. Otherwise, requests may go to either datacenter which could become a problem as latency and throughput will affect the experience (remember that both HT<->MBX and CAS<->MBX communication is RPC and it is not WAN optimized).
3. Failovers/Handoffs. Whenever you have to perform a hand-off (say for security patch) you now have to go out of your primary datacenter. Failovers may not be automatic (depends on the why the failover is occuring and where the file share witness exists and whether it is accessible).
4. Log replication cannot get behind. If it does, then that storage group may not be able to mount (RTO hit) and a reseeding may be requiredo on the passive node if you manually mount the database.
Ross
Glad you were able to correct your issue and allow for all of your storage groups to replicate to the SCR target.
At this time we are not providing a means to perform an Exchange aware backup for SCR targets in Exchange 2007. What I highlighted in the paper (suspend replication, take backup, resume replication) is what you can do if you want to backup your SCR target copies.
Choosing to do SCR or geographically dispersed CCR requires a lot of thought and planning. Things to keep in mind when doing geographically dispersed CCR:
1. If using Windows 2003 as the base OS, you must span the subnet between the datacenters. If using Windows 2008, you can use different subnets (but now you must deal with DNS replication). Also, regardless of which OS you choose, you must span the AD site between the datacenters.
2. Hub Transport and CAS placement. You may have to move servers in and out of the AD site to ensure that the CMS only communicates with local HT and CAS boxes. Otherwise, requests may go to either datacenter which could become a problem as latency and throughput will affect the experience (remember that both HT<->MBX and CAS<->MBX communication is RPC and it is not WAN optimized).
3. Failovers/Handoffs. Whenever you have to perform a hand-off (say for security patch) you now have to go out of your primary datacenter. Failovers may not be automatic (depends on the why the failover is occuring and where the file share witness exists and whether it is accessible).
4. Log replication cannot get behind. If it does, then that storage group may not be able to mount (RTO hit) and a reseeding may be requiredo on the passive node if you manually mount the database.
Ross