Filter
Top Products
Chapter 7 HPSS User Interface Configuration
460 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
The file consists of a number of sections, where each section defines a migration or purge policy.
Each section begins with a line that identifies the type of policy being defined (a migration or purge
policy) and gives it a name. Comments can appear in the file, starting with a ‘#’ character and
continuing to the end of the line. Following is an example policy file that will be used in the rest of
the discussion:
##################################################################
# policy.dat: sample migration and purge policy definition file
# Migration policies
MigratePolicy wait
MigrationDelayTime 0
LastAccessTimeBeforeMigration 3000
MigratePolicy run
MigrationDelayTime 86400
LastAccessTimeBeforeMigration 3000
# Purge policies
PurgePolicy wait
PurgeDelayTime 0
LastAccessTimeBeforePurge 4000
UpperBound 80
LowerBound 60
PurgePolicy run
PurgeDelayTime 300
LastAccessTimeBeforePurge 4000
UpperBound 80
LowerBound 60
##################################################################
A migration policy is specified by a line that begins with MigratePolicy, and a purge policy is
specified by a line that begins with PurgePolicy. The keyword is followed by the name of the policy
being defined,such as, wait and run, in the example. The choice of policy names has no significance
to HDM. If desired, the same name could be used to describe a migrate and a purge policy; HDM
does not assume these policies are related. The configuration parameters that define a policy
immediately follow the line that names the policy. The parameters can be in any order, as long as
they are all provided. Each parameter line contains a keyword, preceded by a TAB character.
After the MigratePolicy line, there must be two lines defining the following parameters:
LastAccessTimeBeforeMigration specifies the number of seconds that must elapse after a file is
accessed before the file becomes eligible for migration.
MigrationDelayTime specifies the time, in seconds, that the migration process waits between
passes in which it looks for files to migrate. If the time is set to zero, HDM waits an infinite amount
of time, meaning the migration process waits for a signal before looking for files to migrate.
hdm_admin can be used to send the signal.
After the PurgePolicy line, there must be four lines defining the following parameters: