Go to main content

Transitioning From Oracle® Solaris 10 to Oracle Solaris 11.3

Exit Print View

Updated: December 2018

Boot, Recovery, Platform, Hardware, and Disk Labeling Changes

An Oracle Solaris 11 system boots from a ZFS root file system by default and the ZFS root file system is contained within a ZFS root pool named rpool. Creating a UFS file system is still supported in Oracle Solaris 11, but you can no longer boot from a UFS or a Solaris Volume Manager root file system.

    Review the following information, as it impacts the way the system is booted for recovery purposes:

  • If you use a system's service processor (SP) or ILOM to recover from a system problem, accessing a system's SP or ILOM is identical to previous releases. The differences mostly pertain to how the system is booted after you get to a SPARC based system's OBP ok prompt or to an x86 based system's firmware screen (BIOS or UEFI).

  • In Oracle Solaris 10, you use flash archive features to create a copy of a UFS or ZFS root environment and then restore the flash archive to recover the system environment, in the case of a system or device failure. In this release, you can create and deploy Oracle Solaris Unified Archives to perform system recovery and cloning operations. Oracle Solaris Unified Archives are system archives that can contain one or more archived instances of the OS. Each instance is an independently referenced system. An instance is defined as a boot environment in either a global or a non-global zone. Each system archive can contain any number of global and non-global zones. See Using Unified Archives for System Recovery and Cloning in Oracle Solaris 11.3 for details.