Migrating Metadata To A New Back-End Share - Acopia Adaptive Resource Switch Cli Maintenance Manual

Migrating Metadata to a New Back-End Share

This stops all client access to the volume during the metadata migration. Whether or not
the migration succeeds, client access resumes as soon as the operation ends.
CLI Maintenance Guide
Managed volumes require fast and extremely-reliable back-end shares to store their
metadata. A slow metadata share can affect client service as well as import speed. To
migrate a volume's metadata from a slow back-end share to one on a faster filer, use
the
nsck migrate-metadata
nsck namespace migrate-metadata volume vol-path target ext-filer
{nfs3 | nfs3tcp | cifs} path
where:
namespace (1-30 characters) identifies the namespace.
vol-path (1-1024 characters) is the managed volume that requires new
metadata storage. Use forward slashes (/) in the path, even for CIFS
volumes.
ext-filer (1-64 characters) identifies the target share for the volume's
metadata. This is the external-filer name for the filer; use
for a complete list of configured filers.
nfs3 | nfs3tcp | cifs is a required choice. This is the protocol used to access
the metadata share; it can be different from any of the protocols used for the
managed volume. The choices are NFSv3 over UDP (nfs3), NFSv3 over
TCP (nfs3tcp), or CIFS.
path (1-1024 characters) selects the metadata share and path (for example,
'/' or '/usr/acoMD'). For a CIFS share, this is the share name (and possibly a
path to a subshare); use forward slashes (/), even for CIFS shares.
Metadata Utilities: nsck and sync
Migrating Metadata to a New Back-End Share
command:
show external-filer
5-43