Installation manual

Configuring a Namespace
Adding a Volume
CLI Storage-Management Guide 7-21
fs3 192.168.25.28 Hematology lab server (DAS, Table 8)
fs4 192.168.25.29 prescription records (DAS, Table 3)
das2 192.168.25.22 DAS (Solaris) filer 2 (rack 16)
das3 192.168.25.23 DAS (Solaris) filer 3 (rack 16)
nas1 192.168.25.21 NAS filer 1 (rack 31)
192.168.25.61 (secondary)
192.168.25.62 (secondary)
das7 192.168.25.24 Redhat-LINUX filer 1
das8 192.168.25.25 Redhat-LINUX filer 2
nas2 192.168.25.44 NAS filer 2 (rack 31)
nas3 192.168.25.47 NAS filer 3 (rack 32)
bstnA6k(gbl)# namespace medarcv
bstnA6k(gbl-ns[medarcv])# sam-reference fs2
bstnA6k(gbl-ns[medarcv])# ...
Adding a Volume
The next, most important step in creating a namespace is creating one or more
volumes for it. Each volume in a namespace is like a single file system. The volume
aggregates one or more exports/shares from actual filers.
There are three forms of namespace volume: managed, direct, and shadow. The
default type is a managed volume, so-called because it keeps metadata on all of the
shares behind it and uses the metadata to manage the shares. A direct volume (called a
presentation volume in the GUI) does not have any metadata or support policy. A
shadow volume is a read-only copy of one or more managed volumes.
The next two chapters provide detailed instructions for configuring direct and
managed volumes. Shadow volumes are described in a chapter after the
storage-policy chapters. One namespace can support all three types of volumes.
From gbl-ns mode, use the
volume command to create a volume:
volume topdir
where topdir (1-1024 characters) is the directory with the contents of the filer
shares. Volumes cannot contain one another: if you make a “/var” volume, you
cannot have a “/var/log” volume in the same namespace; if you make a “/”
volume, you cannot have any other volumes.