Load Recovery Log

The Load Recovery Log command imports the recovery log containing changes to your local repository in the event of a fatal error (such as an operating system crash). The recovery log is automatically maintained by CORE. As you make changes to any project in the local repository, CORE will transparently write information to the recovery log. Using this log, you can recover unsaved database changes.

If you find yourself in a situation where you need to use the recovery log, please call Vitech’s Customer Care Team first so that we can assist you with the process. Though the process is streamlined and automated, your project data is very important. Given the importance of recovering your data, we would like to work with you to ensure you are successful in completing the recovery.

When loading a recovery log, the first step is to select the file using the standard Windows open file dialog. The recovery log is written to the same directory as your repository file and uses the same file name with "_recover" appended.

Once you select the desired recovery log, CORE prompts you to specify which file contents you wish to recover. In maintaining the recovery log, CORE automatically marks when you last saved the repository to simplify the recovery process.

• Since Last Save - will load on the changes made since you last saved your repository. In general, this is the desired option.

• All file contents - will attempt to load all recovery file contents. If some of these changes have already been saved in your repository, you will receive conflict messages indicating any collisions.
• Cancel - will cancel the recovery operation.

When working on a remote project on a CORE Server, the server transparently writes all changes in real time and maintains a special transaction log. In the event that a CORE session terminates due to a local machine crash, your changes will have been automatically saved on the server. Therefore, there is no local recovery log maintained for changes made to remote projects.