If you are installing CVM for the first time, refer to the Sun StorEdge Volume Manager Installation Guide for additional pre-installation information.
Most of the commands involved in the installation of CVM are in the /sbin or /usr/sbin directories. You should add these directories to your PATH environment variable.
If you are using a Bourne Shell (sh or ksh), use the command:
PATH=/sbin:/usr/sbin:$PATH export PATH |
If you are using a C Shell (csh or tcsh), use the command:
setenv PATH /sbin:/usr/sbin:${PATH} |
A system using CVM has one or more disk groups, including the root disk group (rootdg). The rootdg must exist and cannot be shared between systems. At least one disk must exist within rootdg while CVM is running. Before installing CVM, you should decide where to place rootdg for each node in the cluster.
You can create rootdg by encapsulating the root disk as described in "1.4.4 Creating rootdg". Before beginning the installation, you must decide on the layout of shared disk groups. There may be one or more shared disk groups.
If you plan to use Dirty Region Logging (DRL) with CVM, consider leaving a small amount of space on the disk for these logs. The log size is proportional to the volume size and the number of nodes (each log has one recovery map plus one active map per node).
For a two-gigabyte volume in a two-node cluster, a log size of five blocks (one block per map) would be required. For every additional two gigabytes of volume size, the log size should then increase by approximately one block per map (so a four-gigabyte volume with two nodes would have a log size of ten blocks) up to a maximum of 96 blocks. For larger volumes, DRL changes the log granularity to accommodate the increased size without exceeding the maximum log size. A four-node cluster requires larger logs. See "2.1.4 Dirty Region Logging and CVM", for more information about log sizes.
To use CVM with a SPARCstorageTM Array, you must use firmware level 3.4 or later.