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

[Timm Stamer]

Hello Prasad,

we use this in our weekly policy run:

RULE 'migrate cold data' MIGRATE FROM POOL 'system' TO POOL 'data'
WHERE CURRENT_TIMESTAMP - ACCESS_TIME > INTERVAL '30' DAYS


I do not know if a direct placement based on timestamps is possible.



Kind regards
Timm Stamer


Am Mittwoch, dem 28.06.2023 um 23:18 +0000 schrieb Prasad Surampudi:
> 
> 
> 
> ACHTUNG! Diese E-Mail kommt von Extern!WARNING! This email originated
> off-campus.
> 
> 
> 
> 
> 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 theatsgroup.com | 302.419.5833 
> 
> Innovative IT consulting & modern infrastructure solutions
> www.theatsgroup.com
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at gpfsug.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7667 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20230629/90f434fa/attachment-0001.bin>