HSM managed file system used space is about 6%, GPFS policy is up and running with an HIGH threshold at 4%, but nothing happened...
I tested callback functionality using "leaveNode" event with success!!! Someone could explain me why only LowDiskSpace event doesn't run!??! :-(

Re: GPFS lowDiskSpace event handling doesn't start.

‏2013-02-10T16:39:21Z

This is the accepted answer.
This is the accepted answer.

You LowSpaceCallback is restricting to a set of 4 nodes. But the lowDiskSpace only triggered on the file system manager node. If the current fsmgr is not one of these 4 nodes, you will not see the lowDiskSpace event. Either change the fsmgr to one of the nodes in your set or reconfigure the callback without the -N option (default to all nodes in the cluster).

I believe policy ruleName can be anything. It "identifies the rule and is used in diagnostic messages." Please see the Advanced Admin Guide.

Re: GPFS lowDiskSpace event handling doesn't start.

You LowSpaceCallback is restricting to a set of 4 nodes. But the lowDiskSpace only triggered on the file system manager node. If the current fsmgr is not one of these 4 nodes, you will not see the lowDiskSpace event. Either change the fsmgr to one of the nodes in your set or reconfigure the callback without the -N option (default to all nodes in the cluster).

I believe policy ruleName can be anything. It "identifies the rule and is used in diagnostic messages." Please see the Advanced Admin Guide.

For the first time, lowDiskSpace event has been triggered on file system manager node and lowspace test script has been launched.
But, if it is possible, I would ask you something else ( just a few questions...if you can help me again :-) )

First of all, I would inform you about our cluster configuration:

n. 482 compute nodes

n. 2 login nodes

n. 8 I/O nodes for GPFS file systems

n. 4 TSM/HSM client nodes

At the moment, all 8 I/O nodes are GPFS quorum-manager or manager node ( 1 of them is fs manager for HSM managed file system: io5-ib node )

Questions:

lowDiskspace starts only on io5-ib node, lowspace script executes mmapplypolicy command on io5-ib, but io5-ib node is not a TSM/HSM one :-( I think that I can launch mmapplypolicy (on io5-ib node) specifying -N option (for example: mmapplypolicy... -N tsm1-ib, tsm2-ib and so on). But what happens if, due to some maintenance purposes, we need to restart io5-ib node after it launches mmapplypolicy? HSM Migration started on tsm nodes will be interrupted or not?

I would reconfigure callback on I/O nodes only (io1-ib, io2-ib and so on...), but what happens if all I/O nodes launch a lot of mmapplypolicy? Is there a IBM "certified" script that prevents this issue?

Re: GPFS lowDiskSpace event handling doesn't start.

For the first time, lowDiskSpace event has been triggered on file system manager node and lowspace test script has been launched.
But, if it is possible, I would ask you something else ( just a few questions...if you can help me again :-) )

First of all, I would inform you about our cluster configuration:

n. 482 compute nodes

n. 2 login nodes

n. 8 I/O nodes for GPFS file systems

n. 4 TSM/HSM client nodes

At the moment, all 8 I/O nodes are GPFS quorum-manager or manager node ( 1 of them is fs manager for HSM managed file system: io5-ib node )

Questions:

lowDiskspace starts only on io5-ib node, lowspace script executes mmapplypolicy command on io5-ib, but io5-ib node is not a TSM/HSM one :-( I think that I can launch mmapplypolicy (on io5-ib node) specifying -N option (for example: mmapplypolicy... -N tsm1-ib, tsm2-ib and so on). But what happens if, due to some maintenance purposes, we need to restart io5-ib node after it launches mmapplypolicy? HSM Migration started on tsm nodes will be interrupted or not?

I would reconfigure callback on I/O nodes only (io1-ib, io2-ib and so on...), but what happens if all I/O nodes launch a lot of mmapplypolicy? Is there a IBM "certified" script that prevents this issue?

If mmapplypolicy needs to be run on an HSM server, you can script your callback to executes it remotely on HSM server via ssh/rsh. The command mmapplypolicy has --single-instance option to ensure only one mmapplypolicy process running per file system at a time.

From the expert, you need to modify the RULE since exclude should always proceed migration rule...

If mmapplypolicy needs to be run on an HSM server, you can script your callback to executes it remotely on HSM server via ssh/rsh. The command mmapplypolicy has --single-instance option to ensure only one mmapplypolicy process running per file system at a time.

From the expert, you need to modify the RULE since exclude should always proceed migration rule...

Re: GPFS lowDiskSpace event handling doesn't start.

If mmapplypolicy needs to be run on an HSM server, you can script your callback to executes it remotely on HSM server via ssh/rsh. The command mmapplypolicy has --single-instance option to ensure only one mmapplypolicy process running per file system at a time.

From the expert, you need to modify the RULE since exclude should always proceed migration rule...

One way is to use the list provided by policy due to lowspace event and use that list in exec script for both dsmc selective and dsmmigratefs.
This will require you changing/creating custom exec script.

Most customers will backup system on regular basis thus, migration should not need the backup. Also their migration rule will specify that older files are migration candidate thus allowing backup to be done before migration on all cases.
Also keep in mind if migration and backup are being done to same TSM server then doing backup will not cause recall of the migrated file. TSM server will do inline copy.

Re: GPFS lowDiskSpace event handling doesn't start.

One way is to use the list provided by policy due to lowspace event and use that list in exec script for both dsmc selective and dsmmigratefs.
This will require you changing/creating custom exec script.

Most customers will backup system on regular basis thus, migration should not need the backup. Also their migration rule will specify that older files are migration candidate thus allowing backup to be done before migration on all cases.
Also keep in mind if migration and backup are being done to same TSM server then doing backup will not cause recall of the migrated file. TSM server will do inline copy.

Thanks Truongv,
I need to backup all files that will be migrated for a lot of "security" reasons.
I know I can backup already migrated data using inline copy, but I prefer start a backup before any "moving" operations.

So, I have to modify my "custom exec script"...that is "/var/mmfs/etc/mmpolicyExec-hsm" file, doesn't it!?
You are not refer to callbackup.hsmspace.ksh script, I think...

Re: GPFS lowDiskSpace event handling doesn't start.

Thanks Truongv,
I need to backup all files that will be migrated for a lot of "security" reasons.
I know I can backup already migrated data using inline copy, but I prefer start a backup before any "moving" operations.

So, I have to modify my "custom exec script"...that is "/var/mmfs/etc/mmpolicyExec-hsm" file, doesn't it!?
You are not refer to callbackup.hsmspace.ksh script, I think...