Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

In the following example, a file need only reside in one of db/datafiles,
db/indexes, or db/logs or be owned by one of DBA_Manager, MFG_DBA, or HR_DBA
to be designated for possible action:
<SELECT>
<DIRECTORY Flags="nonrecursive">db/datafiles</DIRECTORY>
<DIRECTORY Flags="nonrecursive">db/indexes</DIRECTORY>
<DIRECTORY Flags="nonrecursive">db/logs</DIRECTORY>
</SELECT>
<SELECT>
<USER>DBA_Manager</USER>
<USER>MFG_DBA</USER>
<USER>HR_DBA</USER>
</SELECT>
Multiple placement classes in <ON> clauses of CREATE statements
and in <TO> clauses of RELOCATE statements
Both the <ON> clause of the CREATE statement and the <TO> clause of the RELOCATE
statement can specify priority ordered lists of placement classes using multiple
<DESTINATION> XML elements. VxFS uses a volume in the first placement class
in a list for the designated purpose of file creation or relocation, if possible. If no
volume in the first listed class has sufficient free space or if the file system's
volume set does not contain any volumes with that placement class, VxFS uses a
volume in the second listed class if possible. If no volume in the second listed class
can be used, a volume in the third listed class is used if possible, and so forth.
The following example illustrates of three placement classes specified in the <ON>
clause of a CREATE statement:
<CREATE>
<ON>
<DESTINATION>
<CLASS>tier1</CLASS>
</DESTINATION>
<DESTINATION>
<CLASS>tier2</CLASS>
</DESTINATION>
<DESTINATION>
<CLASS>tier3</CLASS>
</DESTINATION>
</ON>
</CREATE>
Administering SmartTier
Multiple criteria in file placement policy rule statements
374