Home
Administering
Learn how to administer the product.
Administering HCL VersionVault
Learn about performing administrative tasks for an HCL VersionVault community including managing software licenses, user and group accounts, VersionVault server and client hosts, shared data, and the network that connects them.
Periodic maintenance
Periodic attention to storage management and repository integrity is an important administrative function. These topics describe VOB and view storage management tasks, the checkvob utility, and the HCL VersionVault scheduler, which you can use to automate many periodic maintenance chores.
About checkvob
VOBs have complex internal and external relationships that can sometimes be disrupted by system or network failures or when a VOB is restored from backup. checkvob is a cleartool subcommand that can find, and in many cases fix, a variety of problems in these relationships.
Using checkvob to find and fix internal VOB inconsistencies
A VOB storage directory contains a VOB database and a number of storage pools. Any operation that modifies VOB data makes changes to the database and at least one pool. When inconsistencies arise between the contents of a VOB database and the contents of its pools, VOB data integrity may be damaged.
Missing and unreferenced data containers
checkvob works to reconcile the contents of VOB storage pools with the information in the VOB database. This reconciliation requires checkvob to categorize data containers based on their relationship to this information.
Source pool: missing container

Source pool: missing container

Description: The VOB database references a source pool data container that does not exist at the expected location.
Causes: Any of the following, depending on whether the database or the pool has the more recent reference time:
- (Database newer) The database records a checkin that is not found in the (older) pool.
- (Pool newer) Pool stores updated, renamed container with new checkin data, but the older database references the old container name, which no longer exists.
- (Pool newer) Pool stores updated container to reflect versions removed with rmver or rmbranch, but the database references old container.
- (Pool or database reference times differ) A chpool operation on a file element in the interval between pool and database reference times leaves the database pointing at wrong pool.
- Unexpected events.
Fix processing: Examine any unreferenced containers. If a container is found that has the correct data (or a subset or superset of the correct data), create a new container and copy in the referenced (subset of) data. If –force is specified or the fix? prompt is accepted, update the VOB database to reference reconstructed containers. Display a list of versions that could not be recovered.