Home
Administering
Learn how to administer the product.
Administering HCL VersionVault MultiSite
Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.
Using MultiSite for VOB backup and interoperability
You can use HCL VersionVault MultiSite to back up a VOB and to provide access to VOBs in a heterogeneous network.
Backing up VOBs with MultiSite
You can use HCL VersionVault MultiSite to perform VOB backups.
Using a backup replica
To back up a VOB consistently, the VersionVault administrator must lock the VOB. However, many administrators cannot find convenient times to lock the VOB so that the lock does not interfere with development work. One solution is to use MultiSite to create a replica of a VOB in the same local area network as the original.
Handling objects that are not replicated
When using HCL VersionVault MultiSite as a VOB backup strategy, one of the most important things to note is that some objects in a VOB are not replicated.

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.
- 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.
  - Introduction
    HCL VersionVault MultiSite adds a powerful capability to HCL VersionVault. With MultiSite, developers at different locations can use the same HCL VersionVault versioned object base (VOB). For HCL VersionVault, each location (site) has its own copy (replica) of the VOB. At any time, changes made in one replica can be sent in update packets to other replicas. You can manage replicas by using the command-line tools.
  - MultiSite operation
  - Implementation planning
    Before you install and use HCL VersionVaultHCL Compass MultiSite, you need to plan your implementation.
  - MultiSite command set
    This section summarizes the commands for HCL VersionVault MultiSite and HCL VersionVault that display HCL VersionVault MultiSite information. There are a series of MultiSite commands and API functions that display or modify MultiSite information.
  - Packet transportation methods and configuration
    The method you choose for transporting packets between replicas depends on connectivity. If your replicas do not have IP connectivity, you must use a file-based transport method. If your replicas have connectivity, you can use the store-and-forward facility.
  - Feature levels
    Feature levels allow different replica hosts in a VOB family to run different versions of HCL VersionVault. You can raise the feature level of either a single replica host or an entire VOB family.
  - Creating VOB replicas
    Before creating a replica, you must make decisions about branching, mastership, identities and permissions preservation, and method of packet delivery.
  - Replica synchronization
    Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
  - Administering replicas
  - Using MultiSite for VOB backup and interoperability
    You can use HCL VersionVault MultiSite to back up a VOB and to provide access to VOBs in a heterogeneous network.
    - Backing up VOBs with MultiSite
      You can use HCL VersionVault MultiSite to perform VOB backups.
      - Using a backup replica
        To back up a VOB consistently, the VersionVault administrator must lock the VOB. However, many administrators cannot find convenient times to lock the VOB so that the lock does not interfere with development work. One solution is to use MultiSite to create a replica of a VOB in the same local area network as the original.
        Handling objects that are not replicated
        When using HCL VersionVault MultiSite as a VOB backup strategy, one of the most important things to note is that some objects in a VOB are not replicated.
        Designing synchronization strategy
        When using HCL VersionVault MultiSite as a VOB backup strategy, you must determine the frequency and direction of synchronization.
      - Using replicas with incremental backup
        When you use a replica as an incremental backup of a VOB, you still back up the original VOB. You set up a replica of the original VOB in the same local area network, and schedule frequent unidirectional synchronizations. If you restore the original VOB from backup, the replica serves as an incremental backup by supplying changes made since the last backup.
      - Restoring a replica from backup
        If you lock your primary replica to back it up, you must restore it from the backup medium and perform the restorereplica procedure.
    - Using MultiSite for interoperability
      You can use multiple replicas in local area networks to provide native access to VOBs in a heterogeneous network.
  - Troubleshooting MultiSite operations
    When you encounter a situation where running an HCL VersionVault MultiSite command produces an unexpected result, or produces a warning or error message, the information in this section can assist you in troubleshooting the problem.

Handling objects that are not replicated

When using HCL VersionVault MultiSite as a VOB backup strategy, one of the most important things to note is that some objects in a VOB are not replicated.

The following objects are not replicated, and therefore are not restored from backup:

Derived objects: After a recovery from backup, developers must rebuild derived objects associated with the VOB. Checked-in derived objects are replicated, so they are backed up.
Triggers: To ensure that you can re-create triggers after a restoration from backup, you must record information about all triggers in a VOB replica. For example, use the command lstype –kind trtype to list all triggers in a VOB, use the describe trtype: command to list details about each trigger, and then save that information somewhere outside the VOB.
Nonobsolete locks: As with triggers, you must record information about nonobsolete locks. You can write scripts that capture and re-create the trigger and lock information.
VOB properties: Certain VOB properties: the state of synchronous request for mastership (SRFM) enablement, the state of atomic checkin enablement, access controls that are set by the reqmaster command, and the minimum client feature level.

Also, pool assignments are specific to a replica, so re-creating the replica from a backup replica can undo changes made to them. If you make major changes to a VOB’s pool structure, use the chpool command to duplicate these changes at the backup replica. (At replica creation, you can also use the –pooltalk option with mkreplica –import to make pool assignments.)

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.