![]() The SCR source and SCR target are closer together in time because of the missing log files on the SCR source. After a lossy failover, log files are missing on the new active storage group. ![]() This delay minimizes the likelihood that a reseed is necessary after a lossy failover in a LCR/CCR deployment. You cannot configure X because it is a fixed value. Therefore, the actual replay lag time is the maximum of ReplayLagTime or “X log files,” where X is 50 in the current Exchange Server 2007 build. Users with mailboxes in the SCR-enabled storage group must send and receive new emails so that new log files are created on the SCR source and shipped to the SCR target before the database will be created on the SCR target. This is also the case when you SCR enable a storage group Exchange does not create the initial SCR target database until at least 50 log files have been shipped. In addition to this lag time, Exchange verifies that a minimum of 50 log files have been shipped to the SCR target before it replays a log file to the target database. ![]() The format of the value is Days.Hours:Minutes:Seconds. The default value is 24 hours and the maximum delay is 7 days. ReplayLagTime specifies the time the Replication service has to wait until a copied log file is replayed into the SCR target database. ![]() You can use the following parameters to fine-tune SCR:
0 Comments
Leave a Reply. |