Hi, We have two datacanter. DatacenterA have the Exc2007 CCR (Sp3 Rollup6) and DatacenterB have one SCR node (Sp3 Rollup6) (just passive cluster node). When the SCR node is down and then full backed up CCR in DatacenterA (the fact that the backed up storage group), deleting log files did not yet replicated to the SCR and storage group copy status seems to be "Failed" instead "ServiceDown". is this normal? because every time we have to reseeding with Update-StorageGroupCopy and this takes quite some time.

Hello, Thank you for your post. This is a quick note to let you know that we are performing research on this issue. Thanks,Simon Wu TechNet Community Support

hi, Per my experience, both "Failed" and "ServiceDown" can be caused by network issue, I think this is normal behavior since the server is down totally.

Hi Sun, When the SCR target server is down, SummaryCopyStatus is normal behavior "Failed" or "ServiceDown". But why did not transfer log files are deleted but not yet? Does not have to store the log files on CCR until the SCR Target server is online?

Hi Thom, exchange will not delete the transaction log files if they have not been replicated to passive node and SCR node. If the SCR node is not used currently, please remove the copies on the node so that full/incremental backup can purge the committed transaction log files automatically.

Hello , Did the answers help you? Let us know if you need further assistance from us.

the problem starts exactly at that point :) When the SCR passive node is down and when backing up inthe SCR active node (full backup), purge the uncommitted transaction log files automatically.

Hi did the issue persist if you remove copies on SCR node or bring SCR node online and ensure the state is in health?