Migrate and recall with external pools

After you define an external storage pool, subsequent migration or deletion rules might refer to that pool as a source or target storage pool.

When you invoke mmapplypolicy and a rule dictates that data should be deleted or moved to or from an external pool, the program identified in the EXTERNAL POOL rule is invoked with the following arguments:
  • The command to be executed.
  • The name of the file containing a list of files to be migrated, pre-migrated, or purged.
  • Optional parameters, if any.
For example, let us assume an external pool definition:
RULE EXTERNAL POOL 'externalpoolA'
   EXEC '/usr/hsm/bin/hsmControl' OPTS '-server=hsm-manager.nyc.com'
To move files from the internal system pool to storage pool "externalpoolA" you would simply define a migration rule that may look something like this:
RULE 'MigToExt' MIGRATE FROM POOL('system') TO POOL('externalpoolA') WHERE ...
This would result in the external pool script being invoked as follows: 
/usr/hsm/bin/hsmControl MIGRATE /tmp/filelist -server=hsm-manager.nyc.com
Similarly, a rule to migrate data from an external pool back to an internal storage pool could look like: 
RULE 'MigFromExt' MIGRATE FROM POOL 'externalpoolA' TO POOL 'system' WHERE ...
This would result in the external pool script being invoked as follows:
/usr/hsm/bin/hsmControl RECALL /tmp/filelist -server=hsm-manager.nyc.com
Notes:
  1. When migrating to an external storage pool, GPFS ignores the LIMIT and REPLICATION clauses in the policy rule.
  2. If you are using IBM Spectrum Protect with external storage pools, you may need to create specific rules to avoid system problems. These rules should exclude IBM Spectrum Protect-related system files from both migration and deletion. These rules use the form: 
    RULE 'exclude hsm system files' EXCLUDE WHERE PATH_NAME LIKE '%/.SpaceMan%'