verifyChecksums

The verifyChecksums command enables you to perform a checksum analysis of your backed up database files or your restored system to verify that the files have not been corrupted by a hardware or environmental problem during the backup or restore process.

Information or errors from the checksum verification operation are recorded in the checksum.log file located in the directory specified by using the path argument if the ActivityLogDirectory parameter is not specified in the [PersistentDb] section of the JADE initialization file.

The checksums verification operation is driven from the backupinfo file in the specified backup directory or the restoreinfo file in the database system directory.

Perform a checksum analysis of any backup that has been moved across media, especially if transferred across a network.

Specify the optional workers argument if you want to use a single worker thread (1) or more than the default two (2) multiple concurrent worker threads. The verifyChecksums operation can use a maximum of 16 multiple concurrent worker threads.

The syntax of the verifyChecksums command in the jdbutilb command line is as follows.

jdbutilb path=database-path
         ini=initialization-file-name
         verifyChecksums [workers=number-of-worker-threads]

This command performs a checksum analysis of files in the directory specified by the path argument or the ActivityLogDirectory parameter in the [PersistentDb] section of the JADE initialization file and returns a result for batch file ERRORLEVEL checking.

The following are examples of the checksum verification commands for backed up and restored files, respectively.

jdbutilb path=d:\jade\backup\offline\compressed ini\jade\jade.ini verifyChecksums workers=3
jdbutilb path=d:\jade\system ini=d:\jade\jade.ini verifyChecksums