Information Technology Reference
In-Depth Information
metadb(1M)
—Creates and deletes database replicas
➤
metadetach(1M)
—Detaches a volume from a RAID 1 (mirror) volume
➤
metadevadm(1M)
—Checks device ID configuration
➤
metahs(1M)
—Manages hot spares and hot spare pools
➤
metainit(1M)
—Configures volumes
➤
metaoffline(1M)
—Places submirrors offline
➤
metaonline(1M)
—Places submirrors online
➤
metaparam(1M)
—Modifies volume parameters
➤
metarecover(1M)
—Recovers configuration information for soft partitions
➤
metarename(1M)
—Renames volumes
➤
metareplace(1M)
—Replaces slices of submirrors and RAID 5 volumes
➤
metaroot(1M)
—Sets up files for mirroring the root file system
➤
metaset(1M)
—Administers disk sets
➤
metastat(1M)
—Displays the status of volumes or hot spare pools
➤
metasync(1M)
—Resynchronizes volumes during reboot
➤
metattach(1M)
—Attaches a metadevice to a mirror
➤
Summary
A virtual disk management system can overcome disk capacity and architec-
ture limitations and improve performance and availability. In addition, man-
ageability is enhanced by the use of a graphical management tool.
The three main storage factors are performance, availability, and hardware
costs. A virtual disk management system allows managing tradeoffs between
these three factors and in some cases reduces the impact of these factors.
The techniques used to improve performance and/or availability include con-
catenation, striping, mirroring, duplexing and the different levels of RAID.
The Solaris Volume Manager (SVM) manages volumes (collections of phys-
ical disk slices) that include a State Database that stores information on the
SVM configuration and one or more replicas (to provide redundancy). A Hot
Spare Pool is used to automatically replace failed disk slices. A SMV Disk Set
(Volumes, State Database, Replicas and Hot Spare Pool) can be shared by
several host systems.
