CA Vtape can use HFS, zFS or NFS file systems for its general usage. Before you run USS Backstore, your USS administrator must set up a directory path and optionally configure a file system.
Note: We recommend using zFS file system for the initial path.
During operation, CA Vtape dynamically mounts additional file systems. File systems are mounted during startup, and as required in response to SVTS operator refresh commands.
The following example shows the structure of the paths:
/u/users/vtape
signature
triplex
group01
group02
group03
group04
… (groups 11-14, 21-24, 31-34, 41-44, 51-54 and 61-64)
group71
group72
group73
group74
Is the primary mount point or directory and is required to exist before starting CA Vtape with USS Backstore enabled. This directory name may be customized by changing the RootDirectory attribute in the <StartupOptions> section of parmlib. This name does not need to match between SVTS subsystems in the same CA Vtape Complex.
Signature is an unique hexadecimal value assigned to the CA Vtape Complex. This signature directory name is used to guard against multiple CA Vtape Complexes accidentally accessing incorrect files.
Note: The signature value assigned to the CA Vtape Complex can be displayed by the SVTn Display Status console command.
Is a required directory and mount point that is dynamically created and mounted by CA Vtape during startup and parmlib refresh if the file system must be changed. This directory and mount point typically refers to a NFS file system under which the USS Backstore copies will be stored in sub-directories.
Are dynamically created directories used to hold the USS Backstore copies. To accommodate spreading data across multiple NFS servers, each group directory can optionally be customized as an individual mount point.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|