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

How to recover an exchange 2003 database from a previous corrupted installation

Hi there

Our active directory databse corrupted and our back restore failed. So i have to re-install as this was the fastest way of dealing with the problem. I have an exchange databse from the old version (everything fine in new version) and wondered whether there was any way of extracting the data from the old database to say pst files (specially the public folders)

Many thanks in advance

Regards

Nick
0
ndb5
Asked:
ndb5
  • 3
  • 2
  • 2
  • +1
2 Solutions
 
myfootsmellsCommented:
http://www.msexchange.org/tutorials/Recovering-Failed-Exchange-2003-Member-Server-Using-Disaster-Recovery-Switch.html

Try that link.  If you do a google search on recovering exchange 2003 you'll find lots of tutorials.

One thing to keep in mind that is SUPER SUPER important, you'll want to use the same information store name as the server that failed.

Good luck, oh and you'll want to look up exmerge as well.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
This KB should explain the how-to:http://support.microsoft.com/kb/313184

If that doesn't work for you, then...

If you haven't yet attached the client machines, and if they were originally configured with cached mode (including offline public folders) the you'll find that there is a copy of the information in the .ost files on each workstation.

Jeff
TechSoEasy
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

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

 
ndb5Author Commented:
Many thanks for pointing me in the right direction.
Time has moved on a little since i last posted this help request. The situation is as follows:-

1. Our newly installed sbs server is working fine although i did change the server name.
2. The old exchange dat ais still on the new server so to speak.
3. what i would like to do if possible is to extract the data from the old files (especially the public folders amd put it into a format that allows for a restore to the new server exchange without affecting the new data and emails that have arrived
4. In reference to techsoeasy i did attach the systems to the new server
5. Everything is working fine now and we have ironed out any niggles from the new installation which was installed without the disaster recivery switch. I do not wish to damage or risk the new installation of exchange as it is working fine so....

Could you point me in the right direction to extract the data from the old exchange data base say in nto pst files and this would allow me to restore when time permitts the bits that i want. We have a few public folders that had some useful shared data in and it would be good to recover this info.

It seems i may have shot myself in the foot by not naming the server the same as the old one.

Any help or direction pointing in regards to the procedure for revery of data would be very helpful

Thank you both once again in advance..

Regards

Nick

Therefore - could
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Naming the server differently doesn't really matter... what you need to do is actually EXPORT the current mailboxes to .pst files (using EXMERGE) because you can't do that with the old databases.  Then you would recover the old databases according to the documentation I've already provided and after you can reimport the .pst's that you made (I usually suggest that you do this in Outlook if you don't have that many users).

You can find EXMERGE here:  
http://www.microsoft.com/downloads/details.aspx?FamilyID=429163ec-dcdf-47dc-96da-1c12d67327d5&DisplayLang=en

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
P. S. You might still find the original .ost files on the workstations by the way... it's possible that a new one was created when you reinstalled.  In fact if your users don't see their old email then for sure they got recreated (as long as you had cached mode enabled before -- and that's the default setting).

So take a look at C:\Documents and Settings\User Name\Local Settings\Application Data\Microsoft\Outlook and see if there is a large .ost file.

You would then need to convert that to a .pst file.  Because it's an Outlook 2003 .ost the usual tool ost2pst.exe (http://www.xcopy32.com/download.php?file=24)  doesn't work --- directly.  There is someone that has blogged a work-around however...http://blogs.geekdojo.net/adam/archive/2005/08/17/9014.aspx

I realize that this is a bit round-about... however it may be worth trying on one file to see if you can get it to work.

Jeff
TechSoEasy
0
 
WpgComputerGuyCommented:
One other possibility that might work for you is restoring your backup in the recovery storage group.

From memory, here are the high level steps:
1) Create a recovery storage group
2) Restore the db into the recovery storage group
3) Extract the mailboxes to PST files from the recovery storage group

However, this may not work if you didn't do a restore of Active Directory to get all of the same accounts. It relies on the same user accounts still being there if I remember correctly.

This link has docs for the recovery storage group - http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/ue2k3rsg.mspx

When a recovery storage group is created on the server, all Exchange DB restores are put in the recovery storage group. It's a little scary the first few times because there is no option to select to confirm that's where it's going.
0
 
ndb5Author Commented:
Many Many thanks and I appreciate all your support - i will try this and report back. As you have both been so helpful in this matter would you mind splitting the points?

Once again thank you and isn't experts-exchange a great site!

Regards

Nick
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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