• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 479
  • Last Modified:

*** HELP *** Corrupted Exchange 2003 database (no backup)

How do I recover from a dirty shutdown?



D:\Exchsrvr\MDBDATA>eseutil /ml D:\Exchsrvr\MDBDATA\priv1.edb

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...

      Base name: pri
      Log file: D:\Exchsrvr\MDBDATA\priv1.edb
                ERROR: Cannot read log file header. Error -514.

Operation terminated with error -514 (JET_errBadLogVersion, Version of log file
is not compatible with Jet version) after 0.375 seconds.

-------------------------------------------


Microsoft(R) Exchange Server Database Utilities

Version 6.5

Copyright (C) Microsoft Corporation. All Rights Reserved.



Initiating FILE DUMP mode...
         Database: D:\Exchsrvr\MDBDATA\priv1.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,9
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,9
     DB Signature: Create time:12/16/2011 11:53:54 Rand:2210890 Computer:
         cbDbPage: 4096
           dbtime: 2 (0x2)
            State: Dirty Shutdown
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 1
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 2
      Repair Date: 12/16/2011 11:53:54
 Old Repair Count: 0
  Last Consistent: (0x0,0,0)  00/00/1900 00:00:00
      Last Attach: (0x0,0,0)  12/16/2011 14:54:03
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
       OS Version: (5.2.3790 SP 2)

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

Previous Incremental 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: found (1)
Last Bad Checksum Error Date: 12/16/2011 11:21:56
Old bad Checksum Error Count: none

Operation completed successfully in 0.47 seconds.


Microsoft(R) Exchange Server Database Utilities

Version 6.5

Copyright (C) Microsoft Corporation. All Rights Reserved.



Initiating FILE DUMP mode...
         Database: D:\Exchsrvr\MDBDATA\pub1.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,11
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,9
     DB Signature: Create time:10/31/2008 08:58:18 Rand:3947069 Computer:
         cbDbPage: 4096
           dbtime: 105833624 (0x64ee498)
            State: Dirty Shutdown
     Log Required: 57448-57453 (0xe068-0xe06d)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 96202
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 2
      Repair Date: 10/31/2008 08:58:18
 Old Repair Count: 0
  Last Consistent: (0xDA26,11D4,4A)  12/02/2011 14:56:24
      Last Attach: (0xDA26,11D5,BB)  12/02/2011 14:56:31
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:10/30/2008 12:42:37 Rand:8145636 Computer:
       OS Version: (5.2.3790 SP 2)

Previous Full Backup:
        Log Gen: 55846-55872 (0xda26-0xda40)
           Mark: (0xDA27,973,AA)
           Mark: 12/02/2011 15:03:27

Previous Incremental 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: found (1)
Last Bad Checksum Error Date: 10/31/2008 08:58:18
Old bad Checksum Error Count: found (1)

Operation completed successfully in 0.125 seconds.


Microsoft(R) Exchange Server Database Utilities

Version 6.5

Copyright (C) Microsoft Corporation. All Rights Reserved.



Initiating FILE DUMP mode...
         Database: D:\Exchsrvr\MDBDATA\priv1.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,9
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,9
     DB Signature: Create time:12/16/2011 11:53:54 Rand:2210890 Computer:
         cbDbPage: 4096
           dbtime: 2 (0x2)
            State: Dirty Shutdown
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 1
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 2
      Repair Date: 12/16/2011 11:53:54
 Old Repair Count: 0
  Last Consistent: (0x0,0,0)  00/00/1900 00:00:00
      Last Attach: (0x0,0,0)  12/16/2011 14:54:03
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
       OS Version: (5.2.3790 SP 2)

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

Previous Incremental 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: found (1)
Last Bad Checksum Error Date: 12/16/2011 11:21:56
Old bad Checksum Error Count: none

Operation completed successfully in 0.313 seconds.

0
Joeteck
Asked:
Joeteck
  • 7
  • 4
  • 4
  • +2
1 Solution
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
see here :

http://support.microsoft.com/kb/890056

wish to you good luck
0
 
xmlmagicianCommented:
0
 
