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

The following example statement causes the average file system activity be
collected and computed over a period of 30 hours instead of the default 24 hours:
<PLACEMENT_POLICY Name="Policy1" Version="5.1" AveragePeriod="30">
RELOCATE statement examples
The following example illustrates an unconditional relocation statement, which
is the simplest form of the RELOCATE policy rule statement:
<RELOCATE>
<FROM>
<SOURCE>
<CLASS>tier1</CLASS>
</SOURCE>
</FROM>
<TO>
<DESTINATION>
<CLASS>tier2</CLASS>
</DESTINATION>
</TO>
</RELOCATE>
The files designated by the rule's SELECT statement that reside on volumes in
placement class tier1 at the time the fsppadm enforce command executes would
be unconditionally relocated to volumes in placement class tier2 as long as space
permitted. This type of rule might be used, for example, with applications that
create and access new files but seldom access existing files once they have been
processed. A CREATE statement would specify creation on tier1 volumes, which
are presumably high performance or high availability, or both. Each instantiation
of fsppadm enforce would relocate files created since the last run to tier2
volumes.
The following example illustrates a more comprehensive form of the RELOCATE
statement that uses access age as the criterion for relocating files from tier1
volumes to tier2 volumes. This rule is designed to maintain free space on tier1
volumes by relocating inactive files to tier2 volumes:
<RELOCATE>
<FROM>
<SOURCE>
<CLASS>tier1</CLASS>
</SOURCE>
</FROM>
<TO>
363Administering SmartTier
File placement policy rules