The migration rule is only for modifying files without changing their filename or which directory they are in, so changing things like:
compressionreplication (eg 1way to 2way)physical storage eg flash to diskstubbing a file to move content to external storage such
You would want to look for examples of external scripts that work on the result
of running the policy engine in listing mode. The one issue that might need
some attention is the way that gpfs quotes unprintable characters in the
pathname. So the policy engine generates the list and your
The MIGRATE rule is for moving files from one pool to another, without
changing the pathname or any attributes, except the storage devices holding
the data blocks of the file. Also can be use for "external" pools to
migrate to an HSM system.
"moving" from one folder to another is a different
Hi
Thanks for your reply, once I have a set of files that are older than 30 days
would I then use the migration rule to move them ?
Looking at the migration Rule syntax implies a “From” pool and a “To” pool, I
only have a single pool so would I use the same pool name for From and To ? if
it
Hi
U can create list of diretories in output file which were not modify in
the last 30 days, and than second script will move this directories to the
new location that u want.
Regards
Yaron Daniel
94 Em Ha'Moshavot Rd
Storage Architect – IL Lab Services (Storage)
Petach Tiqva,
Hi
I work for Cancer Research UK MI in Manchester UK. I am new to GPFS and have
been tasked with creating a policy that will
Move files older that 30 days to a new folder within the same pool. There are a
lot of files so using a policy based move will be faster.
I have read about the migration
