|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 10 9/10 Installation Guide: Planning for Installation and Upgrade|
For a UFS file system, you can upgrade a system by using one of three different upgrade methods: Solaris Live Upgrade, the Solaris installation program, and custom JumpStart.
For a ZFS root pool, you must use Solaris Live Upgrade to upgrade. For ZFS upgrades, see Chapter 12, Solaris Live Upgrade for ZFS (Planning), in Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
Table 4-5 Solaris Upgrade Methods
The following table lists limitations when you upgrade a system under some conditions.
You can perform a standard interactive upgrade with the Solaris installation program or an unattended upgrade with the custom JumpStart installation method. Solaris Live Upgrade enables you to upgrade a running system.
The Solaris Flash installation feature provides a method of creating a copy of the whole installation from a master system that can be replicated on many clone systems. This copy is called a Solaris Flash archive. You can install an archive by using any installation program.
Caution - A Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not compatible with Solaris Zones partitioning technology. If you create a Solaris Flash archive, the resulting archive is not installed properly when the archive is deployed under these conditions:
The default copy method that is used when you create a Solaris Flash archive is the cpio utility. Individual file sizes cannot be greater than 4 Gbytes. If you have large individual files, the flarcreate command with the -L pax option uses the pax utility to create an archive without limitations on individual file sizes. Individual file sizes can be greater than 4 Gbytes.
For information about installing an archive, see the following table.
The upgrade option in the Solaris installation program and the upgrade keyword in the custom JumpStart program provide the ability to reallocate disk space. This reallocation automatically changes the sizes of the disk slices. You can reallocate disk space if the current file systems do not have enough space for the upgrade. For example, file systems might need more space for the upgrade for the following reasons:
The Solaris software group that is currently installed on the system contains new software in the new release. Any new software that is included in a software group is automatically selected to be installed during the upgrade.
The size of the existing software on the system has increased in the new release.
The auto-layout feature attempts to reallocate the disk space to accommodate the new size requirements of the file system. Initially, auto-layout attempts to reallocate space, based on a set of default constraints. If auto-layout cannot reallocate space, you must change the constraints on the file systems.
Note - Auto-layout does not have the ability to “grow” file systems. Auto-layout reallocates space by the following process:
Backing up required files on the file systems that need to change.
Repartitioning the disks on the basis of the file system changes.
Restoring the backup files before the upgrade happens.
If you are using the Solaris installation program, and auto-layout cannot determine how to reallocate the disk space, you must use the custom JumpStart program to upgrade.
If you are using the custom JumpStart method to upgrade and you create an upgrade profile, disk space might be a concern. If the current file systems do not contain enough disk space for the upgrade, you can use the backup_media and layout_constraint keywords to reallocate disk space. For an example of how to use the backup_media and layout_constraint keywords in a profile, refer to Profile Examples in Oracle Solaris 10 9/10 Installation Guide: Custom JumpStart and Advanced Installations.
The Patch Analyzer performs an analysis on your system if you want to upgrade to one of these releases that follow the initial Solaris 10 3/05 release.
Solaris 10 1/06 release
Solaris 10 6/06 release
If you are already running the Solaris OS and have installed individual patches, upgrading to a subsequent Solaris 10 release causes the following:
Any patches that were supplied as part of one of the releases noted above are reapplied to your system. You cannot back out these patches.
Any patches that were previously installed on your system and are not included in one of the releases noted above are removed.
You can use the Patch Analyzer to determine which patches, if any, will be removed. For detailed instructions about using the Patch Analyzer, refer to Appendix C, Using the Patch Analyzer When Upgrading (Tasks), in Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
Backing up your existing file systems before you upgrade to the Solaris OS is highly recommended. If you copy file systems to removable media, such as tape, you can safeguard against data loss, damage, or corruption.
For detailed instructions to back up your system, refer to Chapter 23, Backing Up and Restoring UFS File Systems (Overview), in System Administration Guide: Devices and File Systems.
To backup your system when non-global zones are installed, see Chapter 27, Solaris Zones Administration (Overview), in System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones.
In previous releases, the restart mechanism enabled you to continue an upgrade after a loss of power or other similar problem. Starting with the Solaris 10 10/08 release, the restart mechanism is unreliable. If you have a problem, your upgrade might not restart.