The vob_restore command restores a damaged VOB. It prompts for all required input and displays explanatory text at each step. If you quit vob_restore before it completes, you can use the –restart option to resume VOB restoration at the point where you stopped it.
If the VOB is replicated, you must run the MultiSite restorereplica command immediately after restoring the VOB from backup. For more information, see the Administrator's Guide.
Note: We strongly recommend that you do not retrieve VOB storage from backup until prompted to do so by vob_restore. If you get the VOB storage directory from backup media before running vob_restore, you must either unregister the VOB before retrieving the backup or stop ClearCase or ClearCase LT before retrieval and restart it afterward. If you wait until prompted, vob_restore performs the necessary steps, safeguarding the integrity of your restored VOB.
You must have one of the following identities:
If the VOB is still accessible, lock it to prevent any further changes. vob_restore leaves the VOB locked when it completes.
(Replicated VOBs only) No mastership restrictions.
If you do not specify all required command line arguments, vob_restore prompts for input.
Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.
Note: In this example, as is recommended, the restored data is not retrieved from backup media before running vob_restore.
checkvob, mktag, mkvob, restorereplica, vob_snapshot, vob_snapshot_setup, Administrator's Guide
Copyright© 2003 Rational Software. All Rights Reserved.