I came across this today. I have no idea why the database failed to replicate correctly, especially as it was a new database with no users on it. However fixing it was fairly trivial.
The issue:
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxjag0D5uubjYw-WtsLWYNg73Dsqjk_IdKSDnspe-uRocB2CL7EGrE5CK1_cV5W2200EEY3sJsHisM1r4EKTUUU3j643GqOvp_T6EAKJTr-FWqGQO8iU4vos-rXBDU48O9I5mE5CFYRyQ/s320/1.jpg)
The issue:
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxjag0D5uubjYw-WtsLWYNg73Dsqjk_IdKSDnspe-uRocB2CL7EGrE5CK1_cV5W2200EEY3sJsHisM1r4EKTUUU3j643GqOvp_T6EAKJTr-FWqGQO8iU4vos-rXBDU48O9I5mE5CFYRyQ/s320/1.jpg)
Once I was back in the console I actually couldn't see the suspended and failed copy without having to restart EMC (a refresh would not work) however EMS did infact show it:
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4P87itlpFfALYcqJMKDMhDfcDF17HBKPR1e0F_Z4xhSLQRLKgVJYseO_uKFHocU30FxXp0qoZp216tOmFKASRX-DJmj8npJJr6PkrNrrL1fZ5x2zzNQPV7qHo_FokjyIEkX1CDvLK0_w/s320/2.jpg)
So via Powershell I simply ran the Resume-MailboxDatabaseCopy and this fixed the issue.
Testing via EMC I noticed once it was restarted I was able to see the failed and suspended database so could have performed it via the UI if I needed too.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhEytP1Fb2-ITz53Q_xa6nCp_wDiqEuSTs5fwNigJlgSEm2pFZ8M9QckvCUBposshvO_eql7P4MzHeCjLnXjWKxYneiEXOS-5oXUmhNAvjS1MIRQ5-QHa7mZ7F21pIuHmaDjuIbYQRKWPs/s320/3.jpg)
Root cause analysis was not done as I was unable to replicate the issue. Hopefully this article will help any other Admins with the issue that may not be quite as quick at fixing it.
No comments:
Post a Comment