Link to home
Start Free TrialLog in
Avatar of Ron_Wells
Ron_Wells

asked on

Server stolen and all they backed up was the priv.edb and the pub.edb.

I have a new client that had been dismounting the exchange databases and copying them to a CD. Their server and workstations were stolen and now they want their email and address books back from their "backups".

I have set up a new server using their original disks.

Is there some miracle way to import their old exchange databases?
Avatar of hodgeyohn
hodgeyohn
Flag of United States of America image

miracle, no.

 you need to reinstall exchange using the same server, and org name.  the same names are important.

you should be able to restore the databases after that.
Avatar of Ron_Wells
Ron_Wells

ASKER

The edb's were copied not "backed up".
You may also need to create a new stm file if they didn't back those up too..
http://support.microsoft.com/kb/555146

Make sure when you recreate the user accounts that you do not create a new mailbox for them.  You can reconnect their old mailboxes by running Exchange cleanup agent and select reconnect all mailboxes.
I think that this article will help you: http://support.microsoft.com/kb/296788/
 
 
I'm getting my moneys worth today. It will take a while to try your solutions. Thanks
As long as the server name and organizational names are the same as they were previously, you can choose to allow Exchange to overwrite the database from a restore.  You'll need to check this box to allow copying the edb files in, they won't mount properly if you don't.
Where do I get: 11. Run "mailbox cleanup agent" on each mailbox store and choose "reconnect all mailboxes".
That's found in Exchange system manager.  Expand administrative groups, drill down to the private store, right click on mailboxes and click run cleanup agent.  Then you can right click on the disconnected mailboxes and reconnect mailbox.
ASKER CERTIFIED SOLUTION
Avatar of hodgeyohn
hodgeyohn
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The solution worked fine once I realized that the client had been using Exchange Server 5.5 and not 2000.