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

</SELECT>
<CREATE>
<ON>
<DESTINATION>
<CLASS>tier1</CLASS>
</DESTINATION>
</ON>
</CREATE>
other_statements
</RULE>
</FILE_PLACEMENT_POLICY>
The GeneralRule rule specifies that all files created in the file system, designated
by <PATTERN>*</PATTERN>, should be created on tier2 volumes. The DatabaseRule
rule specifies that files whose names include an extension of .db should be created
on tier1 volumes. The GeneralRule rule applies to any file created in the file
system, including those with a naming pattern of *.db, so the DatabaseRule rule
will never apply to any file. This fault can be remedied by exchanging the order
of the two rules. If the DatabaseRule rule occurs first in the policy document,
VxFS encounters it first when determining where to new place files whose names
follow the pattern *.db, and correctly allocates space for them on tier1 volumes.
For files to which the DatabaseRule rule does not apply, VxFS continues scanning
the policy and allocates space according to the specification in the CREATE
statement of the GeneralRule rule.
A similar consideration applies to statements within a placement policy rule. VxFS
processes these statements in order, and stops processing on behalf of a file when
it encounters a statement that pertains to the file. This can result in unintended
behavior.
The following XML snippet illustrates a RELOCATE statement and a DELETE
statement in a rule that is intended to relocate if the files have not been accessed
in 30 days, and delete the files if they have not been accessed in 90 days:
<RELOCATE>
<TO>
<DESTINATION>
<CLASS>tier2</CLASS>
</DESTINATION>
</TO>
<WHEN>
<ACCAGE Units="days">
<MIN Flags="gt">30</MIN>
</ACCAGE>
377Administering SmartTier
File placement policy rule and statement ordering