Restore Exchange 2003 Databases

[mikem501]

I am testing a restore strategy. I have a single Exchange Server 2003 running on Windows 2003.

I have conducted a full computer backup including system state but excluding the MDBDATA and Exchange selection in NT Backup.

I took a separate backup then for the Exchange databases only.

I restored the Full Computer backup, and everything is fine till now. I have Windows2003 with a copy of the AD running and MS exchange with no databases (exacly like the original server but without the databases)
When I go to restore the MS Exchange databases, I could not mount the store, (error a hard recovery was not run on the databases)
I ran eseutil /cc in the restored temp folder and I get the error the log file has an incorrect signature.
What am I missing?

Thanks.

 

[Andreh]

This server that you are restoring, are you adding it to your network or is it stand alone? And just a general question about your network, is this server the only DC in your domain and if not does it contain and FSMO roles? These are more general understanding questions of how your network is configured for us to give you a good answer.

Cheers

"Assumption is the mother of all f#%kups!

 

[mikem501]

I have single server on my network that acts as a AD server (DC) and a MS Exchange 2003 server.
As part of a disaster recovery plan, I took a separate server and placed it on another standalone network and restored the backups on this server just to make sure that in the event of any faulure even in the most disastrous when I completely loose the server I can restore back the machine and bring it back to normal operation.

I have installed Windows 2003 server (from the same CD) on this new server. (note that the two servers do not see each other on the LAN).

I have then restored the full computer backup from tape that does not include the MDBDATA folder and the exchange databases.

Until here I got a replica of the original server including all applications, MS Exchange and Active Directory.

I placed the Exchange backup in the tape for restore and the restore was successful. When I come to mount the stores back in system manager, I find an error in system manager telling me to check the event logs.

The most meaningful error is the ESE event, telling me to replay the logs as the database was found in an inconsistent state.

When I replay the database using eseutil /cc command the error from eseutil is that the log files have an incorrect signature.

What is the easiest way to restore back my databases?

Cheers!

 

[Andreh]

Did you restore in 'Directory Services Restore mode'? When recovering AD, you need to use this method.

I have recovered DC's with FSMO roles and without successfully before. Exchange just adds onto this.

I would test the restored server for AD issues using DCDIAG.exe (c:\dcdiag /v >dcdiag.txt). This would give you an idea of issues on the work you have already done.

See how you go with this, I don't have time to post the full process of AD restore at the moment.

Goodluck


"Assumption is the mother of all f#%kups!

 

[mikem501]

Hi Andreh, My AD is fine. The AD restore was not problematic. The only problem I have is with the MS Exchange Database restore. I cannot get the public and private mailstores back and mounted.

Thanks.

 

[Andreh]

No problem Mike, just following my signature at the bottom

Did you try the setup.exe /disatrerrecovery option? May be worth a go. It seems you are pretty close.


"Assumption is the mother of all f#%kups!

 

[Andreh]

sorry, i meant /disasterrecovery.

"Assumption is the mother of all f#%kups!

 

[mikem501]

I did not install MS Exchange again since I got this autmoatically from the Full Computer restore using a restore set containing System state.
Shall I re-install MS Exchange using /disasterrecovery switch?

 

[Andreh]

yes, this should resolve any errors that you have within exchange. Here is some research for you first though:

http://www.msexchange.org/tutorials...er-Server-Using-Disaster-Recovery-Switch.html

Cheers.

"Assumption is the mother of all f#%kups!

 

[mikem501]

Ok finally had some time to fix this problem.

As a general rule, you should completely delete the files matching the specification *nn.* from the storage group data folders. This includes the R00.log file, the R00.chk file, and any Enn.log or Enn.chk files.


After that I managed to run eseutil /cc. This was successful and so was the database mount. Thanks a lot.