[gpfsug-discuss] File placement policy based on creation and modification times

[Prasad Surampudi]

Can we setup a file placement policy based on creating and modification times when copying data from Windows into GPFS? It looks like the placement policy only accepts only CREATION_TIME and not MODIFICATION_TIME or ACCESS_TIME.  If I try to use these, I get message saying these are not supported in the context (placement?) But even the policy with CREATION_TIME is not working properly. We wanted files with CREATION_TIME which is 365 days ago go to a different pool other than ‘system’. But when we copy files it is dumping all files into system pool. But the creation time is looks correct on the file after copied into GPFS. Does it check file CREATION_TIME when a file gets copied over to GPFS?

Here is the placement policy:
RULE ‘tiering’ SET POOL ‘pool2’
WHERE ( DAYS(CURRENT_TIMESTAMP) - DAYS(CREATION_TIME) > 365 )
RULE ‘default’ SET POOL ‘system’

[Logo  Description automatically generated]

Prasad Surampudi | Sr. Systems Engineer
prasad.surampudi at theatsgr<mailto:prasad.surampudi at theatsgroup.com>oup.com<mailto:prasad.surampudi at theatsgroup.com> | 302.419.5833

Innovative IT consulting & modern infrastructure solutions
www.theatsgroup.com<http://theatsgroup.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20230628/5ed21a16/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6597 bytes
Desc: image001.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20230628/5ed21a16/attachment.png>