I believe that is correct. If not, let us know! To recap... when running mmapplypolicy with rules like:
... MIGRATE ... REPLICATE(x) ... will change the replication factor to x, for each file selected by this rule and chosen for execution. ... MIGRATE ... /* no REPLICATE keyword */ will not mess with the replication factor From: "Buterbaugh, Kevin L" <[email protected]> To: gpfsug main discussion list <[email protected]> Date: 06/23/2017 12:07 PM Subject: [gpfsug-discuss] Replication settings when running mmapplypolicy Sent by: [email protected] Hi All, I haven’t been able to find this explicitly documented, so I’m just wanting to confirm that the behavior that I’m expecting is what GPFS is going to do in this scenario… I have a filesystem with data replication set to two. I’m creating a capacity type pool for it right now which will be used to migrate old files to. I only want to use replication of one on the capacity pool. My policy file has two rules, one to move files with an atime > 30 days to the capacity pool, to which I’ve included “REPLICATE(1)”. The other rule is to move files from the capacity pool back to the system pool if the atime < 14 days. Since data replication is set to two, I am thinking that I do not need to explicitly have a “REPLICATE(2)” as part of that rule … is that correct? I.e., I’m wanting to make sure that a file moved to the capacity pool which therefore has its’ replication set to one doesn’t keep that same setting even if moved back out of the capacity pool. Thanks… Kevin — Kevin Buterbaugh - Senior System Administrator Vanderbilt University - Advanced Computing Center for Research and Education [email protected] - (615)875-9633 _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
