Beta 2 of Service Pack 1 Exchange Server 2007 is available for public download and preview for MSDN and TechNet subscribers. As I wrote in my blog entry, Standby Continuous Replication in Exchange ...
Updated Jul 01, 2019
Version 2.0
Blog Post
BestofHarish,
1. SCR introduces the concept of multiple 'storage group copies'. Whereas with LCR and CCR, you only have two copies of each storage group (the active and the passive) with SCR, you can have additional storage group copies (which we call SCR targets).
2. I'm not sure what you are saying here. An SCR target copy cannot be backed up. SCR targets copies only get their updates which come from the logs shipped by the Replication service.
3. Restore-storagegroupcopy is not part of database portability. It is a continuous replication function. Basically, we clean up the replay states for replication so that the target can be configured as a replication source. Restore-SGC attempts to copy all remaining log files and close the storage group. We also mark the database as mountable by updating the MountAllowed flag.
4. All logs that are shipped are checked for corruption and undergo database signature validation before they are replayed. Continuous replication will not replay a corrupt log file into a database copy. The idea is that logs are shipped immediately; they are just not replayed immediately.
5. As with all three forms of continuous replication, the logs will be on the SCR target computer in the path for the log files for the storage group copy. See http://blogs.technet.com/scottschnoll/archive/2006/10/30/More-on-Continuous-Replication.aspx for some more information on this.
6. Why would you want to? That is the whole point of SCR; to give you a viable, online copy in the event you lose your original. The log files will be checked for corruption, and if corruption is found they will not be replayed into the copy of the database.
Have a look at http://technet.microsoft.com/en-us/library/bb676502.aspx for more information on SCR.
1. SCR introduces the concept of multiple 'storage group copies'. Whereas with LCR and CCR, you only have two copies of each storage group (the active and the passive) with SCR, you can have additional storage group copies (which we call SCR targets).
2. I'm not sure what you are saying here. An SCR target copy cannot be backed up. SCR targets copies only get their updates which come from the logs shipped by the Replication service.
3. Restore-storagegroupcopy is not part of database portability. It is a continuous replication function. Basically, we clean up the replay states for replication so that the target can be configured as a replication source. Restore-SGC attempts to copy all remaining log files and close the storage group. We also mark the database as mountable by updating the MountAllowed flag.
4. All logs that are shipped are checked for corruption and undergo database signature validation before they are replayed. Continuous replication will not replay a corrupt log file into a database copy. The idea is that logs are shipped immediately; they are just not replayed immediately.
5. As with all three forms of continuous replication, the logs will be on the SCR target computer in the path for the log files for the storage group copy. See http://blogs.technet.com/scottschnoll/archive/2006/10/30/More-on-Continuous-Replication.aspx for some more information on this.
6. Why would you want to? That is the whole point of SCR; to give you a viable, online copy in the event you lose your original. The log files will be checked for corruption, and if corruption is found they will not be replayed into the copy of the database.
Have a look at http://technet.microsoft.com/en-us/library/bb676502.aspx for more information on SCR.