none
Assistance with Exch 2010 dirty shutdown / recovery EDB RRS feed

  • Question

  • Exchange 2010 dirty shutdown wont come clean!  Soft recovery
      Restored log and EDB and am running eseutil to clean the EDB.  I have the correct log files as of display, and it says that it goes through successfully, however, when I run the /mh, it still comes up dirty.

     I moved the log files and the EDB into the same folder for ease of syntax, but then reverted the files back, both with the same result.

     Do I have to keep the files in the original (restored) folders?
      How do I do a hard recovery for the same set given the soft recovery wont work.  The ultimate goal was to restore a clients sent item folder which has seemed to mysteriously emptied itself.  I have a good backup from native windows backup.  
     So I have a recovery DB in EMC, and am working the actual EDB on a sep disk / location, but cant get it to come clean so I can mount it, then extract the info.

     Client did not have SIR enabled.
    Thursday, April 18, 2019 7:01 PM

All replies

  • Hi,

    Remove all the log files from the logs folder and see if the database mounts back again. If it is not helps, you have to go for a hard discovery.

    You can try the hard recovery with the following command

    eseutil /p e:\temp\data\exchdb.edb


    Regards From: Exchange Online | World of Cloud Computing

    Thursday, April 18, 2019 7:59 PM
    Moderator
  • Hi lr1516,

     

    You can execute the eseutil command using /P for a repair to get the database into a clean shutdown. But it might lead to data loss. The /P could be a measure of extreme desperation when there’s no way at all to recover your database via /R.

     

    You could refer the article below and check if your ESEUTIL command is correct.

     

    Why Exchange Databases Might Remain Dirty After ESEUTIL /R Recovery

    https://blogs.technet.microsoft.com/mspfe/2012/09/06/why-exchange-databases-might-remain-dirty-after-eseutil-r-recovery/

    Regards,

    Kelvin Deng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, April 19, 2019 7:44 AM
  • Hi,

    Soft recovery – eseutil/r

    Once the command completes successfully, mount the stores.

    You might get this error:

    “Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after n seconds.”

    To resolve this, run soft recovery with the “/i ” switch at the end and it will override the EDB-STM mismatch.


    Thanks & Regards, Kumar N

    Friday, April 19, 2019 7:56 AM
  • Hi,

    Soft recovery – eseutil/r

    Once the command completes successfully, mount the stores.

    You might get this error:

    “Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after n seconds.”

    To resolve this, run soft recovery with the “/i ” switch at the end and it will override the EDB-STM mismatch.


    Thanks & Regards, Kumar N

    There is no stm file with Exchange 2010
    Sunday, April 21, 2019 9:20 PM
    Moderator
  • The database restored from backup is in a "clean shutdown" state.
     
    I mounted an empty recovery database. 

    How do I swap the databases as the restored / clean shutdown database has the data I need.

     thanks!
    Tuesday, April 23, 2019 2:29 PM
  • D:\Restore201904\E_\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox
    Database>eseutil /mh rdb1.edb

    Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
    Version 14.01
    Copyright (C) Microsoft Corporation. All Rights Reserved.

    Initiating FILE DUMP mode...
             Database: rdb1.edb


    DATABASE HEADER:
    Checksum Information:
    Expected Checksum: 0x32f6f4d2
      Actual Checksum: 0x32f6f4d2

    Fields:
            File Type: Database
             Checksum: 0x32f6f4d2
       Format ulMagic: 0x89abcdef
       Engine ulMagic: 0x89abcdef
     Format ulVersion: 0x620,17
     Engine ulVersion: 0x620,17
    Created ulVersion: 0x620,17
         DB Signature: Create time:02/27/2012 14:02:29 Rand:1265755 Computer:
             cbDbPage: 32768
               dbtime: 870589350 (0x33e423a6)
                State: Dirty Shutdown
         Log Required: 1631325-1631346 (0x18e45d-0x18e472)
        Log Committed: 0-1631347 (0x0-0x18e473)
       Log Recovering: 0 (0x0)
      GenMax Creation: 04/13/2019 23:00:10
             Shadowed: Yes
           Last Objid: 24364
         Scrub Dbtime: 0 (0x0)
           Scrub Date: 00/00/1900 00:00:00
         Repair Count: 0
          Repair Date: 00/00/1900 00:00:00
     Old Repair Count: 0
      Last Consistent: (0x17E788,8,1F)  03/17/2019 17:51:42
          Last Attach: (0x17E793,9,86)  03/18/2019 10:14:53
          Last Detach: (0x0,0,0)  00/00/1900 00:00:00
                 Dbid: 1
        Log Signature: Create time:02/27/2012 14:02:29 Rand:1261866 Computer:
           OS Version: (6.1.7600 SP 0 NLS ffffffff.ffffffff)

    Previous Full Backup:
            Log Gen: 1630071-1630091 (0x18df77-0x18df8b) - OSSnapshot
               Mark: (0x18DF8C,8,16)
               Mark: 04/12/2019 23:02:49

    Previous Incremental Backup:
            Log Gen: 0-0 (0x0-0x0)
               Mark: (0x0,0,0)
               Mark: 00/00/1900 00:00:00

    Previous Copy Backup:
            Log Gen: 0-0 (0x0-0x0)
               Mark: (0x0,0,0)
               Mark: 00/00/1900 00:00:00

    Previous Differential Backup:
            Log Gen: 0-0 (0x0-0x0)
               Mark: (0x0,0,0)
               Mark: 00/00/1900 00:00:00

    Current Full Backup:
            Log Gen: 0-0 (0x0-0x0)
               Mark: (0x0,0,0)
               Mark: 00/00/1900 00:00:00

    Current Shadow copy backup:
            Log Gen: 0-0 (0x0-0x0)
               Mark: (0x0,0,0)
               Mark: 00/00/1900 00:00:00

         cpgUpgrade55Format: 0
        cpgUpgradeFreePages: 0
    cpgUpgradeSpaceMapPages: 0

           ECC Fix Success Count: none
       Old ECC Fix Success Count: none
             ECC Fix Error Count: none
         Old ECC Fix Error Count: none
        Bad Checksum Error Count: none
    Old bad Checksum Error Count: none

      Last checksum finish Date: 00/00/1900 00:00:00
    Current checksum start Date: 00/00/1900 00:00:00
          Current checksum page: 0


    Operation completed successfully in 7.410 seconds.


    D:\Restore201904\E_\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox
    Database>


    Please understand the following:
      The exchange server is up and running.  A client needs contents of his SENT ITEMS restored from a backup.
     I have the EDB and the correct log files in the folder above but cannot get the EDB file out of dirty shutdown status.

     how do I proceed from there?
    Tuesday, April 23, 2019 5:58 PM
  • Hi lr1516,

     

    I understand the recovery database is in dirty shutdown state now. The link below is the process of restoring data using a recovery database.

     

    Restore data using a recovery database

    https://docs.microsoft.com/en-us/exchange/high-availability/disaster-recovery/restore-data-using-recovery-dbs?view=exchserver-2019

     

    In step1, put the recovered data file in a file. For example, c:\Dbrecovery

    In step2, It needs to use Eseutil to bring that database into a clean shutdown state, in your scenario,  the cmdlet should be:

     

    eseutil /R E00 /l "c:\DBRecovery" /d "c:\DBRecovery\rdb1.edb"

     

    Then run the following: eseutil /mh "c:\DBRecovery\rdb1.ed", check database state. If the result returns 'clean shutdown', please follow the remaining steps in link above, if it returns 'dirty shutdown', please execute the cmdlet to perform a repair of the database.

     

    eseutil /P  "c:\DBRecovery\rdb1.edb"

    Regards,

    Kelvin Deng

     


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, April 29, 2019 10:22 AM
  • Hi,

    Soft recovery – eseutil/r

    Once the command completes successfully, mount the stores.

    You might get this error:

    “Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after n seconds.”

    To resolve this, run soft recovery with the “/i ” switch at the end and it will override the EDB-STM mismatch.


    Thanks & Regards, Kumar N

    There is no stm file with Exchange 2010

    And nobody misses it.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, April 29, 2019 9:41 PM
    Moderator
  • Follow this article https://www.nochanceforrecoveryfix.com/blog/fix-exchange-database-dirty-shutdown-error/ and know how to fix Exchange database dirty shutdown error.

    VENDOR SHILL!

    This is a sales pitch by an employee of the manufacturer offering advice that requires buying their product.  Consider that before opening the link.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!



    Friday, May 10, 2019 6:23 AM
    Moderator
  • Read the blog <Vendor URL> and know how to never recover from a dirty shutdown error.


    VENDOR SHILL!

    This is a sales pitch by an employee of the manufacturer offering advice that requires buying their product.  Consider that before opening the link.



    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Tuesday, May 28, 2019 4:00 PM
    Moderator