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

Exchange server - disk failed, disk with Priv.edb & stm.edb files on there,,,,

I am running Exchange 2003 standard version, and came into work today to find that the GB scsi disk failed that stores all the Exchange mailstore data.  Now exchange will not let me move the file over to a new volume, because it can not see the failed disk.  I modified the path on the mailstore file so the path now points to the new location, and received a message saying files moved successfully, however that is not the case, because it can not see the E:\ since it crashed.  Is there a quick way to create new .edb files, and get going?  Or am I forced to revove all the users from the mailstore, delete the mail store and create a new mail store and creat new users/email's?

Please help,,
0
IngramEntities
Asked:
IngramEntities
  • 5
  • 5
1 Solution
 
dbllpCommented:
first create a new mailstore with a different name where you plan on putting the new one.

then see if it lets you move the mailboxs to it... I doubt it.

I think you are out of luck here.
0
 
IngramEntitiesAuthor Commented:
I found a good backup from 2.11.2011 and restored the backup to the server and still can not mount the mail store?????  Can it be because the original locations was E:\mtbdatda\ and I had to restore the backup to D:\mtbdata\ ?  What else do I need to do to correct the data file path in order to get my mail store to mount successfully?

ESM error reads:
An Internal processing error has occurred.  Try restarting ESM and reviewing application logs.   ID c1041724
0
 
dbllpCommented:
good you have a backup!

that error should then populate the event log, post up whats in the event log.
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
dbllpCommented:
look here when you have the those event log info:

http://support.microsoft.com/kb/896143
0
 
IngramEntitiesAuthor Commented:
Getting stuck with Event ID 9175:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
0
 
dbllpCommented:
run a repair on the database

eseutil /p (full path and name of database)

goto a command prompt and then go to the BIN folder in the exchange server folder then run the above command
0
 
IngramEntitiesAuthor Commented:
I had to just make a new mailstore, and reconnect users
0
 
dbllpCommented:
running a repair didnt work?

you had a backup, so you chose to lose all your data instead of using that backup?
0
 
IngramEntitiesAuthor Commented:
Problem solved by IT team, as mentioned above
0
 
IngramEntitiesAuthor Commented:
Had to start from scratch and restore mail from users .PTS files back to exchange.  Not the quickest way, but we did not loose any mail.  So it was well worth it.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

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