Migrating Filesets
Directing File Placement
CLI Storage-Management Guide 14-17
Whether or not you use a schedule, the rule places all new files as clients create them.
By default, the rule also watches all client changes inline, and migrates any file that
changes to match the source fileset. A schedule has no effect on new or
newly-changed files.
“Creating a Schedule” on page 12-27 has full details on creating a schedule. To apply
a schedule to the placement rule, use the
schedule command in gbl-ns-vol-plc mode:
schedule name
where name (1-64 characters) identifies the schedule. Use the
show policy
schedule
command to list all schedules.
For example, the following command sequence applies an hourly schedule to 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])# schedule hourly
bstnA6k(gbl-ns-vol-plc[archives~/home~mvTars])# ...
Removing the Schedule
Use no schedule to use only a single, initial volume scan and migrate all files and/or
directories found in that scan. This makes the placement rule migrate all existing files
and/or directories in a single session:
no schedule
Again, a schedule (or lack of schedule) has no effect on new files, or files that clients
change to match the fileset.
For example:
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])# no schedule
bstnA6k(gbl-ns-vol-plc[wwmed~/acct~docs2das8])# ...
Kommentare zu diesen Handbüchern