Installation manual

Migrating Filesets
Directing File Placement
14-16 CLI Storage-Management Guide
For a placement rule without a schedule, this limit applies to the one-and-only run of
the rule. If the original fileset exceeds this limit, the left-over files from that fileset
remain on their source share(s) indefinitely. New files that belong in the fileset are
created at the target share(s), before they have any size, so they are not blocked by this
limit.
For example, the following command sequence sets a 50G limit on the “docs2das8”
rule:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# place-rule docs2das8
bstnA6k(gbl-ns-vol-plc[wwmed~/acct~docs2das8])# limit-migrate 50g
bstnA6k(gbl-ns-vol-plc[wwmed~/acct~docs2das8])# ...
Removing the Limit
By default, a placement rule migrates until all matching files are removed from the
source share(s). Use the
no limit-migrate command to return to this default:
no limit-migrate
For example, the following command sequence removes any migration limit in the
“mvTars” rule:
bstnA6k(gbl)# namespace archives
bstnA6k(gbl-ns[archives])# volume /home
bstnA6k(gbl-ns-vol[archives~/home])# place-rule mvTars
bstnA6k(gbl-ns-vol-plc[archives~/home~mvTars])# no limit-migrate
bstnA6k(gbl-ns-vol-plc[archives~/home~mvTars])# ...
Applying a Schedule (optional)
You can optionally run the placement rule on a schedule. The schedule determines
when the rule scans the back-end filers behind the volume to find files for migration.
This applies to existing files and/or directories that belong in your fileset; if there are
a large number of files, you can use a schedule so that the migrations occur in stages
and during off-peak hours. By default, the placement rule migrates all existing files on
the first scheduled run; to spread the load out over time, you can use
duration in the
schedule or
limit-migrate in the placement rule.