Removing Shares Without File Migration - Acopia Adaptive Resource Switch Cli Maintenance Manual

Troubleshooting Managed Volumes
Removing an Imported Share

Removing Shares Without File Migration

8-22
bstnA6k# remove-share migrate wwmed /acct it5 fm1 async
WARNING !! Share 'it5' will be removed from volume '/acct' in
namespace 'wwmed' after migrating files to 'fm1'
Proceed? [yes/no] yes
Scheduling report: removeShare.it5.rpt
bstnA6k# ...
You can also remove a share without migrating its files. This may have an impact on
clients; any of the share's files that are visible to them will appear to vanish. This is
typically reserved for share-import failures (described later in the chapter), or
situations where a major change has been announced to the client base. As with the
remove-share migrate
directories.
From priv-exec mode, use the
from a namespace without migrating any of its files:
remove-share nomigrate namespace volume share destination
[async]
where all of the options are described above. The destination is required for the
share's master directories, which must migrate before the share is removed. In
multi-protocol volumes, master directories with NFS-only names cannot migrate
to the destination share; resolve this as discussed above, in
Directories" on page
The CLI prompts for confirmation; enter yes to continue. The back-end share does not
lose any of its files or directories when you use this command. You can access the
share directly when the share-removal completes.
For example, the following command sequence removes the '/rcrds~oldrx' share from
the 'medarcv' namespace. All of the share's master directories migrate to the 'rx'
share:
bstnA6k(gbl)# end
bstnA6k# remove-share nomigrate medarcv /rcrds oldrx rx async
command, this command migrates the share's master
remove-share nomigrate
8-16.
command to remove a share
"Migrating NFS-Only
CLI Maintenance Guide