This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 95%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
hi all,
We test any desaster szenarios and see that passiv copies have dirty shutdown when we restore it from backup.
We test also dismount aktive DB, suspend and remove passiv copy - passiv copy are dirty shutdown and can't use without eseutil and softrepair. It this per design?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 94%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
Hi @Chris ,
Agree with Andy.
When you do an Exchange Aware backup the DB is mounted and open for business/transactions to occur. The DB is temporarily quiesced during the backup and then ALL Logs that have not yet been committed to the DB are bundled with the backup so that when restored they can be played to bring it into a consistent state.
As soon as you mount the DB again its back into the dirty state.
Please refer to similar threads: why-does-an-exchange-database-ends-up-in-dirty-shutdown-state-after-backup
Hi,
I am writing to see how everything is going on with this thread. If you still have further concern on this, please feel free to let us know.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Yes, that is expected. When you dismount a database gracefully and any uncommitted logs are replayed into the database, that is a clean shutdown.
When you restore from a backup or attempt to mount a passive database that has either lagged copies or does not have all the required logs committed to the database, it is in a "dirty" state and the required logs need to be replayed into it either by the backup program or with eseutil