Installation manual

Policy for Balancing Capacity
Adding a Share Farm
12-26 CLI Storage-Management Guide
Stopping All Share-Farm Rules
You can stop all auto migrations and/or new-file balancing on a share farm by
disabling it. This reverts all shares to standard behavior; no auto migrations as free
space gets low on a share, and any new file or directory is created on the same share
as its parent. To do this, use the
no enable command from gbl-ns-vol-sfarm mode.
no enable
For example, the following command sequence stops all rules in the ‘fm2’ share farm:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# share-farm tst
bstnA6k(gbl-ns-vol-sfarm[wwmed~/acct~tst])# no enable
bstnA6k(gbl-ns-vol-sfarm[wwmed~/acct~tst])# ...
Removing a Share Farm
You cannot remove a share farm if any rules use it as a source or target. (Later
sections and chapters explain how to configure rules that use share farms in this way.)
Remove all such rules before removing the share farm; use
show policy to find them,
as instructed in “Showing All Policy Rules” on page 12-2.
From gbl-ns-vol mode, use the
no share-farm command to remove a share farm:
no share-farm name
where name (1-64 characters) identifies the share farm to be removed.
This does not affect client access to the farm’s shares.
For example, the following command sequence removes the “san14luns4-8” share
farm from the “/acct” volume:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# no share-farm san14luns4-8
bstnA6k(gbl-ns-vol[wwmed~/acct])# ...