Home
Administering
Learn how to administer the product.
Administering platforms for HCL VersionVault
Learn how to perform HCL VersionVault administrative tasks on supported platforms.
Using network-attached storage devices with HCL VersionVault
Using a network filer for ACL-enabled VOB storage
When you use a network filer to hold your VOB storage directories, follow this guidance to configure the VOB storage host and the filer.
NFS version 4 requirement
Because VersionVault with ACLs uses file system ACLs on the container files in a VOB storage pool (source containers and cleartext containers), your network filer must support NFS version 4 with ACLs. VersionVault needs the AUTH_SYS user identity option. It is not supported by other AUTH_* identity systems.

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.
  - HCL VersionVault on Windows™
  - HCL VersionVault on the UNIX system and Linux
  - Using network-attached storage devices with HCL VersionVault
    - Device-specific procedures
    - Using a network filer for ACL-enabled VOB storage
      When you use a network filer to hold your VOB storage directories, follow this guidance to configure the VOB storage host and the filer.
      - NFS version 4 requirement
        Because VersionVault with ACLs uses file system ACLs on the container files in a VOB storage pool (source containers and cleartext containers), your network filer must support NFS version 4 with ACLs. VersionVault needs the AUTH_SYS user identity option. It is not supported by other AUTH_* identity systems.
      - Using explicit NFS mounts
        For safest behavior (not subject to autofs- or automount-induced failures), use explicit file system mounts to make the VOB storage available on the VOB server host.
      - Creating VOBs
        Most administrators use storage locations (stglocs) to configure VOB storage on a filer.
      - Fix identity mapping problems
        If your VOB policies and/or rolemaps use identities that do not map correctly over NFSv4 to identities known on the filer, you may encounter errors when changing policies or rolemaps or manipulating elements.
      - Client access to VOB storage pools
        HCL VersionVault clients (view servers, full clients) can use NFSv3, NFSv4, or CIFS to access the VOB storage pools. The filer enforces ACLs for all protocols.
- Administering HCL VersionVault MultiSite
  Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.

NFS version 4 requirement

Because VersionVault with ACLs uses file system ACLs on the container files in a VOB storage pool (source containers and cleartext containers), your network filer must support NFS version 4 with ACLs. VersionVault needs the AUTH_SYS user identity option. It is not supported by other AUTH_* identity systems.

Before you start creating ACL-enabled VersionVault VOBs, ensure that your NFS configuration is working.

Enable NFSv4 and NFSv4 ACLs in the NFS configuration for the network filer.
Configure the same NFS identity mapping domain on the VOB server host and the filer
Grant the VersionVault VOB server host root access to the volume that stores the VOBs (on the volume export).
If there are Windows™ clients, set up a CIFS share for the volume.
Mount the filer's volume on the VOB server host by using NFSv4.
To confirm the correct identity mapping between the VOB and host filers, use the ls command to verify that files created by root are listed as owned by root and that files created by the VOB owner account are owned by the VOB owner.
Optional. On Linux™, install the nfs4-acl-tools package so that you can examine element container ACLs.

Notes:

If you use NFSv4 filer storage for a VOB, performance can be slow for the following VersionVault operations: checkout, checkin, clearfsimport, and other operations that create new containers in VOB storage directories. You can improve the performance of these operations by disabling write delegations in the filer configuration. However, performance improvement is platform-dependent. On some platforms, this change might result in substantial improvement. On other platforms, the improvement is negligible.
All user and group principals included in role maps or policies must be known by name to the VOB server and to the NFSv4 network filer. You cannot use accounts that are not known to the filer. See Fix identity mapping problems.

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.