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.
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.
Setting up an export view for non-VersionVault access
An export view for non-VersionVault access exports a view-extended pathname to the VOB mount point.
Export configurations
Multihop configurations, in which the exported VOB and export view are not located on the same host, should be used only when there is no alternative.

Export configurations

Multihop configurations, in which the exported VOB and export view are not located on the same host, should be used only when there is no alternative.

About this task

Accessing data from a non-VersionVault host can involve three hosts:

The host on which the VOB resides
The host on which the export view resides
The non-VersionVault host

A multihop configuration, in which the VOB and its export view reside on different hosts, requires MVFS-level communication, which is slower than NFS communication, between the two HCL VersionVault hosts. In addition, a multihop configuration introduces the possibility of access cycles, in which two of the hosts depend on each other for network-related services, or such a dependency is created through vendor hosts. Such situations may result in time-outs (if VOBs are soft-mounted) or deadlocks (if VOBs are hard mounted).