Installation manual

Migrating Filesets
Directing File Placement
14-10 CLI Storage-Management Guide
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# place-rule reset
bstnA6k(gbl-ns-vol-plc[wwmed~/acct~reset])# from fileset a_b_tree match directories
promote-directories
bstnA6k(gbl-ns-vol-plc[wwmed~/acct~reset])# ...
Promoting Directories on a Target Share Farm
If the file-placement target is a share farm, the share that gets the directory also gets
the directory promotion. The share farm’s new-file-placement algorithm determines
the exact share where the directory goes. Share-farm rules for new-file placement
were described earlier: recall “Balancing New Files Based on Free Space” on
page 12-19.
Avoid Promoting CIFS Directories Based on Last-Accessed
Time
CIFS filers update a directory’s last-accessed time whenever the policy engine reads
the time stamp. Do not migrate and promote CIFS directories if the source fileset
• is age-based, and
• does all selections based in the last-accessed time (recall “Choosing
Last-Accessed or Last-Modified” on page 13-15).
If a rule migrates and promotes directories based on their last-accessed times in a
CIFS or multi-protocol namespace, the back-end filer changes the directory’s time
stamp after the migration. Any other rule that chooses directories based on the
last-accessed time would therefore use the wrong time stamp. This can cause
unpredictable results.
NFS-only filers do not have this problem, nor is it a problem with files.