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

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.

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.

Following are sample commands for mounting a filer's NFSv4 export and checking that you can view NFSv4 ACLs. If you get an error viewing ACLs, verify the mount options and the filer configuration before proceeding with the VOBs.

After you validate that the NFSv4 mount is correct, add a permanent mount-point entry to the file system table to be mounted when the system boots.

Linux™

SUSE Linux™ Enterprise: you must be running SLES 11 or higher to use ACLs-enabled VOBs stored on a filer.

Red Hat Enterprise Linux™: all versions supported by HCL VersionVault also support ACLs-enabled VOBs stored on a filer.

mount -t nfs4 filer:/ /nfs4-filer
ls -ld /nfs4-filer/vol/cc_acl_nfsv4/stg
nfs4_getfacl /nfs4-filer/vol/cc_acl_nfsv4/stg

Solaris 11

mount -o vers=4 filer:/ /nfs4-filer
ls -ld /nfs4-filer/vol/cc_acl_nfsv4/stg
ls -Vd /nfs4-filer/vol/cc_acl_nfsv4/stg

Ensure the ls -Vd output includes a "deny" line, which is an indication that NFSv4 ACLs are working. Alternatively, you can use chmod to add an access control entry to a file's ACL and verify that succeeds.

Solaris 10

The Solaris 10 NFS client does not support server volume mount-point crossing. For a Solaris 10 VOB server, you must mount the storage volume explicitly instead of the root. Note that this means the host-local path omits the /vol/volume-name portion of the path, unlike the other UNIX™ variants.

mount -o vers=4 filer:/vol/cc_acl_nfsv4 /nfs4-filer
ls -ld /nfs4-filer/stg
ls -Vd /nfs4-filer/stg

Check the output as described for Solaris 11.

Note: Filer-hosted VOBs hosted on Solaris 10 encounter a substantial performance slowdown when write delegations are enabled on the filer, due to the way HCL VersionVault manages storage containers and the way Solaris 10 handles write delegations. If you use Solaris 10 and filers, you can minimize this slowdown by disabling write delegations on the filer.

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.