VOB automounting configuration: Administrator actions

The steps to configure VOB automounting are listed here.

About this task

The following sections describe each step in more detail. This configuration process must be completed on each client system on which VOBs will be automounted. You do not have to configure automounting on every client system in your environment. The choice can be made independently for each system. If no specific action is taken, the default behavior continues: all public VOBs are mounted at start-up by the HCL VersionVault start script.

Procedure

To configure and enable VOB automounting:
  1. Update the system's master automount configuration file to associate an MVFS automount map with each VOB root that you want to automount.
  2. Set up one or more automount maps for VOBs. One option is to use the provided template auto.mvfs file by copying it to the /etc folder and setting VOB_ROOT_PATH, as appropriate for your environment.
  3. Create a configuration file to direct the VersionVault start script to skip the step of mounting all public VOBs.
  4. Restart the automounter and VersionVault.
    Note: If a VersionVault system is configured without dynamic views (server-only configuration), no VOBs are mounted. Therefore, it does not make sense to configure automounting.