Installation manual

Configuring a Namespace
Enabling the Namespace (optional)
CLI Storage-Management Guide 7-23
Enabling All Shares in the Namespace
From gbl-ns mode, you can enable all of the namespace’s shares with a single
command. Use the
enable shares command to accomplish this:
enable shares
For example, the following command sequence enables all shares in the “wwmed”
namespace:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# enable shares
bstnA6k(gbl-ns[wwmed])# ...
Taking Ownership of All Managed Shares (optional)
Before a managed volume imports each share, it checks the root directory in the share
for a special file that marks it as “owned” by an ARX. If this marker file exists, the
managed volume does not proceed with the import; no two volumes can manage the
same share. You may need to override this safety mechanism for a special case.
Consider an installation that uses legacy, filer-based applications to prepare for
disaster recovery: it copies all of its directories and files from a primary site to another
site. If an ARX manages the directories at the primary site, it places its ownership
marker in the root of each share. The filer-based application copies the marker files to
the remote site, along with all data files. An ARX at the backup site cannot import
these shares because of the markers.
This does not apply to any direct volumes in the namespace.
You can use the optional
take-ownership flag for this special case. If any managed
volume finds an ownership marker in the root of a share, it overwrites the marker file.
Otherwise, it imports the share as usual:
enable shares take-ownership
Do not use this option if it is possible that another ARX is managing one of the
namespace’s shares. This would unexpectedly remove the share(s) from service at the
other ARX.