Veritas File System 5.0 AdministratorÆs Guide, HP-UX 11i v3, First Edition, May 2008
Multiple placement classes in <FROM> clauses of RELOCATE and
DELETE statements
The <FROM> clause in RELOCATE and DELETE statements can include multiple source
placement classes. However, unlike the <ON> and <TO> clauses, no order or priority
is implied in <FROM> clauses. If a qualifying file resides on a volume in any of the
placement classes specified in a <FROM> clause, it is relocated or deleted regardless
of the position of its placement class in the <FROM> clause list of classes.
Multiple conditions in <WHEN> clauses of RELOCATE and DELETE
statements
The <WHEN> clause in RELOCATE and DELETE statements may include multiple
relocation criteria. Any or all of <ACCAGE>, <MODAGE>, <SIZE>, and <IOTEMP> can
be specified. When multiple conditions are specified, all must be satisfied in order
for a selected file to qualify for relocation or deletion.
In the following example, a selected file would have to be both inactive, that is,
not accessed, for more than 30 days and larger than 100 megabytes to be eligible
for relocation or deletion:
<WHEN>
<ACCAGE Units="days">
<MIN Flags="gt">30</MIN>
</ACCAGE>
<SIZE Units="MB">
<MIN Flags="gt">100</MIN>
</SIZE>
</WHEN>
You cannot write rules to relocate or delete a single designated set of files if the
files meet one of two or more relocation or deletion criteria.
File placement policy rule and statement ordering
You can use the Dynamic Storage Tiering graphical user interface (GUI) to create
any of four types of file placement policy documents. Alternatively, you can use
a text editor or XML editor to create XML policy documents directly. The GUI
places policy rule statements in the correct order to achieve the desired behavior.
If you use a text editor, it is your responsibility to order policy rules and the
statements in them so that the desired behavior results.
The rules that comprise a placement policy may occur in any order, but during
both file allocation and fsppadm enforce relocation scans, the first rule in which
Dynamic Storage Tiering
File placement policy rule and statement ordering
178