Restoring a member of an administrative VOB hierarchy
About this task
Note: If you are restoring a UCM component or PVOB, do not use these
procedures before you run checkvob –ucm. Doing so may
remove damaged cross-VOB hyperlinks that checkvob –ucm can
repair.
Although it is preferable to always back up members of an
administrative VOB hierarchy as a group, it is likely that you will restore
only a few members of a group at a time (for example, members stored on a
server whose disk has failed). Whenever you restore some, but not all, members
of an administrative VOB hierarchy, there is the possibility of a mismatch
in global type information. For example, if an administrative VOB is backed
up before a new global type is created, VOBs that are lower in the hierarchy
will exhibit problems related to the unavailable global type after that backup
is restored. To prevent such problems:
- After you restore an administrative VOB from backup, check for and fix any broken hyperlinks in that VOB and all other members of the hierarchy.
- After you restore any member of an administrative VOB hierarchy from backup, check for and clean up any broken hyperlinks from that VOB to its administrative VOB.
To remove broken hyperlinks, use checkvob –hlink. For more information, see Using checkvob to find and fix broken hyperlinks and the checkvob reference page.