In my previous blog post on Implementing and Configuring AutoReseed I’ve explained how to implement and configure AutoReseed in a Database Availability Group. In this blogpost I will explain what happens when a disk fails and AutoReseed kicks in.
Recently I had to implement and configure AutoReseed in Exchange 2013 and it wasn’t as easy as I figured in Advance. To be honest, I had to rebuild the DAG after fiddling too much with the Mailbox servers so it might well be a good idea to write down my experiences.
Recently I had to upgrade an Exchange 2013 platform from CU2 to CU5, there were four Exchange 2013 Client Access servers and eight Exchange 2013 Mailbox servers (in a DAG).
During the upgrade of the Mailbox servers users were presented with the dreaded “The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook.” dialog box.