Introduction to Exchange 2003 – Restore.env
When you restore an Exchange 2003 database, a file called restore.env is created automatically. If you are curious to know more about the contents of restore.env then this is the page for you.
Topics for Exchange 2003 – Restore.env
- Purpose of Restore.env
- Examine the Contents of Restore.env
- Hard Recovery of Exchange 2003
- Soft Recovery of Exchange 2003
We humans do not normally need to read restore.env. This is just a temporary environmental file holding path information about the data. Its purpose is to help the Exchange 2003 restore process find its files and match them with the corresponding email stores. However, if you wish, you can view the contents of restore.env using eseutil /cm, or if the restore.env file remains after a faulty restore, open it with notepad. See more about eseutil here.
To discover what’s in your restore.env run: eseutil /cm path to restore.env. Note: you probably need to navigate to the \Exchsrvr\Bin folder before executing the command.
Example of Restore.env contents
Microsoft(R) Exchange Server(TM) Database Utilities Version 6.0
Copyright (C) Microsoft Corporation 1991-2003. All Rights Reserved.
Restore log file: e:\restore
Restore Path: e:\restore
Annotation: Microsoft Information Store
Backup Instance: EnglandStorage
Restore Instance System Path:
Restore Instance Log Path:
Databases: 2 database(s)
Database Name: York1
Source Files: D:\Exchsrvr\EnglandStorage\York1.edb D:\Exchsrvr\EnglandStorage\York1.stm
Destination Files: D:\Exchsrvr\EnglandStorage\York1.edb D:\Exchsrvr\EnglandStorage\York1.stm
Database Name: York2
Source Files: D:\Exchsrvr\EnglandStorage\York2.edb D:\Exchsrvr\EnglandStorage\York2.stm
Destination Files: C:\RestoredDB\York2.edb C:\RestoredDB\York2.stm
Log files range: E0000001.log – E0000003.log
Last Restore Time: Fri Dec 31 18:00:00 2004
Recover Status: recoverNotStarted
Recover Error: 0x00000000
Recover Time: Tue Mar 1 13:30:15 2005
Operation completed successfully in 0.37 seconds.
Here is a free tool to monitor your Exchange Server. Download and install the utility, then inspect your mail queues, monitor the Exchange server’s memory, confirm there is enough disk space and check the CPU utilization.
This is the real deal – there is no catch. SolarWinds provides this fully-functioning freebie, as part of their commitment to supporting the network management community.
After you have physically restored the database files from backup, Exchange 2003 needs to get up-to-date. What it does is to replay all the transactions since that backup set. How does it do this? By reading the log files. Restore.env keeps a list of the all the database files and their paths so that restore can complete successfully.
Restore.env plays no part in a soft recovery. Here we have an automatic synchronization of the transaction logs with the database after an unexpected shutdown. The key file here is the checkpoint file. Exchange 2003 say’s ‘ Where was I before I was rudely shutdown? ‘. ‘ Ah I see from the checkpoint file (E0x.chk).
Kiwi CatTools is a free program for backing up configuration settings on hardware devices. Here is Guy’s challenge. If you download CatTools, then it will not only take care of backups, but also it will show you something new about the hardware on you network. I could give you a money back guarantee – but CatTools is already free! Thus, I just make a techie to techie challenge, you will learn more about your network if you:
Restore.env is a file created automatically during a normal Exchange 2003 restore. If you wish to examine the contents, then run eseutil /cm (path to restore.env).
- Mailbox Recovery
- Recovery Storage Group
- Alternative Forest Recovery
- Deleted Item Recovery
- Restore Horror Stories
- Restore. env
- Diagnostic Logging
- SMTP Logging
- Free Kiwi Syslog Analyzer
- Tips for Disaster Recovery