Before you restore

Whenever you restore a VOB, a view, or (if you use Rational® ClearQuest® in a UCM environment) a Rational ClearQuest database, you are introducing an artifact from an earlier time into an environment in which that artifact’s history is often critical.

Before you restore any of these databases, consider the implications of the restore operation on other databases in your community.

After you restore an ordinary VOB or UCM component VOB from a vob_snapshot backup, you must check and fix any discrepancies between the VOB’s database and its pools. Restoring a VOB from backup with vob_restore and Restoring a VOB from backup without vob_restore provide details on this procedure.
If you need to restore individual elements that have been inadvertently removed from a VOB with the rmelem command, follow the procedure described in Restoring an individual element from backup.
Note: When restoring VOBs, it is helpful to understand the file-system layout of VOB storage directories, as described in The VOB storage directory.
After you restore an ordinary VOB or UCM component VOB, you must resynchronize the VOB with any views that hold references to it. See Synchronizing VOBs and views after you restore for the procedures.
After you restore a view, you must resynchronize the view with any VOBs to which it holds references. See Synchronizing VOBs and views after you restore for the procedures.
If you use UCM and Rational ClearQuest, a number of relationships between VOB, PVOB, and Rational ClearQuest databases must be reconciled after any of these databases is restored. These relationships, along with procedures for detecting and correcting discrepancies in them, are described in Restoring one or more members of a set of related databases.