dirty shutdown not always indicate the DB is in that way

17 Feb

when using exeutil /mh those DB like Local Continuous Replication (LCR), Cluster Continuous Replication (CCR), Standby Continuous Replication (SCR), of the Database Availability Group (DAG)  passive database copies appear in a dirty shutdown state. this is by design. Do not fear that.

the reason is dirty shutdown database indicates that the database requires additional transaction logs to be committed in order for the database to stand on its own. Those Lagged passive databases always get the log from active node a little later. And after get enough log the replay process will start. So it means those database will always in dirty shutdown status.  So this is by design, right?

Leave a comment

Posted by on February 17, 2011 in Exchange Server


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: