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

</RULE>
</PLACEMENT_POLICY>
In this placement policy, new files are created on the SSD tiers if space is available,
or elsewhere if space is not available. When enforce is performed, the files that
are currently in SSDs whose write activity is increased above a threshold or whose
read activity fell below a threshold over a given period are moved out of the SSDs.
The first two RELOCATEs capture this intent. However, the files whose read
activity intensified above a threshold and whose write activity does not exceed a
threshold over the given period are moved into SSDs, while giving preference to
files with higher read activity.
The following figure illustrates the behavior of the example placement policy:
The files whose I/O activity falls in the light gray area are good candidates for
moving in to SSD storage. These files have less write activity such that they have
less impact on wear leveling, and the slower write times to SSDs is less of a factor.
These files have intense read activity, which also makes the files ideal for
placement on SSDs since read activity does not cause any wear leveling side effects,
and reads are faster from SSDs. In contrast, the files whose I/O activity falls in
the dark gray area are good candidates to be moved out of SSD storage, since they
have more write activity or less read activity. Greater write activity leads to greater
wear leveling of the SSDs, and your file system's performance suffers from the
385Administering SmartTier
Using SmartTier with solid state disks