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.
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.
Synchronization export problems
Problems encountered while during the export phase of synchronization typically are the result of not being able to find the appropriate oplog entry.
Oplog gap detected during creation of update packet
When running syncreplica –export, a warning that the command found a different oplog ID than expected can indicate a serious error, involving an unrecoverable data loss.

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.
  - 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.
    - General MultiSite troubleshooting tips
      Many problems can be clarified, if not solved, by examining the various log files, checking your system configuration, and listing the history of exports.
    - Replica export problems
      Common mkreplica –export problems include specifying a new replica name that matches one that already exists or having an old package left over from a previous failed run.
    - Replica import problems
      Common problems encountered while attempting to import an update packet include permissions issues, naming conflicts in the object or tag registry.
    - Synchronization export problems
      Problems encountered while during the export phase of synchronization typically are the result of not being able to find the appropriate oplog entry.
      - Cannot find oplog entry
        syncreplica –export can fail with a warning message about missing oplog entries.
      - Oplog gap detected during creation of update packet
        When running syncreplica –export, a warning that the command found a different oplog ID than expected can indicate a serious error, involving an unrecoverable data loss.
      - Export failure during version construction
        An export operation can fail when attempting to access an element that is being modified by a user.
      - Packets accumulate in outgoing storage bay
        Problems with packet delivery are recoverable errors. In many cases, the MultiSite automatic-retry capability recovers from errors.
      - Replica cannot update itself
        It is an error to specify a syncreplica –export command in such a way that you specify the sending replica as a destination for the exported packets.
    - Transport problems
      This section describes problems that can occur during the transport phase of synchronization.
    - Synchronization import problems
      This section describes problems that can occur during the import phase of synchronization.
    - Running epoch_watchdog
      The epoch_watchdog script checks whether a replica’s epoch numbers have rolled back without a restorereplica command being run.
    - Restoring and replacing VOB replicas
      Occasionally, a VOB storage directory is lost. This can occur because of a hardware failure (for example, disk crash), a software failure (for example, operating system-level file system corruption), or a human error (for example, an rm –fr or del command). If an unreplicated VOB storage directory is lost, you can restore a recent copy from backup and resume development work. The changes made between the time of the backup and the time of the failure are not recoverable.
    - Restoring replica storage that has been accidentally deleted
      This is the process to follow when a replica's storage directory is lost, and there is no backup to be restored.

Oplog gap detected during creation of update packet

When running syncreplica –export, a warning that the command found a different oplog ID than expected can indicate a serious error, involving an unrecoverable data loss.

syncreplica –export can fail with the following warning message:

Gap in oplog detected for replica replica-name.
Wanted oplog id: oplog-ID. Got oplog id: oplog-ID.

If the procedures described in Cannot find oplog entry do not work, contact HCL Customer Support.

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.