Exchange disaster recovery - new machine

We're testing our Disaster Recovery strategy which involves installing Exchange and AD on Virtual Server instances and restoring the exchange database from backup.  I'm having difficulty doing this, and have a few questions:

BTW, I have read the Exchange Disaster Recovery Guide from Microsoft, but haven't found te answer to these questions...

1) We are using NT Backup as wel as Symantec LiveState, which is basically doing a file backup.  If LiveState backups the exchange database files live, what steps are necessary to restore and repair any corruption and replay any log files that did not get into the main database.  I was geting lots of errors trying to run ESEUTIL (I'll detail the errors in a later post).

2) Is it possible to restore (using NTBACKUP) Exchange databases to a new server?  I created a new server with the same name as the old one (outlined in the steps here: but when I try to restore to the server I get DatabaseNotFound Jet errors, which according to MS's site means that the destination database has a different name that the source database, although I have confirmed that they are exactly the same.

I'm restoring the file backup right now and will try ESEUTIL again; I'll post specific error messages as I get them.

All other Disaster recovery processes (AD, file, SQL) are going great, but if I can't get Exchange back, there'll be hell to pay...

Any help is GREATLY appreciated.


LVL 25
Who is Participating?
The method i use :

on the new server, install 2003 server & Sp + same hotfixes but NOT exchange

reset computer account in AD for the exchange server
rename the new by old server & change IP
join domain
install exchange with setup /disasterrecovery, install exchange  Service packs
install antivirus & other apps
Restore from your backup software

and VOILA !
dstanley9Author Commented:
Oh, if only it were that simple...

I have done all of that, and still cannot restore from backup.  

Do you use NT Backup or another method?  Do you restore to a Recovery Storage Group or directly back to the First Storage Group?

not a recovery storage group (only for resotre individual mailboxes on production server),

if you reinstall exchange with disasterrecovery, you only have to full restore the exchange databases

(don't mount database before restoring data)

i've test it lot of times without any problem
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

dstanley9Author Commented:
If you mount the stores before restoring, can you simply dismount and then restore?  Or do you have to delete the databases and start over?  Maybe that's what my problem was...
dstanley9Author Commented:
BTW, I'm not saying it doesn't work, I'm sure I'm just missing something stupid...

One other this to note, my domain controller is also a Virtual Server that was removed from the domain.  I seized all of the operations roles to that server after moving into lab environment.  Don;t know if that changes anything...

If you mount the stores before restoring; it will create log files and system files (E01.xx, ... ) then you need to dismount, delete database files, delete transaction & system files before restoring

dstanley9Author Commented:
I got it working - it was a version issue.  I had installed Exchange from my MSDN DVDs, which say "SP1" but when I reinstalled SP1 and re-mounted I got the database to mount.  I still had to run ESEUTIL since the database was in a dirty shutdown state, but I did not get any more jet errors.

I'll go ahead and give the points since you did answer my question.


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.

All Courses

From novice to tech pro — start learning today.