The ccm fs_check command is responsible
for ensuring that the metadata, cache, and archive portions of a database
are consistent.
In Release 7.1 and later, the ccm fs_check command
checks for the existence of archives for static versioned objects.
- If a versioned object was recently checked in it but does not
have an archive, the archiver did not process the object. This behavior
is normal and is not an error.
- If an object was checked in without an archive for a longer time
than specified by a user, the archiver might not be running. You receive
a warning.
- The ccm fs_check command has a new /c|/cutoff cutofftime option.
Any object versions that are checked in before the cutoff time but
not yet archived produce a warning. The default cutoff is two days, /2:0:0:0.
You receive a warning for any unarchived files that were checked in
earlier than the day before yesterday.
- After the archive is checked, the check for unused archive files
function now uses less memory than in Release 7.0 and earlier.
You must resolve all errors and warnings before you start the archive
conversion. Here are some of the commonly reported errors and warnings
from the ccm fs_check command and some possible steps
to resolve the errors: