With the -m option to create a new boot environment and splitĪ directory off to its own slice. The directory is then a file system that can be shared If you want to share a directory, the directory must be split When you create any new boot environments, /home is shared with the new boot environment by default. For example, if root ( /), /var, and /home areĪll on the same slice, reconfigure the disk and put /home on its own slice. You can reslice the disk before creating the new boot environmentĪnd put the shareable file system on its own slice. You can reconfigure the disk several ways depending on your needs. Shareable file systems must be user-defined file systemsĪnd on separate swap slices on both the active and new boot environments. File systems such as /home are not critical file systems and could be shared betweenīoot environments. Systems critical to the operating environment such as root ( /)Īnd /var must be copied. Slice to be shared between boot environments rather than copied to conserve You might want some large file systems on that
#VERITAS VOLUME MANAGER COMMAND LINE UPGRADE#
Solaris Live Upgrade copies the entire contents of a slice to the designated Guidelines for Selecting Slices for Shareable File Systems Used by any other boot environment, whether the slice contains a swap, ufs, The boot environment creation fails if the swap slice is being The swap slice cannot be in use by any boot environment except the currentīoot environment or if the -s option is used, the source bootĮnvironment. Guidelines for Selecting a Slice for a swap File Note - If you have problems upgrading with Veritas VxVM, see "System Panics When Upgrading With Solaris Live Upgrade Running Veritas When upgrading or installing a flash archive, see "Upgrading Metadevices and Volumes" Using boot environments with metadevices or volumes has special considerations
When creating a new boot environment, the lucreate -m command recognizes the following three types of devices only:Ī physical slice in the form of /dev/dsk/c numt numd nums numĪ Solaris Volume Manager metadevice in the form of /dev/md/dsk/d numĪ Veritas VxFS volume in the form of /dev/vx/dsk/ volume_name Systems can be either a physical slice or volume The root ( /) file system, cannot be a VsVM volume root ( /) must be System, the source can be a volume or physical slice Root ( /) file system, the source can be a metadeviceįile system, must be either a stripe with only a singleįile systems can be either a physical slice or metadevice If Target is not a root ( /) File System, but is for /usr, /var, or /opt If Target is a Metadevice for a root ( /) File System Table 31-2 Acceptable Slices for Metadevices or Volumes
Table 31-2 describes the acceptable disk configurationsįor creating a boot environment when using metadevices or volumes. You can use either a physical disk slice, a Solaris Volume Manager metadevice, ( /) file system when creating a new boot environment.įor any file system except the root ( /) file system, You cannot use a Veritas VxFS volume for the root
Must be either a stripe with only a single disk or a mirror on a single-disk If you chooseĪ Solaris Volume Manager metadevice for the root file system, the metadevice ( /) file system for the new boot environment can be eitherĪ physical disk slice or a Solaris Volume Manager metadevice. When creating a new boot environment, the slice chosen for the root The source boot environment can be contained on any combination of physicalĭisk slices, Solaris Volume Manager metadevices, or Veritas Volume Manager You can use Solaris Live Upgrade on a system that is currently usingĮither Solaris Volume Manager metadevices or Veritas Volume Manager VxVM volumes. Guidelines for Selecting Slices for root ( /) Mirrors
0 kommentar(er)
