We had failed data base copies on a CCR cluster and running Update-StorageGroupCopy failed. The backups have not run for a while but I could verify that the logs were indeed present. The best way to get around this is to run an Exchange backup and the Update the Storage Group Copy. This was not possible as wee needed to urgently get the database copies healthy. We then had to dismount all the databases, checked that they are in a clean shut down state using eseutil.exe /mh and move the logs to a different folder. We then mounted the databases and were then able to seed the database copies.
We had an Exchange 2007 CCR cluster where the passive node databases stopped seeding. After some investigation we noticed that the Exchange Replication Service starts and a second or two later stops. The event log did not give us much information, only stating that the service started and stopped again. We checked all the databases on the passive node and noticed that they were in a dirty shut down state as the logs stopped replaying to the database a few days earlier. Resolution that worked for us: 1. Move each database to a new folder on the disk that it resides. 2. Start the Exchange Replication Service. (We monitored the…