unaccessed (for read or write) for the length of time specified by this field.
Start purge when space used exceeds. Purge will begin for a storage class when the amount of it s space
used exceeds this threshold. Used space includes any file in the storage class, whether it has been
migrated or not.
Stop purge when space used falls to. Purging will stop for a storage class when the amount of its space
used drops to this threshold. Note that the purge may stop before this point if it runs out of files which
are available for purging.
Purge Locks expire after. Maximum number of minutes that a file may hold a purge lock. Purge locked
files are not eligible for purging. A value of 0 indicates that purge locks expire immediately.
Files may be purge locked to the highest level (level zero) of a hierarchy, provided that level zero is of
type disk, and data exists at level zero. Once a file is purge locked, it is no longer a purge candidat e. By
entering a "lock expiration duration," you will be able to monitor the number of purge locked fil es and
the number of expired purge locked files using the Migration Purge Server (MPS) log. After a purge run,
the MPS will log the total number of purge locked files and the number of expired purge locks (those
files that have been locked longer than this specified number of minutes). To view the names of the files
with expired purge locks, use the Purge List Utility (plu) with the -lexp parameter on a given class of
service.
Purge by. The MPS uses this time attribute of a file to determine which fil es are eligible to be purged.
By default, files are selected for purge based on the time the purge record was created, the Migration
Completion Time. Alternately, the selection of files for purging may be based on the time the file was
created, the File Creation Time, or the time the file was last accessed, the Last Access Time.
If this field is changed, all Core Servers and Migration Purge Servers must be restarted in order
for the change to take effect. Additionally, files will be purged in an unpredictable order until all
purge records existing at the time of the change are cleared.
Storage Subsystem (subsystem policy tab only). The descriptive name of the storage subsystem to which
a subsystem-specific policy applies. This field is filled in with the selected storage subsystem name at the
time a subsystem specific policy is created and may not be changed afterwards.
Related Informatio n
Section 4.2.3.7: Migration and Purge Policy Overrides on page 81
6.5.3. Changing a Purge Pol icy
To update an existing basic purge policy, select the policy from the Purge Policies window and click the
Configure button. After modifying the basic policy, click on the Update button to save the changes. To
update an existing subsystem specific purge policy, first select and display the existi ng basic policy and
then select the tab for the desired subsystem policy. After modifying the subsystem specific polic y, click
on the Update button to save the changes.
Before changes made to a purge policy take effect, the Migration Purge Servers must be either restarted
or instructed to reread the policy.1 If the Migration Purge Servers are restarted, t he changes to the purge
1 Use the Controls selection list on the MPS Storage Class Information screen or the Migration Controls selection
list on the Active Storage Class list screen to reread policies.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 192