Microsoft KB Archive/253914

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Article ID: 253914

Article Last Modified on 2/21/2007



APPLIES TO

  • Microsoft Exchange 2000 Server Standard Edition



This article was previously published under Q253914


SUMMARY

The contents of the Restore.env file can be dumped using the eseutil.exe utility. To dump Restore.env, run the following command:

Eseutil /cm directory where restore.env is located


MORE INFORMATION

For example, if Restore.env is located in the C:\TempRest directory, run the following command:

Eseutil /cm c:\temprest


You should then see output similar to the following:

   Microsoft(R) Exchange Server(TM) Database Utilities
   Version 6.0
   Copyright (C) Microsoft Corporation 1991-2000.  All Rights Reserved.

             Restore log file: d:\TempRest

                 Restore Path: d:\TempRest
                   Annotation: Microsoft Information Store
              Backup Instance: MyStorageGroup
              Target Instance:
    Restore Instance System Path:
       Restore Instance Log Path:

                    Databases: 2 database(s)
                        Database Name: MyDatabase1
                                 GUID: A2CFF078-782F-4BFE-43944BFEA1B46055
                         Source Files:    D:\Exchsrvr\MyStorageGroup\MyDatabase1.edb    D:\Exchsrvr\MyStorageGroup\MyDatabase1.stm
                    Destination Files:    D:\Exchsrvr\MyStorageGroup\MyDatabase1.edb    D:\Exchsrvr\MyStorageGroup\MyDatabase1.stm

                        Database Name: MyDatabase2
                                 GUID: 6ACF4E55-C7D6-433E-88AD433E9CD5CF03
                         Source Files:    D:\Exchsrvr\MyStorageGroup\MyDatabase2.edb    D:\Exchsrvr\MyStorageGroup\MyDatabase2.stm
                    Destination Files: C:\RestoredDB\MyDatabase2.edb    C:\RestoredDB\MyDatabase2.stm



              Log files range: E0100003.log - E0100004.log
            Last Restore Time: Wed Dec 31 18:00:00 1969

               Recover Status: recoverNotStarted
                Recover Error: 0x00000000
                 Recover Time: Fri Feb 11 13:30:15 2000

   Operation completed successfully in 0.78 seconds.
                

Important Values in the Restore.env File

  • Restore log file and Restore Path: This is the location of the Restore.env file and the files that come from the tape that is needed to recover the database (.log, .pat files); it is specified by the user during restore.
  • Backup Instance: Storage group that the database (or databases) belongs to.
  • Databases: Number of databases restored. A database consists of an EDB and an STM file.NOTE: The next four values (Database Name, GUID, Source Files, and Destination Files) refer to one database. If multiple databases are restored, these values are shown once for each database.


  • Database Name: The name of the database.
  • GUID: The globally unique identifier for the database.
  • Source Files: The paths to the database files when they were backed up.
  • Destination Files: The paths to the database files when they were restored.


NOTE: In the sample Restore.env file, note that MyDatabase2 was moved between the time that it was backed up and the time it was restored.

  • Log files range: The range of log files (inclusive) that were restored. All of the log files must be present to run recovery.
  • Recover Status: Displays "recoverNotStarted" if recovery has not been attempted, and "recoverEnded" if recovery was started but did not finish.
  • Recover Error: Contains error code if recovery was started but encountered an error and could not finish.
  • Recover Time: Either the time when the Restore.env was created or the last time recovery started but didn't finish.



Additional query words: x2kinfoht RIP restore in progress key hard recovery

Keywords: kbhowto kbinfo KB253914