Veritas™ File System 5.0.1 Administrator's Guide

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:

<TO>

</DESTINATION>

</TO>

<WHEN>

</ACCAGE>

</WHEN>

</RELOCATE>

<WHEN>

</ACCAGE>

</WHEN>

</DELETE>

As written with the RELOCATE statement preceding the DELETE statement, files

will never be deleted, because the <WHEN> clause in the RELOCATE statement applies

to all selected files that have not been accessed for at least 30 days. This includes

those that have not been accessed for 90 days. VxFS ceases to process a file against

a placement policy when it identifies a statement that applies to that file, so the

DELETE statement would never occur. This example illustrates the general point

that RELOCATE and DELETE statements that specify less inclusive criteria should

precede statements that specify more inclusive criteria in a file placement policy

document. The GUI automatically produce the correct statement order for the

policies it creates.

Dynamic Storage Tiering

File placement policy rule and statement ordering

178