Exchange Server 2003 has a known compatibility issue with this version of Windows.
For more information, refer to http://go.microsoft.com/fwlink/?LinkId=37488.
http://support.microsoft.com/?kbid=555285
--------------------------------------------------------------------------------
Microsoft Support:
1-800-936-3500 (U.S. and Canada Only)
Exchange Server 2003 Disaster Recovery Operations Guide
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/disrecopgde.mspx
XADM: Exchange 2000 Server Eseutil Command Line Switches
http://support.microsoft.com/kb/317014/
XADM: ESEUTIL Command Line Parameters
http://support.microsoft.com/kb/182903/
Description of the Isinteg utility
http://support.microsoft.com/kb/182081/
Ramifications of running the eseutil /p or edbutil /d /r command in Exchange
http://support.microsoft.com/kb/259851/
Important It is always best to restore from a backup whenever possible.
--------------------------------------------------------------------------------
To reinstall a broken Exchange installation, manually remove using MS KB260378.
http://support.microsoft.com/default.aspx?scid=kb;en-us;260378
IIS may require re-installation more than once, start the SMTP service to
verify it is working correctly before reinstalling Exchange.
To reinstall, run "setup.exe /disasterrecovery" after successfully running
"setup.exe /forestprep" and "setup.exe /domainprep" from the Exchange CDROM.
Apply all previous Service Packs and Hotfix/Rollups.
If you use the "setup.exe /removeorg" switch, you will have to manually
recreate the Administrative group that the original Exchange install was in,
this is because the information store has the LDAP path encoded in. If the
original group was not named "First Administrative Group", you will have to
install the System Manager first, then create an administrative group with the
previous name, then install the Exchange Messaging components. It will not ask
you which group since there is only one group, it will automatically choose
the existing group (or create one: "First Administrative Group").
To perform an online restore, start all exchange services and dismount the
stores, check "database can be overwriten by restore" in System Manager, run
the restore process.
If using copied database files, it has been seen that MS tech support places
the E00.log file in a different directory before mounting an unknown state
store.
If you defragment or repair an Exchange database, transaction logs that
previously were associated with this database can no longer be replayed into
it. You cannot replay log files unless all uncommitted log files from the time
the database was last running are available. You must have all log files
starting from the checkpoint at the time the database was backed up. You can
then replay log files from this point as long as they follow an unbroken
sequence. If there is a single log file missing in the middle or from the
beginning of the sequence, replay stops there.
log files:
http://tinyurl.com/fuakf
--------------------------------------------------------------------------------
If you restore from a backup, you ensure that you have a good, clean,
stable, database that will start and run on your server. In almost every
circumstance, it is faster and more reliable to restore from a backup than
to perform a hard repair on the database. This is because the repair runs
at approximately 4 to 6 gigabytes (GB) per hour, and you must run the
Isinteg process after the repair, which runs at approximately 3 to 6 GB
per hour. (These rates are average; performance may vary depending on how
many passes the repair has to make on your database and the speed of the
hardware.)
If you use Eseutil to repair an Exchange database, you must have sufficient
free disk space for Eseutil to run. If you are running Eseutil /P you must
have approximately 20 percent of the size of the database you are repairingc
on the same drive. If you do not have that much room, you can use command-
line switches to redirect the temp files to a different location. If you are
using Eseutil /D, you must have 110 percent of the size of the database.
While you can redirect the temp files to another drive as you can with the
/P switch, it will dramatically increase the time it takes to repair your
database. If it is possible, have ample free space when using the /D switch.
If you have no backup, and no other option but to run a hard repair on your
database, follow these steps:
0. Backup or copy the databases for safety.
1. Run a hard repair on the database by using Eseutil /p or Eseutil /d /r.
2. Defragment the database by using Eseutil /d. Offline defragmentation
creates a new physical database structure and moves the existing data to
that structure.
3. Check the consistency of the database by using Isinteg -fix. You may
need to run Isinteg several times until the summary report returns no
errors (or: isinteg.exe fix test alltests).
If you only plan to salvage data from the disk, and do not plan to put it
back in production, you can skip step 2 earlier in this section. Skipping
step 2 will save time in your recovery process but might cause the database
to have indexing and space allocation errors. These errors are not what you
want in a production environment, but are unlikely to affect your ability to
salvage data from the database.
After you run the eseutil /p or edbutil /d /r command on the priv.edb or
pub.edb databases, the databases may exhibit the following symptoms:
The information store either will not stop or stops responding.
The information store stops accepting mail from the message
transfer agent (MTA).
E-mail remains in the Outboxes of the users.
The Store.exe program runs with very high CPU use with no load
on the server.
The Store.exe program generates an access violation if there is
a heavy load.
Users cannot open e-mail attachments or e-mail messages.
If Isinteg is run multiple times and does not correct the database corruption,
you must use the Exmerge utility to extract data from one database and place
it in another database: 259688 (http://support.microsoft.com/kb/259688/) How
to use the Exmerge utility to extract data from a damaged private information
store.
--------------------------------------------------------------------------------
Copy the Corrupted Databases for Repair
Make sure the databases you are copying have been shut down in a clean state.
Use Eseutil /mh to dump the header information for the database. Look for
State: Clean Shutdown in the dumped information.
exeutil /mh "path\to\db.edb"
If the database is in a dirty state, try to restore the database to a clean
state before you repair it. This task entails playing any required transaction
logs into the database. The Log Required field in the dump file from
Eseutil /mh will show you the logs that are required to restore the database
to a clean state. The logs shown in this field are shown in decimal, you must
convert these values to hexadecimal to find the appropriate transaction log
files.
In many cases, remounting the database causes soft recovery to start so that
the database can be shut down in a clean state.
--------------------------------------------------------------------------------
Replay Log Files, Eseutil /cc
1. After the last backup has been restored and you want to initiate a hard
recovery.
2. Navigate to the folder where the Restore.env file is located.
3. Type eseutil /cc. Do not use any other parameters.
4. When the transaction logs finish replaying successfully, the message,
"Operation completed successfully" appears.
Eseutil performs the same function as the Last Restore Set check box. Use all
other Eseutil /cc switches with extreme caution.
--------------------------------------------------------------------------------
Types of Recovery. There are two forms of recovery:
Soft recovery - A transaction log replay process that occurs when a database
is re-mounted after an unexpected stop, or when transaction
logs are replayed into an offline file copy backup of a
database.
Hard recovery - A transaction log replay process that occurs after restoring
a database from an online backup.