Veritas™ File System 5.0.1 Programmer's Reference Guide

■ Per-file-system policies
The most specific allocation policy in effect for a given allocation operation is
used.
The MVS APIs fall into the following basic categories:
■ Manipulation of volumes within a file system
■ Manipulation of allocation policy definitions
■ Application of allocation policies
Each of the APIs is also available via options to the fsvoladm(1M) and fsapadm(1M)
commands.
See the fsvoladm(1M) and fsapadm(1M) manual pages.
Uses for multi-volume support
Possible uses for the multi-volume support feature include the following:
■ Controlling where files are stored so that specific files or file hierarchies can
be assigned to different volumes
■ Separating Storage Checkpoints so that data allocated to a Storage Checkpoint
is isolated from the rest of the file system
■ Separating file system metadata from file data
■ Encapsulating volumes so that a volume appears in the file system as a file;
this is particularly useful for databases that are running on raw volumes
■ Migrating files off a volume so that the volume can be replaced or serviced
■ Implementing a storage optimization application that periodically scans the
file system and modifies the allocation policies in response to changing patterns
of storage use
Volume application programming interfaces
The volume APIs can be used to add volumes to a file system, remove volumes
from a file system, list which volumes are in a file system, and retrieve information
on usage and availability of space in a volume.
Multi-volume file systems can only be used with VxVM volume sets. Volume sets
are administered via the vxvset command.
See the Veritas Volume Manager Administrator’s Guide.
Multi-volume support
Uses for multi-volume support
52