Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've been experiencing problems with a exchange database after removing and readding it to a passive node. After a total reseed which also deleted the old files i ran into an error telling me that one of the transaction logs wasn't present any more.

After a lot of googling and reading on technet I found the answer to be in doing the Update-MailboxDatabaseCopy -CatalogOnly command on the failed database. However, the DB have now been stuck in "Reinitializing" for a good two hours. I understand that this is probably quite normal on a 100-300Gb database with ~8Gb of CatalogData.

So, I still can't help to wonder - is it normal for the resynchronization to take this long. If yes - what is a reasonable time estimate for the resynchronization?

Brgds, Simon

share|improve this question
    
And if this is actually NOT normal behaviour. How do I get the database to go from resynchronizing to Healthy? –  Simon Aronsson Jul 20 '12 at 14:51
    
Are you seeing any progress in EMC? Copy Queue Length on the Database? Are there any Eventlog entries? If it is stalled, try to restart the Mailbox Replication Service on the target server. –  MichelZ Jul 21 '12 at 8:40

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.