Hello, I'm running an Exchange 2007 CCR environment. We have 5 SG's currently, and the 5th one does not appear to be happy. I noticed this morning that the full DB backup failed on DB5 with error: Event 459: MSExchangeIS (7296) Fifth Storage Group: The file M:\Fifth Storage Group\E0400007443.log is missing and could not be backed-up. Event 214: MSExchangeIS (7296) Fifth Storage Group: The backup has stopped with error -569. Incrementals work fine however, and that log file no longer exists. Then, I received a report from one of our techs that they tried to create a user with a mailbox but when they try editing the user account they can't click on any tabs and the console locks up. I've tested and confirmed that the same things happen when I try to access that user. Additionally, I've tried a few other users in DB5 and some of them cause the same problem (but not all). To clarify further on this, basically accessing the Properties on the mailbox hangs at the General tab and no data is populated so everything is blank. Using the Shell, I can pull up the full details on the user accounts that lockup the console. I ran the DB troubleshooter but it didn't give me any errors. Event viewer also does not show any DB related errors other than the Backup failure above. I'm tempted to try dismounting/mounting the store, but since It's mid-day and I haven't heard of any complaints from users in those DB's, I'd rather not try that until later. Any idea what could be causing this? Thanks,Matt

So at noon I noticed the queues on our Hub transports were suddenly filling up, most of which were related to emails destined to DB5. I tried cutting over from one Hub transport to another (restarting the hub transport service) and though it cutover successfully the other Hub's queue started filling. I then went to cutover the cluster to the other node, that's when it became very apparent there were issues with DB5. It failed to mount, so the DB engine "initiated recovery steps" andstarted replaying all of the log files to it and then mounted it successfully. The queues are now flowing and everything appears to be alright, I'm also able to open up the Properties on the mailboxes that I couldn't view before. Here are a few key entries in the event viewers during this time (In order of most recent from the top)... Log file E0400007A25.log in exchange2007bby\Fifth Storage Group could not be replayed. Re-seeding the passive node is now required. Use the Update-StorageGroupCopy cmdlet in the Exchange Management Shell to perform a re-seed operation. Microsoft.Exchange.Cluster.ReplayService (3152) Recovery E04: Database recovery/restore failed with unexpected error -543. Microsoft.Exchange.Cluster.ReplayService (3152) Recovery E04: Database L:\database\Fifth Storage Group\mailboxdbsg5.edb requires logfiles 30228-31268 in order to recover successfully. Recovery could only locate logfiles up to 31212. Now, I'm not too sure why it told me to reseed using update-storagegroupcopy when it went ahead on its own to replay all of the logs and mount the database? I've checked and the Copy Status is Healthy. As for a cause for this... we did have the node that was hosting this database crash mid-day (last week) due to a hardware error. It successfully cutover to the other node though, but could it still have potentially corrupted that DB? Is there anything additional I should do at this point? Thanks, Matt

Matt, I am having the same errors in nearly the same environment. I have a healthy copy on my failover node. Did you have any additional problems failing over? If you don't mind, let me know if I should be expecting anything to go wrong.