JoeteckAuthor Commented:
Have a silly question... If I have an old backup...like two months old, can I just overwrite the files, and bring it back up?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
MadParCommented:
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
0
 
SriHarsha KTechnical Services SpecialistCommented:
@ Joeteck -- U can use the old backup and restore that only if the old database is in good condition.But you are going to loose the data inthese 2months.

So,better try to repair the current database.If this fails then we can use the old database from backup.

But first,check the disk for file level corruption.
-Start by running chkdsk on the physical drive and check for any error.
 If found then run chkdsk /r /f  in restore mode.

- Check whether exchange database and logs are excluded from anti virus exclusions.
(Sometimes when the logs and database gets corrupted when they are not excluded).

- Now perform the steps mentioned in the below article.
http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/

Note - Repair process time depends on the extent of corruption.The time for Offline Defragmentation is 1hr for 4gb of database app and to perform that offline defragmentation there shud be 110% of free space available on the drive where you going to perform.
See to that,there is sufficient drive space.(USB drives not supported).

Hope you can complete by this weekend.
Cheers...have a good time.
0
 
xmlmagicianCommented:
has any of the suggestions worked? best of luck
0
 
JoeteckAuthor Commented:
No nothing yet.. I was at work till 1:30 last night and I'm going back today. The database is 54gig and the stm is 37gig. I have another exchange server in a new domain, so I copied the files to an external drive usb 3.0 drive to try and let that do the repair. Do I need the log files too? What do you guys think of using third party utilities for repairing or exporting from edb to pst? So far all the utilities say its damaged beyond repair. Strange thing is I have two storage groups and the second one is working. I can send and receive email.. I backed up using ntbackup and the file was 178gig but seems to be bad. Any help would be great...
0
 
MadParCommented:
Ontrack PowerControl
0
 
SriHarsha KTechnical Services SpecialistCommented:
What do u mean by this "so I copied the files to an external drive usb 3.0 drive to try and let that do the repair." ... Do u mean you have copied the corrupted database to another exchange server and did a repair there????

There are 3rd party tools like Ontrack that can do deep recovery.
0
 
SriHarsha KTechnical Services SpecialistCommented:
yes log files are not required in majority cases.

As log files are pertaining to the SG,there seems to be no problme with the Second Storage Group.

- I backed up using ntbackup and the file was 178gig but seems to be bad. Any help would be great (Are you saing that you backed up the second SG?
  How do u identified it to be bad?)

0
 
JoeteckAuthor Commented:
My mailserver is way too slow to do any type of repair.. its a pentium 4 2.8ghz. The other is a core i5-2500k I built, so its a beast and fast as crap. It already repaired the public folders but since the first storage group is screwed up, does not matter.. I copied the priv1 file to a usb 3.0 1tb lacie drive where its attempting to do a repair using Digiscope.  Already 2:42 minutes into the so called repair. Hopfully it will. If any wishes to call me instead please feel free.. 741-8041 I'm in the 631 area code, in ny.

Thanks
0
 
JoeteckAuthor Commented:
745-8041
0
 
SriHarsha KTechnical Services SpecialistCommented:
Hi what is the status now??
0
 
JoeteckAuthor Commented:
I added a new domain.. and bought digiscope and recovered my database... what a long weekend..
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
your db was corrupted?
0
 
JoeteckAuthor Commented:
Oh god yes!! It took 20 hours to repair using digiscope! That's on a core i5-2500k.

I never had to replace a domain in my life.. since the gcs was on the exchange server, and the domain was pretty much trashed when I started working there, I knew it was a matter of time until it Shit the bed.. I did move all the fsmo roles to a new box, however the exchange server still thought it was in control. I could never really view all the users when I ran users and computers on that system, so I knew it was time.. thankfully I had a fully operational new domain ready to go... I just had to move everyone out of the old one and into the new one.. huge nightmare.. still fixing stuff...its essentially starting a new company from scratch...But more a D/R. I would only recommend this as a last resort... but now everything is the way it should be... two domain Controlers and an exchange memeber server... amen to that!
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
joeteck , if you need further help check my profile and mail me
0
 
JoeteckAuthor Commented:
Replaced domain and used Digiscope to recover my database
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 7
  • 4
  • 4
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now