Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

How to create Clean Priv1.edb & Priv1.STM

Dear All,

We are using Exchange Server 2003, i want to delete the current MDBDATA folder (Priv1.edb & Priv1.stm) and create clean Priv1.edb & Priv1.stm. could you please tell me how can i create new database


Ram Kumar Chellam
Ram Kumar Chellam
2 Solutions
MASTechnical Department HeadCommented:
Ram Kumar ChellamAuthor Commented:

I want to know the following way is right to create the clean database :

How To Create A Blank Clean PRIV1 edb for Microsoft Exchange Server
The Exchange Information Stores are located in the MDBDATA folder (unless you have moved them to a custom location), usually on the second partition in a 2 partition Exchange Installation. In most cases the Information Stores Services are already shut down due to the tragedy that brought you to this page. If not, stop the Information Stores Services.
Now you will be able to rename the MDBDATA folder to something like MDBDATA-old or whatever you want. Now create a blank MDBDATA folder, go back and start your Information Stores Service.
At this point you can go into your Exchange Administration right click on the Private Mail Store (priv1.edb) and click “mount”. You will get a nag screen that complains about there being no edb and life will come to an end in the galaxy if your not careful, but ignore all that and hit OK. It now creates a brand new PRIV1.edb and PRIV1.stm file!

move all user to other mail group from  Priv1.edb & Priv1.stm
unmount Priv1.edb/Priv1.stm  database
delete Priv1.edb/Priv1 and all logs
mount the database and it will generate all clean database

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Naazg your outline is correct i.e.  taking the above actions will

1. Protect the current database (EDB and STM) by renaming the old DB folder.  I am assuming the reason you are doing this is because the database is corrupt or unmountable and you desire is to get the users operational ASAP while you attempt to repair and recover data from the damaged db?

2.  When you mount the database and Exchange complains that the database file are not present, by continuing you will create a new dial-tone database and  users will be able to send and receive new emails.

3. At this point you can then set about repairing the old database to recover data via a 3rd party utility  just Google for something like "open offline Exchange 2003 database" or via the Exchange RSG http://support.microsoft.com/kb/824126.

NOTE 1: before doing a dial-tone recovery you should first consider that once the new database is in place that Outlook clients configured in cache mode will error on connect because the key between the OST (Offline cache) and the exchange database is now different.  The users will be given the choice to connect to the Exchange server and start working online  OR to connect to the offline cache OST file.  As soon as the user connects to the new online server this will cause the old OST to becomes inaccessible.  So before users connect to the newly created Exchange database I would suggest one of two things;

1. Have each user connect to the offline cache OST and then export all contents to PST.  This will give each user a backup of their respective mailboxes post crash and they can then import that information into the new Exchange mailbox.

2. Before allowing any user to connect to the new exchange database you could take a copy of each users OST file and then should you be unable to recover the data from the old exchange database you could purchase a 3rd party OST to PST conversion tool and then import that data into the new Exchange database.

Frankly option 1 is your best bet IMO and most gratifying since users get data back quickly

NOTE 2:  The other thing you want to consider is WHY did this database go offline, i.e. did a hardware problem cause the DB to go bad?  If so then you are just going to repeat the error once again so before putting any new data into the system you need to understand and correct the reason it happened in the first place.

Ram Kumar ChellamAuthor Commented:
Thanks for the points

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

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