Ignite-UX CHECK_RECOVERY

Ignite-UX CHECK_RECOVERY

check_recovery compares the current state of the system to the System Recovery status file (created by the last invocation of make_recovery) to determine if a new System Recovery Tape needs to be created. Only Core OS and User Core OS files are validated. Refer to make_recovery for an explanation of these terms.
check_recovery displays all discrepancies found between the current system and the status file to stderr. Based on these, the System Administrator can then make a determination as to whether a new System Recovery Tape needs to be created.

check_recovery detects the following discrepancies:

Additions: A file existing on the current system and not listed in the System Recovery status file is a file added to the system since the last System Recovery Tape was created.

Deletions: A file not existing on the current system and listed in the System Recovery status file is a file deleted from the system since the last System Recovery Tape was created.

Modifications: A file existing on the current system but with a different “last modification date” is further validated via its checksum. If the file’s checksum is different from the value in the System Recovery status file, then the file has been modified.
check_recovery can be invoked only by a user who has superuser privileges. It has no options.

Install make_recovery tape into tape drive.
Type: check_recovery

Click Here for additional information on Ignite or to learn about Ignite installation services offered by Beechglen including validating Ignite images on a system in our lab.