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
Hi Scott,
While we enable SCR, what do you mean by 50 logfiles & 24 hours lag delay? What if i have 500 logfiles? Also, being asynchronous replication, what does this delay refer to? Shouldn't it replicate once the logfile is closed as with lcr/ccr?
Where do we mention the files/locations on the scr target to get the data replicated from the source scr? thats not clear. Target server doesn't show the target sg/mb anywhere before we switch to recovery objects, but where do we have being them replicated? The enabling of scr is done but recovery sg/mb is being created afterwards, & could be created after disaster as well. Where are the target paths?
Wwat names & paths necessarily be provided to create recovery objects (sg & db) ahead of disaster to facilitate database portability? What association do they have with Active Directory, for which we are deleting them after we create them?
Ofcourse, after the active is corrupted, it is unavailable. In that event, utlook 2007 clients would be able to access the new paths after DS replication. But do you mean outlook 2003 or earlier clients, all manual intervention is required?
While we enable SCR, what do you mean by 50 logfiles & 24 hours lag delay? What if i have 500 logfiles? Also, being asynchronous replication, what does this delay refer to? Shouldn't it replicate once the logfile is closed as with lcr/ccr?
Where do we mention the files/locations on the scr target to get the data replicated from the source scr? thats not clear. Target server doesn't show the target sg/mb anywhere before we switch to recovery objects, but where do we have being them replicated? The enabling of scr is done but recovery sg/mb is being created afterwards, & could be created after disaster as well. Where are the target paths?
Wwat names & paths necessarily be provided to create recovery objects (sg & db) ahead of disaster to facilitate database portability? What association do they have with Active Directory, for which we are deleting them after we create them?
Ofcourse, after the active is corrupted, it is unavailable. In that event, utlook 2007 clients would be able to access the new paths after DS replication. But do you mean outlook 2003 or earlier clients, all manual intervention is required?