Veritas™ File System 5.0.1 Administrator's Guide

for which each document is the current active policy. When a policy document is
updated, SFMS can assign the updated document to all file systems whose current
active policies are based on that document. By default, SFMS does not update file
system active policies that have been created or modified locally, that is by the
hosts that control the placement policies' file systems. If a SFMS administrator
forces assignment of a placement policy to a file system, the file system's active
placement policy is overwritten and any local changes that had been made to the
placement policy are lost.
Assigning a placement policy
The following example uses the fsppadm assign command to assign the file
placement policy represented in the XML policy document /tmp/policy1.xml for
the file system at mount point /mnt1.
To assign a placement policy
◆
Assign a placement policy to a file system:
# fsppadm assign /mnt1 /tmp/policy1.xml
Unassigning a placement policy
The following example uses the fsppadm unassign command to unassign the
active file placement policy from the file system at mount point /mnt1.
To unassign a placement policy
◆
Unassign the placement policy from a file system:
# fsppadm unassign /mnt1
Analyzing the space impact of enforcing a placement policy
The following example uses the fsppadm analyze command to analyze the impact
if the enforce operation is performed on the file placement policy represented in
the XML policy document /tmp/policy1.xml for the mount point /mnt1. The
command builds the I/O temperature database if necessary.
To analyze the space impact of enforcing a placement policy
◆
Analyze the impact of enforcing the file placement policy represented in the
XML policy document /tmp/policy1.xml for the mount point /mnt1:
# fsppadm analyze -F /tmp/policy1.xml -i /mnt1
147Dynamic Storage Tiering
Administering placement policies