Recipe6.11.Finding the Low Anchor Log File


Recipe 6.11. Finding the Low Anchor Log File

Problem

You need to determine the anchor log file (i.e., the last consistent log file) to replay logs.

Solution

Using a command-line interface

  1. Dismount the store using the technique described in Recipe 6.8.

  2. Run eseutil to determine the low anchor log file:

    > \path\Exchsrvr\bin\eseutil.exe /mh \path\to\database.edb | find /I "consistent"

The output from this command will list the suffix of the last consistent log file, in decimal for Exchange 2000 and in hexadecimal for Exchange Server 2003. In the following output from Exchange Server 2003, the number 0x9 when appended to the default log file prefix indicates that the low anchor log file would be E0000009.LOG. To determine the log file prefix for Exchange 2000, first convert from the decimal output to hex.

  Last Consistent: (0x9,1D25,36)  09/20/2004 04:44:00

Discussion

If you have an offline backup that you wish to recover, and you want to replay transaction logs to restore up to the point of failure, you need to identify the low anchor log file. This is the first in the series of log files that must be replayed to restore all available transactions back into the Exchange database. You must ensure that you have all log files from the low anchor log file forward to the log file that contains the point-of-failure transactions (the high anchor log file). To know which log files you need to restore from your offline backup, you'll need to be able to find the anchor log file; once you've done that, you can move on to restoring the offline backup, as described in Recipe 11.12.

See Also

Recipe 6.8 for dismounting the store, and MS KB 296788 (Offline Backup and Restoration Procedures for Exchange)



Exchange Server Cookbook
Exchange Server Cookbook: For Exchange Server 2003 and Exchange 2000 Server
ISBN: 0596007175
EAN: 2147483647
Year: 2006
Pages: 235

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net