nco_check_store checkpoint verification utility

The nco_check_store utility verifies that existing checkpoint files are valid. It is intended to be used by automations and can be used only to check ObjectServer stores that are not currently in use.

The nco_check_store utility reports the validity of the checkpoint files with the following return codes:

  • 0: Success. The checkpoint files are valid.
  • 1: Failure. The checkpoint files are not valid and must not be used.

You can also use the nco_check_store utility from the command line. When invoked from the command line, you must set the message logging level to info to display the progress and results of the test.

Note: Do not run nco_check_store when the ObjectServer is running.

The command-line options for nco_check_store are described in the following table.

Table 1. Checkpoint verification utility command-line options 
Command-line option Description
-help Displays help on the command-line options and exits.
-memstoredatadirectory string Specifies the path to the ObjectServer database. The default is $NCHOME/omnibus/db.
-messagelevel string Specifies the message logging level. Possible values are: debug, info, warn, error, and fatal. The default level is error.
Messages that are logged at each level are as follows:
  • fatal: fatal only
  • error: fatal and error
  • warn: fatal, error, and warn
  • info: fatal, error, warn, and info
  • debug: fatal, error, warn, info, and debug
Tip: The value of string can be in uppercase, lowercase, or mixed case.
-messagelog string Specifies the path to which messages are logged. The default is stderr.
-server string Specifies the name of the ObjectServer database to verify. The default is NCOMS.
-version Displays version information on the checkpoint verification utility and exits.

Example usage

To use nco_check_store from within an automation to check that backup files created by the ObjectServer are valid, set the -memstoredatadirectory command-line option to the directory that contains the backup.