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.
MultiSite operation
VOB objects and VOB replica objects
Each replica is a VOB, but the VOB object and VOB-replica object are different objects in the VOB database.

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
    - Information propagated among VOB replicas
      Not all information is replicated across replicas. (For example, in general, site-specific information is not replicated.) This section shows what information is and is not propagated among replicas.
    - VOB objects and VOB replica objects
      Each replica is a VOB, but the VOB object and VOB-replica object are different objects in the VOB database.
    - Mastership
    - Conflict resolution
    - The operation log
  - 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.
  - 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.

VOB objects and VOB replica objects

Each replica is a VOB, but the VOB object and VOB-replica object are different objects in the VOB database.

Specifically:

VOB object: The database has a single VOB object. This object’s UUID is listed as the VOB family uuid in a lsvob –long listing.
VOB-replica object (or replica object): The database has a VOB-replica object for each of the VOB’s replicas. This object’s UUID is listed as the Vob replica uuid in a lsvob –long listing.

For example:

cleartool lsvob –long /vobs/dev 
Tag: /vobs/dev
...
Vob family uuid: 87f6265b.72d911d4.a5cd.00:01:80:c0:4b:e7
Vob replica uuid: 87f6265f.72d911d4.a5cd.00:01:80:c0:4b:e7
Vob registry attributes: replicated

Use describe vob: to list details about the VOB object; use describe replica: to list details about the VOB-replica object (the replica). For example:

cleartool describe vob:/vobs/dev replica:boston_hub@/vobs/dev 
versioned object base "/vobs/doc" 
  created 15-Aug-01.14:19:48 by susan.user
  "Main source VOB for development."
  master replica: boston_hub@/vobs/dev
  replica name: boston_hub 
  VOB family feature level: 3
  VOB storage host:pathname "goldengate:/vobstg/dev.vbs"
  VOB storage global pathname "/net/goldengate/vobstg/dev.vbs"
...
replica "boston_hub" 
  created 15-Aug-01.14:19:48 by susan.user
  replica type: unfiltered
  master replica: boston_hub@/vobs/dev
  request for mastership: enabled
...

All replicas of a VOB record the same VOB object and set of VOB-replica objects. When a new replica is created, it takes some time for the change (creation of a new VOB-replica object) to be propagated to all the replica’s databases.

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.