Migrating Filesets
Changing Rule Order
CLI Storage-Management Guide 14-23
Removing the Placement Rule
You can remove a placement rule to both disable it and delete its configuration. Many
file-placement rules can manipulate directory mastership so that directory trees grow
naturally on desired filers. If all directory masters are placed correctly, the managed
volume creates new files and directories under them by default; the file-placement
rule is no-longer needed.
Use the no form of the
place-rule command to remove a placement rule:
no place-rule name
where name (1-64 characters) identifies the rule to be removed.
For example, the following command sequence removes the placement rule,
“placeOnSAN19,” from the “medarcv~/rcrds” volume:
bstnA6k(gbl)# namespace medarcv
bstnA6k(gbl-ns[medarcv])# volume /rcrds
bstnA6k(gbl-ns-vol[medarcv~/rcrds])# no place-rule placeOnSAN19
bstnA6k(gbl-ns-vol[medarcv~/rcrds])# ...
If the rule matches files and/or directories based on their names and/or ages instead of
their paths, you may want to keep the rule indefinitely. The file-placement rule can
continue to match against newly-created files/directories, steering them as needed. It
can also re-assess existing files/directories as they age, or as clients change them, and
migrate them as needed.
Changing Rule Order
The policy software enforces its rules in order. Whenever two rules conflict, the
higher-order rule is enforced and the lower-order rule is not. Conflicts arise for files
and/or directories that match two different rules; each rule may attempt to place the
file or directory on a different target. By default, rules are ordered on a
first-come-first-served basis; the first rule you enter is of the highest order, and the
last rule is the lowest order.
Kommentare zu diesen Handbüchern