Overview

Through <product name> files represent Virtual Volumes on a standard Linux file system. Define the file systems as one or more mount points. The collection of mount points that hold the Virtual Volumes is called the Vault.

Virtual volumes are directed to a mount point by volume serial range. You can use one or more mount points by assigning volume ranges to those mount points. CA Vtape can assign virtual volume serial ranges through its dataset and data class policy-based filters. This lets you decide what z/OS applications and workloads get which cloud storage.

CA Cloud Storage for System z uses the following directory structure to store its Virtual Volumes:

/var/lib/cacloud/vault_01
This is the vault or main directory where all Virtual Volumes are stored.
/var/lib/cacloud/vault_01/mp_01
/mp_02

/mp_03

Under /vault_01 are the mount point directories. Each of these can be mapped to local disk drives, a gateway, or an NFS appliance.

Note: The /etc/FSTAB file contains the file systems mounted during boot. Update this file with the settings recommended by your appliance for your mount points.
/var/lib/cacloud/vault_01/mp_01/vv_100 <- VOLSERs 100000-100999
/vv_101 <- VOLSERs 101000-101999

/mp_02/vv_102 <- VOLSERs 102000-102999

/mp_03/vv_103 <- VOLSERs 103000-103999

Virtual VOLSERs in sets of 1000 must be defined as directories under a mount point.
Soft links, like MVS catalog aliases, map the location of each VOLSER range. The mapped range allows the CA Cloud Storage for System z Server to locate any volume within the vault.
/var/lib/cacloud/vault_01/vv_100 -> mp_01/vv_100

/vv_101 -> mp_01/vv_101

/vv_102 -> mp_02/vv_102

/vv_103 -> mp_03/vv_103