tlcsupport
asked on
Microsoft Exchange 2003 Mailbox Store Shutdown State = Dirty (AP)
Basically, one of our Exchange servers went down :(
Now it wont mount some of the exchange mailbox stores, when doing an ESEUTIL /MH on the mailbox store I am receiving these:
State: Dirty Shutdown
Log Required: 114128-114132 (0x1bdd0-0x1bdd4)
How do I find out which log files it actually needs and then how do I import them into the EDB file so I can mount the database?
Now it wont mount some of the exchange mailbox stores, when doing an ESEUTIL /MH on the mailbox store I am receiving these:
State: Dirty Shutdown
Log Required: 114128-114132 (0x1bdd0-0x1bdd4)
How do I find out which log files it actually needs and then how do I import them into the EDB file so I can mount the database?
ASKER
I did the /MH and got:
State: Dirty Shutdown
Log Required: 114128-114132 (0x1bdd0-0x1bdd4
but that doesn't match up with the filename format of the log files.
Here is the full outcome of the /mh
C:\Program Files\Exchsrvr\bin>eseutil /mh "S:\Exchsrvr\MDBDATA\Stora ge Group 3\M
ailbox Store 3.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: S:\Exchsrvr\MDBDATA\Storag e Group 3\Mailbox Store 3.edb
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,11
Engine ulVersion: 0x620,11
Created ulVersion: 0x620,11
DB Signature: Create time:11/23/2006 14:36:12 Rand:109826350 Computer:
cbDbPage: 4096
dbtime: 498246677 (0x1db2a415)
State: Dirty Shutdown
Log Required: 114128-114132 (0x1bdd0-0x1bdd4)
Streaming File: Yes
Shadowed: Yes
Last Objid: 139629
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: (0x1BB58,14F8,172) 08/17/2010 09:26:50
Last Attach: (0x1BB58,14FA,CE) 08/17/2010 09:26:50
Last Detach: (0x0,0,0) 00/00/1900 00:00:00
Dbid: 2
Log Signature: Create time:11/23/2006 14:36:10 Rand:109818909 Computer:
OS Version: (5.2.3790 SP 2)
Previous Full Backup:
Log Gen: 109205-109274 (0x1aa95-0x1aada)
Mark: (0x1AA9A,4BA,13B)
Mark: 08/13/2010 20:49:54
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: none
Old bad Checksum Error Count: none
Operation completed successfully in 3.0 seconds.
State: Dirty Shutdown
Log Required: 114128-114132 (0x1bdd0-0x1bdd4
but that doesn't match up with the filename format of the log files.
Here is the full outcome of the /mh
C:\Program Files\Exchsrvr\bin>eseutil
ailbox Store 3.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: S:\Exchsrvr\MDBDATA\Storag
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,11
Engine ulVersion: 0x620,11
Created ulVersion: 0x620,11
DB Signature: Create time:11/23/2006 14:36:12 Rand:109826350 Computer:
cbDbPage: 4096
dbtime: 498246677 (0x1db2a415)
State: Dirty Shutdown
Log Required: 114128-114132 (0x1bdd0-0x1bdd4)
Streaming File: Yes
Shadowed: Yes
Last Objid: 139629
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: (0x1BB58,14F8,172) 08/17/2010 09:26:50
Last Attach: (0x1BB58,14FA,CE) 08/17/2010 09:26:50
Last Detach: (0x0,0,0) 00/00/1900 00:00:00
Dbid: 2
Log Signature: Create time:11/23/2006 14:36:10 Rand:109818909 Computer:
OS Version: (5.2.3790 SP 2)
Previous Full Backup:
Log Gen: 109205-109274 (0x1aa95-0x1aada)
Mark: (0x1AA9A,4BA,13B)
Mark: 08/13/2010 20:49:54
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: none
Old bad Checksum Error Count: none
Operation completed successfully in 3.0 seconds.
hi
you must convert the decimal range that is listed in the Log Required field to hexadecimal values. For example, if the Log Required value is 28217 – 28221, log files from 06E39 to 06E3D are required by this database. In Exchange Server 2003 SP1, the Log Required field has been enhanced to report both decimal and hexadecimal values.
Note You can use the Scientific mode of the Windows Calculator to convert from decimal to hexadecimal. Start the Calculator, and then click Scientific on the View menu. Enter the decimal number, and then click Hex.
post back results
you must convert the decimal range that is listed in the Log Required field to hexadecimal values. For example, if the Log Required value is 28217 – 28221, log files from 06E39 to 06E3D are required by this database. In Exchange Server 2003 SP1, the Log Required field has been enhanced to report both decimal and hexadecimal values.
Note You can use the Scientific mode of the Windows Calculator to convert from decimal to hexadecimal. Start the Calculator, and then click Scientific on the View menu. Enter the decimal number, and then click Hex.
post back results
ASKER
Ah-ha! Genius!
Ok, so I now have the 4 log files. It seems that all 5 stores in the Storage Group require these 4 log files.
How do I go about importing them into the 5 .edb files so I can get email back online and working?
Ok, so I now have the 4 log files. It seems that all 5 stores in the Storage Group require these 4 log files.
How do I go about importing them into the 5 .edb files so I can get email back online and working?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, it looks like its after 5 log files, E021BDD0 to E021BDD4
BDD0,1,2,3 are in the log folder, but BDD4 is not. Ideas?
BDD0,1,2,3 are in the log folder, but BDD4 is not. Ideas?
You are in good hands @adaroc's last post. Its complete
I have a few things to add.
A) make sure you have 1.5x free space of your edb size.
If your edb is 10gb then you need 15gb free space
I have a few things to add.
A) make sure you have 1.5x free space of your edb size.
If your edb is 10gb then you need 15gb free space
ASKER
This is the outcome with the /i switch on:
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
Logfile base name: E02
Log files: <current directory>
System files: <current directory>
Database Directory: C:\logs\powa.edb
Performing soft recovery...
Operation terminated with error -528 (JET_errMissingLogFile, Current log file mi
ssing) after 1.16 seconds.
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
Logfile base name: E02
Log files: <current directory>
System files: <current directory>
Database Directory: C:\logs\powa.edb
Performing soft recovery...
Operation terminated with error -528 (JET_errMissingLogFile, Current log file mi
ssing) after 1.16 seconds.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you try that
eseutil /r e00 /i /l"c:\ PATH TO LOG FILEs..." /d"g:\...PATH TO DATABASE"
eseutil /r e00 /i /l"c:\ PATH TO LOG FILEs..." /d"g:\...PATH TO DATABASE"
hi
whats the state of play pls ?
whats the state of play pls ?
ASKER
In the end we got hold of Microsoft and had to do a restore of the exchange backup as the database was "corrupt beyond repair"
Then check the logs required for making this database into clean shutdown i.e run eseutil /mh path of the database just below the status you will logs required.
this article will help in identifing : http://support.microsoft.com/kb/240145
Make sure that those logs are available if it is available then you need to go with eseutil /r
post back results