Installation manual

Policy for Balancing Capacity
Draining One or More Shares
CLI Storage-Management Guide 12-39
bstnA6k(gbl-ns-vol-plc[wwmed~/acct~emptyRH])# no schedule
bstnA6k(gbl-ns-vol-plc[wwmed~/acct~emptyRH])# ...
Limiting Each Migration (optional)
You can use the limit-migrate command to put a ceiling on the amount of data
migrated. The policy engine migrates files until it meets this limit; it stops migrating
as soon as it discovers that the next file would exceed the limit.
limit-migrate size[k|M|G|T]
where
size (1-18,446,744,073,709,551,615) is the size, and
k|M|G|T (optional) is the units; kilobytes (1024 bytes), Megabytes
(1024*1024 bytes), Gigabytes (1024*1024*1024), or Terabytes
(1024*1024*1024*1024). The default is bytes.
This limit applies to every run of the placement rule, so you can use it in conjunction
with a schedule to migrate a limited amount of data during off-hours. For example,
you can allow a limit of 20 Gigabytes and a daily schedule that runs at midnight. If the
source share contains 100 Gigabytes of data, it would migrate over five nights, 20G
per night.
For a placement rule without a schedule, this limit applies to the one-and-only run of
the rule. If the share exceeds this limit, the left-over files remain on the source share
indefinitely. New files are always created at the target share(s), so they are not
blocked by this limit.
For example, the following command sequence sets a 10G limit on the “move2nas”
rule, which only runs on Friday afternoons:
bstnA6k(gbl)# namespace archives
bstnA6k(gbl-ns[archives])# volume /etc
bstnA6k(gbl-ns-vol[archives~/etc])# place-rule move2nas
bstnA6k(gbl-ns-vol-plc[archives~/etc~move2nas])# schedule fri5pm
bstnA6k(gbl-ns-vol-plc[archives~/etc~move2nas])# limit-migrate 10G
bstnA6k(gbl-ns-vol-plc[archives~/etc~move2nas])# ...