How to Complete Manual Consistency Check Using nsrhsmck

You can also check the consistency of HSM-managed filesystems manually. The nsrhsmck command checks and corrects the consistency of HSM-managed filesystems and deals with cases in which the stubs files are renamed or deleted from the client filesystem. The basic syntax of the nsrhsmck command is:

# nsrhsmck -cdfv -s server-name path

You must specify a path on the command line when you run nsrhsmck. Only files and index entries that fall under the specified path are examined for consistency.

If you rename the stub file on the client machine, Backup cannot recall the migrated file to its original location. Before you can recall the file, you must use the nsrhsmck -f command to update the client index to reflect the new name.

If you delete the stub file from the client machine, you can recover the stub file from backup media, then recall the actual file.

If you want to delete a migrated file, delete the stub file from local disk, then use the nsrhsmck -d command to mark the client index entry for the migrated file as possibly deleted. After 60 days, use the nsrhsmck -c command to remove the expired entries from the client index. Backup no longer tracks the migrated file and the file cannot be recalled.

Before an entry is deleted from the client index, Backup checks to make sure the file does not exist on disk. If a file marked as possibly deleted is detected on disk before the index entry is deleted, the index entry will be unmarked as a possible deletion.