De-Staging A Namespace's Managed Volumes - Acopia Adaptive Resource Switch Cli Maintenance Manual

De-Staging a Namespace's Managed Volumes

While the namespace is de-staged, its managed volumes are inaccessible to clients.
As with
import) in the namespace's managed volumes. That is, no modifications are possible
after the managed volumes are later re-enabled. To prevent this, someone must first run
the
modify
CLI Maintenance Guide
You may want to perform filer recoveries directly on the filer. To directly access the
shares behind a namespace's managed volumes, you first release (or de-stage) the
shares from the volumes. This removes all metadata from all managed volumes and
then disables them. Once the volumes are de-staged, you can access all of their shares
directly (that is, not through a VIP) without any risk of metadata corruption. After you
restore all files to the shares, you can re-enable all of the namespace's managed
volumes.
As with a rebuild, NFS clients must unmount and remount the volumes after the
shares are re-enabled.
From priv-exec mode, use the
namespace's managed volumes.
nsck namespace destage
where:
namespace (1-30 characters) is the name of the namespace to be destaged.
Use the
show namespace
destage specifies to destage the namespace metadata and prepare it for
reimport.
The CLI prompts for confirmation before releasing the shares: enter yes to continue.
Enter no to cancel the destage operation.
, this disables all modifications (client writes and file renames on
nsck ... rebuild
command and raise the
Metadata Utilities: nsck and sync
De-Staging a Namespace's Managed Volumes
command to release all shares from a
nsck destage
command to see a list of configured namespaces.
flag.
reimport-modify
5-39