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

mount edb to Exchange sbs2003

I have a software that repair exchange databases , the name is Kernel for Exchange Server by Nucleus technologies, anyway

After I got the repair database, I still have the standard folder \exchsrvr\mdbdata with the old files:
-A bunch of e00xxxx.log
-One E00.log
-One E00.chk
-Some IFS files
-the old priv1.edb
-the old priv1.stm
 
How should i treat these ones? Should I delete all the .log files, what about the old priv1.edb? etc.

Thanks
Etc.
0
75carlos
Asked:
75carlos
  • 8
  • 4
1 Solution
 
DLeaverCommented:
I have never used this software but I can tell you the procedure that I use on repairing EDB's using Eseutil

- I set the mailbox and PF mailbox database stores to be allowed to be overridden by a restore
- Ensure all stores are dismounted
- Stop all Exchange services
- rename the MDBDATA folder to MDBDATA-old
- Drop in the repaired EDB and STM - nothing else
- restart the Exchange services, with the IS being the last

Open the Management msc and if the DB's are healthy then they should be mounted

*This process is a form of Forklifting, and I didn't create it but I have done it so many times that I can list it from memory hence no web links
0
 
75carlosAuthor Commented:
I was not able to get a clean database with that tape. I got "dirty shutdown"
So my only option is to restore from tape.
What should be the corre4ct procedure for this?

Thanks
0
 
DLeaverCommented:
Run eseutil /mh to check the database status, if its in a dirty shutdown state then run the /P switch to repair it and then run the /mh switch again to check the status is now clean

Then follow my last post to re mount
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
75carlosAuthor Commented:
I 'm coping the directory mdbdata just in case.
Run eseutil /mh:

Microsoft(R) Exchange Server Database Utilities

Version 6.5

Copyright (C) Microsoft Corporation. All Rights Reserved.



Initiating FILE DUMP mode...
         Database: e:\program files\exchsrvr\mdbdata\priv1.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:04/05/2006 02:01:26 Rand:6384431 Computer:
         cbDbPage: 4096
           dbtime: 3753225152 (0xdfb5abc0)
            State: Dirty Shutdown
     Log Required: 198483-198485 (0x30753-0x30755)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 176437
     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: (0x2E27D,27C8,4D)  02/06/2012 21:07:27
      Last Attach: (0x2E27D,27D0,20)  02/06/2012 21:15:33
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:04/05/2006 02:01:25 Rand:6396490 Computer:
       OS Version: (5.2.3790 SP 2)

Previous Full Backup:
        Log Gen: 198374-198388 (0x306e6-0x306f4)
           Mark: (0x306EA,1B95,2F)
           Mark: 03/14/2012 19:31:22

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.16 seconds.
0
 
rocket_sudhiCommented:
Try the following

1) Take a backup of .edb, .stm and Log files.
2) Run eseutil /g---> check the integrity of file
3) Try ISinetg
4) then try eseutil /p (dont try at first attempt)
0
 
DLeaverCommented:
Ok so its in a dirty shutdown state

Run eseutil /p

Then run the eseutil /mh and post it back here if you like. - it should state it is in a clean state

Its a matter of opinion as the /p switch shouldn't be tried likely but as you are using a copy of your edb then there is no harm done, and I have used this fix many times before without issue
0
 
75carlosAuthor Commented:
I run eseutil /p  but I have to terminate it since it got stuck in
"deleting unicode fixed up table"

the new result of eseutil /mh is:

Microsoft(R) Exchange Server Database Utilities

Version 6.5

Copyright (C) Microsoft Corporation. All Rights Reserved.



Initiating FILE DUMP mode...
         Database: e:\program files\exchsrvr\mdbdata\priv1.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:03/17/2012 02:08:54 Rand:64436131 Computer:
         cbDbPage: 4096
           dbtime: 3886819273 (0xe7ac27c9)
            State: Dirty Shutdown
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 185147
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 2
      Repair Date: 03/17/2012 02:08:54
 Old Repair Count: 0
  Last Consistent: (0x0,0,0)  00/00/1900 00:00:00
      Last Attach: (0x0,0,0)  03/17/2012 02:08:54
      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: none
Old bad Checksum Error Count: none

Operation completed successfully in 3.16 seconds.


When I run eseutil /p, it was recomended that I should run:
---To ensure the database is up-to-date please use the 'Recovery' operation.--
0
 
75carlosAuthor Commented:
Runing sesutil /r e000 i get:


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

Initiating RECOVERY mode...
    Logfile base name: e00
            Log files: <current directory>
         System files: <current directory>

Performing soft recovery...

Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access fi
le, the file is locked or in use) after 21.32 seconds.



All the rights on folders are as should be.
0
 
75carlosAuthor Commented:
I restore but still "dirty shutdown"

is it possible to get a restore that has a corrupted db already?

I'm f... at lost here.
0
 
75carlosAuthor Commented:
I'm getting event id 619

Whic is telling that the "attemped to attach database e:\program files\exchsrvr\mdbdata\priv1.edb  but it is a database restored from backup set on which hard recovery was not started or did not complete succesfully.
0
 
DLeaverCommented:
Run through the steps in this KB article

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

What backup software have you been using?  At the start you said you were using a recovery software - has this not been successful?
0
 
75carlosAuthor Commented:
I did call Microsoft on Saturday and they help me to resolve the problem.
To make it short I had to restore (the instructions that were posted by the expert are the same as MS told me to run) until I was able to find a restore with a "Clean state" from the beginning of the week, so I lost like 3 days.

So obviously you can be restore from an early date run eseutil /mh and get "dirty shutdown"...not clear for me how that is possible but it did happen.

Regarding the software I got...same problem, it was not able to fix the .EDB
0
 
75carlosAuthor Commented:
restore from good backup thT'S WAS ALL
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

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