new store on Exchange 2003

SBS 2003
Exchange 2003

So I have a semi-corrupted exchange db.  I wanted to make a new db from scratch and migrate all the mailboxes to it, but I guess I cannot do that on SBS 2003.  There can only be 1 store.

So is my only option to use Exmerge to export every mailbox to pst and delete the current db and create a new one and merge them all back in

Just checking that my facts are right
Who is Participating?
MegaNuk3Connect With a Mentor Commented:

Have you tried NTbackup yet and confirmed there is no AV scanning of the Exchange files?
Alan HardistyCo-OwnerCommented:
You can either use a Recovery Storage Group to do this or use the Dialtone method to create a new store and then extract the mail from the old store and import it into the new store.

Exchange 2003 Recovery Storage Group:

Dial Tone Recovery Method:
AmitIT ArchitectCommented:
Use eseutil tool and first check the corruption level. Next you are run the repair using same tool.

Safest option. Creating new DB, you might end up with lot of issues.
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.

Use the Dial Tone method Alan has mentioned, it will give you a nice new clean DB and the mailboxes will have minimal downtime.
How do you know the DB is semi corrupted anyway? How many users are there?
shard26Author Commented:
Like 20-30 users.

From messages I see during backups.

the db mounts and works fine from the clients point of view, but the backup errors point to corruption.  I would feel safer getting a nice new db and bringing everything over.
Just be sure to read the implications of doing a dial tone DB:

As cached mode users will be prompted to work offline or online(non cached)

Also from what I remember, any Blackberry (BES) users won't be able to synch their devices with their new mailboxes and will require re-activation.

Another way to sort this out, would be to dismount your DB
- eseutil /mh on the DB and look at the RepairCount value
- eseutil /p your DB
- eseutil / mh on the DB again, if the repairCount has gone up by less than 2 then the DB is safe to use
- eseutil /d your DB to defrag it
-isinteg -fix -test alltests on your DB 3 times to sort out logical issues
You are done
Unfortunately eseutil and isinteg require your DB to be offline so your users won't be able to access it.

Also above I meant to say if your RepairCount goes up by less than 3, then only minor changes have been made to it and it is safe to use. I have seen /p run and not increase the repaircount so hopefully you will be that lucky .
shard26Author Commented:
yeah, i will be doing all of this during off hours. so no access is fine.

It might be worth dismounting your DB for a few minutes today outside of business hours and seeing what the repair count is currently. If the repair count is above 10 then I would recommend the dial tone method instead of trying to repair that DB.
shard26Author Commented:
that would be the "eseutil /mh "?

AmitIT ArchitectCommented:
Read this.

did you tried to take db backup using NTBackup. See if that also throws same error
Yep eseutil /mh
shard26Author Commented:

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

Initiating FILE DUMP mode...
         Database: priv1.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:06/28/2006 18:44:59 Rand:1094087329 Computer:
         cbDbPage: 4096
           dbtime: 619457215 (0x24ec2abf)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 238697
     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: (0x979E,1FCC,E2)  02/17/2011 23:28:49
      Last Attach: (0x96DF,18A7,2E)  02/13/2011 02:12:18
      Last Detach: (0x979E,1FCC,E2)  02/17/2011 23:28:49
             Dbid: 2
    Log Signature: Create time:07/19/2005 12:02:26 Rand:261965 Computer:
       OS Version: (5.2.3790 SP 2)

Previous Full Backup:
        Log Gen: 37458-37458 (0x9252-0x9252)
           Mark: (0x9252,1434,6F)
           Mark: 01/08/2011 00:05:14

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.63 seconds.
shard26Author Commented:
(that is from today before I did anything)
Excellent, it has either never been repaired or the fixes were so minor they were recorded. So hopefully when you do your /P the RepairCount will be 2 or less.
You might want to try the NTBackup test first though.
shard26Author Commented:
So do the /P and then do the /mh right afterwards?
shard26Author Commented:
Actually I created a job last night to do only the Info Store and it ran fine.

To see all the errors I was getting  >

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.

All Courses

From novice to tech pro — start learning today.