Open topic with navigation

You are here: Verification > Configuring the verification log

Configuring the verification log

A verification log is created on the source during the verification process. The log identifies what is verified as well as which files are not synchronized.

  1. Right-click the source server on the left pane of the Replication Console and select Properties.

  2. Select the Logging tab.

  3. At the top of the window, Folder identifies the location where the log files identified on this tab are stored. By default, the log files are stored in the same directory as the Double-Take Availability program files.
  4. Under the Verification section, Filename contains the base log file name for the verification process. The replication set name will be prepended to the base log file name. For example, since the default is DTVerify.log, the verification log for the replication set called UserData would be UserData DTVerify.log.
  5. Specify the Maximum Length of the log file. The default is 1048576 bytes (1 MB). When the log file reaches this limit, no additional data will be logged.

  6. By default, the log is appended to itself each time a verification process is completed. Clear the Append check box if you do not want to append to the previous log file.

    Changes made to the verification log in the Server Properties, Logging tab will apply to all connections from the current source machine.

     

  7. Specify the Language of the log file. Currently, English is the only available language.
  8. Click OK to save the settings.

In the log file, each verification process is delineated by beginning and end markers. A list of files that are different on the source and target is provided as well cumulative totals for the verification process. The information provided for each file is the state of its synchronization between the source and the target at the time the file is verified. If the remirror option is selected so that files that are different are remirrored, the data in the verify log reflects the state of the file before it is remirrored, and does not report the state of the file after it is remirrored. If a file is reported as different, review the output for the file to determine what is different.

Related Topics