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.
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
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.

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.

Note that some clients attempt to use NFSv4 for automounted pathnames, if the server supports it. If a client uses NFSv4, then it must be configured correctly for NFS mapping ID domain, and so on. If you do not want your clients to use NFSv4 to the filer, disable NFSv4 on the clients.

For information on identity mapping, see Credentials mapping.

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.