Why Use Multiple Boot Environments?

With multiple boot environments, the process of updating software becomes a low risk operation because system administrators can create backup boot environments before making any software updates to your system. If needed, they have the option of booting a backup boot environment.

Here are some specific examples where having more than one Oracle Solaris boot environment, and managing them with the beadm utility, is useful:

• If you are modifying a boot environment, you can take a snapshot of that environment at any stage during modifications by using the beadm create command. A snapshot is a read-only image of a dataset or boot environment at a given point in time.

  You can create custom names for each snapshot that identify when or why the snapshot was created. For example, if you are doing monthly upgrades to your boot environment, you can capture snapshots for each monthly upgrade. You can use the beadm list -s command to view the available snapshots for a boot environment.

  A snapshot is not bootable. But, you can create a boot environment, based on that snapshot, by using the -e option for the beadm create command. Then you can use the beadm activate command to specify that this boot environment will become the default boot environment on the next reboot.

• You can maintain more than one boot environment on your system, and perform various updates on each of them as needed. For example, you can clone a boot environment by using the beadm create command. A clone is a bootable copy of a boot environment. Then, you can install, test, and update different software packages on the original boot environment and on its clone.

  Although only one boot environment can be active at a time, you can mount an inactive boot environment by using the beadm mount command. Then, you could use the pkg install packagename with the -R option to update specific packages on that environment.

• When you use either the Package Manager tool, the Update Manager tool, or the pkg command to install or update packages in your active Oracle Solaris boot environment, this process may create a clone of that boot environment. If a clone is created, packages are installed or updated in the clone rather than in the original boot environment. After successfully completing the changes, the new clone is activated. Then, the clone will become the new default boot environment on the next reboot. The original boot environment remains on the GRUB menu for x86 systems, or the boot menu for SPARC systems, as an alternate selection.

  You can use the beadm list command to see a list of all the boot environments on the system, including the backup boot environment that still has its original, unchanged software. If you are not satisfied with the changes made to the environment, you can use the beadm activate command to specify that the backup will become the default boot environment on the next reboot.

  For more information, see Images and Boot Environments in Oracle Solaris 11 Express Image Packaging System Guide .