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.
Administering replicas
Managing mastership
Changing mastership of VOB objects
When you create an object in a replicated VOB, your current replica is the new object’s master replica. To transfer mastership of the object to another replica, use the chmaster command or the Properties Browser (Windows®).
Transferring mastership of all objects mastered by a replica
Before removing a replica, you must transfer mastership of all objects mastered by that replica, using the chmaster –all command.

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 the CLI and native GUIs
    - Managing mastership
      - Mastership commands for VOB objects
        You can use the command-line interface to manage mastership of VOB objects. On Windows®, many of the VersionVault and MultiSite interfaces (for example, Check Out, the Properties Browser, Request for Mastership, and so on) contain extended functionality that also supports managing mastership.
      - Displaying mastership information for VOB objects
        Mastership information that can be displayed for VOB objects includes the master replica of an object, all objects mastered by a particular replica, the mastership changes for an object, and settings for mastership requests.
      - Assigning branch mastership during element creation
        By default, when you create an element in a replicated VOB, mastership of the branch main for that element is assigned to the replica that masters the branch type main. You can override this default behavior by explicitly assigning mastership of the main branch when you create the element.
      - Changing mastership of VOB objects
        When you create an object in a replicated VOB, your current replica is the new object’s master replica. To transfer mastership of the object to another replica, use the chmaster command or the Properties Browser (Windows®).
        Transferring mastership of a type object
        When you create a type object, it is mastered by the replica where you create it. You can change the mastership of the type object using the chmaster command.
        Transferring mastership of a replica object
        When you create a new replica, its replica object is mastered by the replica at which you enter the mkreplica –export command. You can change the mastership of the replica object using the chmaster command.
        Transferring mastership of a VOB
        When you replicate a VOB for the first time, the VOB is mastered by the original replica. You can change the mastership of the VOB using the chmaster command.
        Transferring mastership of an element
        When you create a new element, it is mastered by the replica in which you create it. You can change the mastership of the element using the chmaster command.
        Transferring mastership of a branch
        When a branch is created, it is mastered by the replica that masters the branch type. This is called default mastership. When you transfer mastership of a branch to another replica, using the chmaster command, that replica now masters the branch. This is called explicit mastership.
        Transferring mastership of a stream
        The chmaster –stream command transfers mastership of a stream and its associated objects.
        Transferring mastership of all objects mastered by a replica
        Before removing a replica, you must transfer mastership of all objects mastered by that replica, using the chmaster –all command.
      - Fixing an accidental mastership change
        If a mastership change is made in a replica by mistake, you can fix the problem by following the steps that are described in this topic.
      - Working with type objects
        When you create an attribute type, a hyperlink type, or a label type, you can make the type shared or unshared.
    - Implementing requests for mastership
      To support development of VOB elements that cannot be merged, you can give developers the ability to request mastership of branches and branch types.
  - 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.

Transferring mastership of all objects mastered by a replica

Before removing a replica, you must transfer mastership of all objects mastered by that replica, using the chmaster –all command.

About this task

The following example shows a partially successful chmaster –all command and describes how to fix it. In this example, the administrator at replica bangalore is transferring mastership to boston_hub.

RAMOHALLI> multitool chmaster –all –long boston_hub@\dev
Changed mastership of versioned object base \dev\
Changed mastership of directory element \dev\.@@
Changed mastership of directory element \dev\lost+found@@
...
multitool: Error: Branch type "bangalore_main" has branches (with 
default mastership) that have outstanding checkouts.
Changed mastership of branch type v1.0_bugfix
...
multitool: Error: Lock on label type "V1.0_BUGFIX" prevents operation 
"change master".
Changed mastership of label type BANGALORE_V2.0
...
Changed mastership of replica bangalore
multitool: Warning: Not all objects had mastership changed.

These errors prevent the successful completion of this chmaster command:

There are checkouts on the bangalore_main branch.
There is a lock on a label type.

Procedure

Find the checkouts and either check in the files or cancel the checkouts:

H:\dev> cleartool lscheckout –all
03-Jun.17:28 jk checkout version "\dev\cmdsyn.c" from 
\main\bangalore_main\83 (unreserved)
08-Jun.12:45 singh     checkout version "\dev\etc\util\tool.c" from 
\main\bangalore_main\22 (unreserved)
...

See the checkin, checkout, and uncheckout reference pages.

Unlock the type object.

cleartool unlock lbtype:V1.0_BUGFIX@\dev
Unlocked label type "V1.0_BUGFIX".

Alternatively, enter a lock –replace –nusers command and add yourself to the –nusers list.

cleartool lock –replace –nusers ms_admin lbtype:V1.0_BUGFIX@\dev
Locked label type "V1.0_BUGFIX".

Reenter the chmaster command.

RAMOHALLI> multitool chmaster –all –long boston_hub@\dev
Changed mastership of branch type bangalore_main
Changed mastership of label type V1.0_BUGFIX
Changed mastership of all objects.

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.