Creating a Boot Environment
The process of creating a boot environment provides a method of copying critical file systems from an active boot environment to a new boot environment. The disk is reorganized if necessary, file systems are customized, and the critical file systems are copied to the new boot environment.
File System Types
Solaris Live Upgrade distinguishes between two file system types: critical file systems and shareable. The following table describes these file system types.
|
File System Type |
Description |
Examples and More Information |
|---|---|---|
|
Critical file systems |
Critical file systems are required by the Solaris OS. These file systems are separate mount points in the vfstab of the active and inactive boot environments. These file systems are always copied from the source to the inactive boot environment. Critical file systems are sometimes referred to as nonshareable. |
Examples are root (/), /usr, /var, or /opt. |
|
Shareable file systems |
Shareable file systems are user-defined files such as /export that contain the same mount point in the vfstab in both the active and inactive boot environments. Therefore, updating shared files in the active boot environment also updates data in the inactive boot environment. When you create a new boot environment, shareable file systems are shared by default. But you can specify a destination slice and then the file systems are copied. |
/export is an example of a file system that can be shared. For more detailed information about shareable file systems, see Guidelines for Selecting Slices for Shareable File Systems. |
|
Swap |
|
|
Creating RAID-1 Volumes on File Systems
Solaris Live Upgrade can create a boot environment with RAID-1 volumes (mirrors) on file systems. For an overview, see Creating a Boot Environment With RAID-1 Volume File Systems.
Copying File Systems
The process of creating a new boot environment begins by identifying an unused slice where a critical file system can be copied. If a slice is not available or a slice does not meet the minimum requirements, you need to format a new slice.
After the slice is defined, you can reconfigure the file systems on the new boot environment before the file systems are copied into the directories. You reconfigure file systems by splitting and merging them, which provides a simple way of editing the vfstab to connect and disconnect file system directories. You can merge file systems into their parent directories by specifying the same mount point. You can also split file systems from their parent directories by specifying different mount points.
After file systems are configured on the inactive boot environment, you begin the automatic copy. Critical file systems are copied to the designated directories. Shareable file systems are not copied, but are shared. The exception is that you can designate some shareable file systems to be copied. When the file systems are copied from the active to the inactive boot environment, the files are directed to the new directories. The active boot environment is not changed in any way.
|
For procedures to split or merging file systems | |
|
For an overview of creating a boot environment with RAID–1 volume file systems |
Examples of Creating a New Boot Environment
For UFS file systems, the following figures illustrate various ways of creating new boot environments.
For ZFS file systems, see Chapter 11, Solaris Live Upgrade and ZFS (Overview)
Figure 2–2 shows that critical file system root (/) has been copied to another slice on a disk to create a new boot environment. The active boot environment contains the root (/) file system on one slice. The new boot environment is an exact duplicate with the root (/) file system on a new slice. The /swap volume and /export/home file system are shared by the active and inactive boot environments.
Figure 2–2 Creating an Inactive Boot Environment – Copying the root (/) File System
Figure 2–3 shows critical file systems that have been split and have been copied to slices on a disk to create a new boot environment. The active boot environment contains the root (/) file system on one slice. On that slice, the root (/) file system contains the /usr, /var, and /opt directories. In the new boot environment, the root (/) file system is split and /usr and /opt are put on separate slices. The /swap volume and /export/home file system are shared by both boot environments.
Figure 2–3 Creating an Inactive Boot Environment – Splitting File Systems
Figure 2–4 shows critical file systems that have been merged and have been copied to slices on a disk to create a new boot environment. The active boot environment contains the root (/) file system, /usr, /var, and /opt with each file system on their own slice. In the new boot environment, /usr and /opt are merged into the root (/) file system on one slice. The /swap volume and /export/home file system are shared by both boot environments.
Figure 2–4 Creating an Inactive Boot Environment – Merging File Systems
- © 2010, Oracle Corporation and/or its affiliates