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.
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.
Moving VOBs
You cannot use an ordinary file-system copy utility to copy a VOB to another location. You must follow special procedures that maintain the integrity of VOB data and preserve permissions and ownership on VOB storage directories.

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.
    - Relocating elements to another VOB
      The cleartool relocate command moves elements to another VOB.
    - Moving VOBs
      You cannot use an ordinary file-system copy utility to copy a VOB to another location. You must follow special procedures that maintain the integrity of VOB data and preserve permissions and ownership on VOB storage directories.
      - Special procedures for replicated VOBs
        If you are moving a VOB replica to a new host, take the following steps first.
      - Moving a VOB on Windows®
        There are two primary use cases for moving a VOB on Windows®: moving a VOB to a host in the same Windows domain (or to a different partition on a Windows host), and moving a VOB to a host in another Windows domain.
      - Moving a VOB on Linux or the UNIX system
        There are two primary use cases for moving a VOB on Linux or the UNIX system: moving a VOB to a host that has the same architecture (binary data format) and moving a VOB to a host that has a different architecture.
      - Moving a VOB to a different operating system type
        When you move a VOB from a Windows® host to a host running Linux or the UNIX system or vice versa, all user identity information stored in the VOB storage directory and VOB database must change. The binary data format of the VOB database must change also.
      - Moving a VOB to network-attached storage
        All procedures for moving VOBs refer to the architecture, or binary data format, of the VOB host. VOB database formats are architecture-dependent, and the database must be reformatted if the VOB is moved to a host of a different architecture.
  - 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.
  - 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.

Moving VOBs

You cannot use an ordinary file-system copy utility to copy a VOB to another location. You must follow special procedures that maintain the integrity of VOB data and preserve permissions and ownership on VOB storage directories.

Procedures for moving VOBs are covered in the following scenarios:

Moving a VOB to another disk partition on Windows® or to another Windows® host in the same domain.
Moving a VOB to a Windows® host in a different domain.
Moving a VOB to another disk partition on Linux or the UNIX system or to another host running Linux or the UNIX system with the same architecture.
Moving a VOB to a host running Linux or the UNIX system, with a different architecture.
Moving a VOB from a Windows® host to a host running Linux or the UNIX system.
Moving a VOB from a host running Linux or the UNIX system to a Windows® host.

When moving VOBs, bear in mind that

Two hosts are said to have the same architecture when they have the same binary data format. Binary data format is controlled by CPU type, so platforms with the same CPU type have the same binary data format. Whenever you move a VOB to a host with a different architecture, it must be reformatted to the new host's binary data format.
In the case of ACL-protected VOBs, that platforms with the same architecture (such as Linux and the UNIX system) can have different ACL mechanisms that can require different copying and archiving procedures.
You can use the mkreplica command to move a VOB. If the VOB is ACL-enabled, the ACLs may or may not be preservable, depending on the source and target operating system types (and in the case of replicated VOBs, the MultiSite configuration as well). If you are moving a VOB from Windows to Linux or the UNIX system or vice versa, you must create a non-preserving replica because these platforms do not share the same namespace.
Lock the VOB before untagging and unregistering it to prevent lock failures on VOBs that reference other VOBs, such as a PVOB.
Remove any trigger scripts from the VOB before moving it. After moving the VOB, point the trigger scripts to the new location of the VOB.

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.