Veritas File System 4.1 Administrator's Guide (HP-UX 11i v3, February 2007)

Quality of Storage Service
Customizing QoSS
Chapter 10 141
You can use the fsapadm utility to create a special allocation policy named fsmove_SITE. The fssweep
and fsmove utilities never create an allocation policy named fsmove_SITE. If this allocation policy exists
and was established as the file system’s default allocation policy, fssweep considers any file in this
allocation policy as residing in any of the volumes that belong to the policy. For example, if you create
fsmove_SITE to specify devices whose index numbers are 4 and 6, and if a relocation policy looks for
source volume indexes of 2 and 4, files can be searched. The index 4 is common to both the relocation policy
and the allocation policy. The purpose of the fsmove_SITE allocation policy is to allow allocating newly
created files differently from way the fsmove_ALL allocation policy is defined, and still allow the files to
be recognizable by the fssweep utility.
Relocation List Format
The relocation list is standard output from the fssweep utility that may be piped to the fsmove utility as
standard input. The list consists of multiple lines of text, each of which describes one file to be moved and its
destination component volume. The following is the format of the text fields:
safe_filename destination_volumes
The safe_filename is ordinary text if the file name does not embed special characters or if it is provided on
the fsmove command line. If special characters are included in the file name that fssweep provides to
fsmove, the exclamation mark (!) escape character delimits the special character. The exclamation marks are
followed and preceded by the two hexadecimal digits providing the internal value of the special character.
This conversion allows fsmove to read special characters from fssweep correctly.
The fssweep utility provides the destination_volumes for the file to be relocated based on the policy
manager’s configuration policy. If there is more than one destination component volume, fsmove tries to
relocate a file to each component volume, in the order specified, until the file is successfully written to one
of the volumes.