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

Exchange 2003 recovery problem

Hi Experts,

Setup:
Windows SBS 2003 running Exchange 2003 as part of it.

Background:

Yesterday I received a call from a client stating their email had gone down.  On logging into the server I found that the main data partition on the server was jammed full.  
Talking to the client I decided the best course of action was to move the mailbox database onto another partition so using the exchange system manager I went through the procedure to move the priv1.edb and priv1.stm files to the new location.
Once that was started off I left it going and advised the client it would take some time as the databases were about 30odd GB.

Cut to later that evening, I log into the server to find that its crashed and rebooted its self.  I get logged in and find that the whole data partition on the server has gone!  Ulp, better hope the backups are good...

Incidentally the priv1 files are sitting on the other drive just fine.  The users are able to access their mailboxes in outlook no problem.

So, I recreated the partition and started by recovering the folder structure for the exchange bit of the partition.  Once I do this and reboot exchange comes up and gives me access to the mailboxes that are now on the other drive, however I have no public folders as these files were not backed up at file level.

Stage 2, thinking I'm doing OK, I try to restore the Public Folder Database from the BackupExec backup from the last good backup.  However once I have done this I cannot mount the public folder database and get a 0xfffffde0 message.  At this stage users can no longer access their mailboxes in outlook.

To try and cure this I stopped the store service, moved the database files out to separate location and restarted the store service.  In ESM it showed the public store as offline so I tried to mount it and it gave me the option to create a new database as the files were missing.  All good I though...

Refresh of ESM shows that the mailbox store is now dismounted and will not mount and is giving the same error 0xfffffde0 in the application log.  Having run eseutil /m on the mailbox store I can see its in dirty shutdown state.

What I need to know is, is there anyway I can get this store back online again, or what is the simplest option to get me back up and running ASAP.

Many Thanks for any assistance that you can give me.

Steve

0
stevencUK
Asked:
stevencUK
  • 3
1 Solution
 
MorasivaCommented:
Hi,

Check the below MS article,

http://support.microsoft.com/kb/253931
0
 
stevencUKDirectorAuthor Commented:
Hi,

I can't see that option on any of the screens in BackupExec.  I'm using version 12 if that helps?

I tried following this article:
http://www.symantec.com/business/support/index?page=content&id=TECH10533

This still ends in a fail, however I now find a different error in the app log of 0xfffff749

I have also tryied a different setting in the exchange restore as per:
http://www.experts-exchange.com/Storage/Backup_Restore/Backup_Exec/Q_24249895.html
but I am no further forward.

Why does exchange make it so difficult to get back up and running!

Any further advise appreciated.

Steve
0
 
stevencUKDirectorAuthor Commented:
Have managed to get this up and running eventually.

What we had to do is:

Restore the storage group from BackupExec
Run eseutil /p on each database to get them into clean shutdown state.
Down the ExchangeIS service, delete all files except the 2 .edb and 2 .stm files from the database folder.
Restart the ExchangeIS service and all was then working.

Thanks for the suggestion.
0
 
stevencUKDirectorAuthor Commented:
Figured out a sequence that worked eventually.
0
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.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

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

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