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.
Restoring critical HCL VersionVault data
If you have implemented a sound backup strategy for HCL VersionVault data, it should be easy to restore that data, if necessary.
Synchronizing VOBs and views after you restore
VOBs and views maintain persistent references to each other. These references, which are backed up and restored along with the VOB and view data, might need to be corrected after you restore a VOB or view.
Re-establishing the consistency of a dynamic view's derived object state

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.
  - HCL VersionVault network planning and administration
  - License servers and license administration
    Most HCL VersionVault applications and commands (cleartool commands, for example, or GUIs such as the VersionVault Explorer) require a license to run.
  - Reconfiguring VersionVault to use a different JRE
    When you change the Java Runtime Environment (JRE) for HCL VersionVault, you must reconfigure the product to make it work with the new JRE.
  - Administering the HCL VersionVault registry
    The HCL VersionVault registry is a central repository of information about shared resources such as VOBs and views.
  - HCL VersionVault network administration in mixed environments
    An HCL VersionVault environment that includes hosts that run Windows and hosts that run the UNIX system or Linux is said to be a mixed environment.
  - Overview of security considerations
    As an administrator, you are responsible for the security of your HCL VersionVault deployment.
  - VOB and view access control
    HCL VersionVault supports a rich set of access controls on versioned objects.
  - VOB administration
    Because VOBs are the principal repository for artifacts under HCL VersionVault control, VOB administration is one of the HCL VersionVault administrator’s most important tasks.
  - VOB datatypes and administrative VOB hierarchies
    There are many types of VOB metadata. Some are unique to a particular VOB, but many must be managed consistently across a group of VOBs that store related artifacts (components of a UCM project, for example). These topics introduce VOB metadata and describe how to use administrative VOB hierarchies to simplify sharing of type objects among related VOBs.
  - Moving VOBs and relocating VOB data
    HCL VersionVault includes tools for moving data and metadata to another VOB and for moving entire VOBs to another disk or host. You may need to use these tools to reorganize VOB directories, redistribute data storage, or rebalance server loads.
  - Views and view administration
    A view provides a workspace where users access versions of file and directory elements that are under HCL VersionVault control. Views can also contain view-private file system objects (such as ordinary files and directories) that are not under HCL VersionVault control.
  - Backing up critical HCL VersionVault data
    Like all databases, VOBs, views, and the HCL VersionVault registry have special backup and restore requirements.
  - Restoring critical HCL VersionVault data
    If you have implemented a sound backup strategy for HCL VersionVault data, it should be easy to restore that data, if necessary.
    - Before you restore
      Whenever you restore a VOB, a view, you are introducing an artifact from an earlier time into an environment in which that artifact’s history is often critical.
    - Restoring a VOB from backup with vob_restore
      The vob_restore utility automates many of the routine steps involved in restoring a VOB from backup.
    - Restoring a VOB from backup without vob_restore
    - Restoring a VOB on network-attached storage
      You cannot use vob_restore to restore a VOB whose database is stored on a NAS device.
    - Restoring ACL-protected VOBs
      Restoring ACL-protected VOBs calls for special attention to handling the ACLs correctly.
    - Restoring an individual element from backup
      If you mistakenly delete an element with the rmelem command, you can restore it from a VOB backup. This procedure cannot be used to restore an element to a UCM component.
    - Restoring a view from backup
    - Synchronizing VOBs and views after you restore
      VOBs and views maintain persistent references to each other. These references, which are backed up and restored along with the VOB and view data, might need to be corrected after you restore a VOB or view.
    - Restoring one or more members of a set of related databases
      You must consider the relationships among VOBs when backing them up and, especially, when restoring 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.
  - Importing data
    HCL VersionVault includes several utilities for importing data from other configuration management systems or directly from the file system itself.
  - Troubleshooting
    These topics cover a variety of procedures that administrators might need to follow to find and fix problems.
  - Improving client host performance
  - Improving VOB host performance
  - Configuring cross-platform file-system access
  - HCL VersionVault and Windows® domains
  - Configuring non-VersionVault access on Linux® or the UNIX system
    You can configure an HCL VersionVault host running Linux® or the UNIX system to support access to VOBs and dynamic views from computers that do not run HCL VersionVault.
  - Configuring HCL VersionVault for high availability
  - Estimating VOB size
    If you can estimate the number of elements, versions, and derived objects that a VOB will ultimately contain, you can compute a very rough estimate of the size of a VOB that can accommodate them. VOB storage includes a database and pools. On Windows®, the database and pools must reside on a single disk partition. On Linux® or the UNIX system, the pools can be located on a different partition or host, using symbolic links.
  - Administering the VersionVault WAN server
  - About VersionVault WAN server parallel view loading
  - Administering and using CMI task-provider integrations
    HCL VersionVault supports integrations with task providers such as HCL Compass through the Change Management Interface (CMI). The integrations require some configuration tasks, after which you can work with UCM activities or base VersionVault branches that are associated with the tasks.
- Administering platforms for HCL VersionVault
  Learn how to perform HCL VersionVault administrative tasks on supported platforms.
- Administering HCL VersionVault MultiSite
  Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.

Re-establishing the consistency of a dynamic view's derived object state

About this task

After you restore a VOB from backup, its VOB database mght be out of date with respect to certain derived objects. The old database does not store config records for any DOs that were created in subsequent builds. As a result, errors occur during hierarchical builds that reuse those late-arriving DOs to construct higher-level targets. In the typical case, clearmake displays an INTERNAL ERROR message and writes an entry of the following form in the error_log file:

missing config record for derived object (OID) "0b5759d0.fb1811cc.a0af.08:00:69:02:2e:aa"

Procedure

Determine which DOs are causing the inconsistency.
The cleartool ls command annotates them with [no config record].
cleartool ls
bldr_comm.ugh@@09-Dec.18:26.287028 bldr_cr.msg.o [no config record] bldr_cr.o [no config record] bldr_cr_cache.msg.c@@24-May.20:51.42929 . . .
Remove the DOs that have no config record.
Use an operating system command such as rm or del.
rm bldr_cr.msg.o bldr_cr.o

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.