JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 9/10 Installation Guide: Planning for Installation and Upgrade
search filter icon
search icon

Document Information


Part I Overall Planning of Any Solaris Installation or Upgrade

1.  Where to Find Solaris Installation Planning Information

2.  What's New in Solaris Installation

3.  Solaris Installation and Upgrade (Roadmap)

4.  System Requirements, Guidelines, and Upgrade (Planning)

System Requirements and Recommendations

Allocating Disk and Swap Space

General Disk Space Planning and Recommendations

Disk Space Recommendations for Software Groups

Upgrade Planning

Upgrading and Patching Limitations

Upgrade Programs

Installing a Solaris Flash Archive Instead of Upgrading

Creating an Archive That Contains Large Files

Upgrading With Disk Space Reallocation

Using the Patch Analyzer When Upgrading

Backing Up And Restarting Systems For an Upgrade

Planning Network Security

Restricted Security Specifics

Revising Security Settings After Installation

Locale Values

Platform Names and Groups

x86: Partitioning Recommendations

Default Boot-Disk Partition Layout Preserves the Service Partition

How to Find the Version of the Solaris OS That Your System Is Running

5.  Gathering Information Before Installation or Upgrade (Planning)

Part II Understanding Installations That Relate to ZFS, Booting, Solaris Zones, and RAID-1 Volumes

6.  ZFS Root File System Installation (Planning)

7.  SPARC and x86 Based Booting (Overview and Planning)

8.  Upgrading When Solaris Zones Are Installed on a System (Planning)

9.  Creating RAID-1 Volumes (Mirrors) During Installation (Overview)

10.  Creating RAID-1 Volumes (Mirrors) During Installation (Planning)



Upgrade Planning

Table 4-5 Solaris Upgrade Methods

Current Solaris OS
Solaris Upgrade Methods
Solaris 8, Solaris 9, Solaris 10
  • Solaris Live Upgrade – Upgrades a system by creating and upgrading a copy of the running system
  • The Solaris installation program – Provides an interactive upgrade with a graphical user interface or command-line interface

  • Custom JumpStart method – Provides an automated upgrade

Upgrading and Patching Limitations

The following table lists limitations when you upgrade a system under some conditions.

For More Information
For ZFS root pools, there are other upgrade limitations
You can only use Solaris Live Upgrade to upgrade ZFS root pools.
Upgrading to a different software group
You cannot upgrade your system to a software group that is not installed on the system. For example, if you previously installed the End User Solaris Software Group on your system, you cannot use the upgrade option to upgrade to the Developer Solaris Software Group. However, during the upgrade you can add software to the system that is not part of the currently installed software group.
For more information on software groups, see Disk Space Recommendations for Software Groups.
Upgrading when non-global zones are installed
You can upgrade a system that has non-global zones installed with the Solaris installation program, Solaris Live Upgrade or JumpStart. The following limitations apply:
  • Solaris Live Upgrade is the recommend program to upgrade or patch a system. Other upgrade programs might require extensive upgrade time, because the time required to complete the upgrade increases linearly with the number of installed non-global zones. If you are patching a system with Solaris Live Upgrade, you do not have to take the system to single-user mode and you can maximize your system's uptime.

  • When you use a Solaris Flash archive to install, an archive that contains non-global zones is not properly installed on your system.

For requirements and limitations see Upgrading With Non-Global Zones.
Patching with Solaris Live Upgrade from the Solaris 8 or 9 OS
You cannot use Solaris Live Upgrade to patch a Solaris 10 inactive boot environment when the active boot environment is running the Solaris 8 or 9 OS. Solaris Live Upgrade will invoke the patch utilities on the active boot partition to patch the inactive boot partition. The Solaris 8 and Solaris 9 patch utilities are unaware of Solaris Zone, Service Management Facility (SMF), and other enhancements in the Solaris 10 OS. Therefore the patch utilities fail to correctly patch an inactive Solaris 10 boot environment. Therefore, if you are using Solaris Live Upgrade to upgrade a system from the Solaris 8 or Solaris 9 OS to the Solaris 10 OS, you must first activate the Solaris 10 boot environment before patching. After the Solaris 10 boot environment is activated, you can either patch the active boot environment directly or set up another inactive boot environment and patch that one by using Solaris Live Upgrade.
Upgrading with Veritas file systems
The Solaris interactive installation and custom JumpStart programs do not present you with the opportunity to upgrade a system when you are using Veritas VxVM file systems under these conditions:
  • If the root file system to be upgraded is under Veritas control. For example, if the root (/) file system is mounted on a /dev/vx/... device.

  • If any Solaris software is installed on any file system that is under Veritas control. For example, if the /usr file system is mounted on a /dev/vx/... device.

To upgrade when Veritas VxVM is configured, use one of the following methods:

Upgrade Programs

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.

Upgrade Program
For More Information
Solaris Live Upgrade
Enables you to create a copy of the currently running system. The copy can be upgraded and then a reboot switches the upgraded copy to become the currently running system. Using Solaris Live Upgrade reduces the downtime that is required to upgrade the Solaris OS. Also, Solaris Live Upgrade can prevent problems with upgrading. An example is the ability to recover from an upgrade if the power fails, because the copy being upgraded is not the currently running system.
The Solaris installation program
Guides you through an upgrade with an interactive GUI.
Custom JumpStart program
Provides an automated upgrade. A profile file and optional preinstallation and postinstallation scripts provide the information required. When creating a custom JumpStart profile for an upgrade, specify install_type upgrade. You must test the custom JumpStart profile against the system's disk configuration and currently installed software before you upgrade. Use the pfinstall -D command on the system that you are upgrading to test the profile. You cannot test an upgrade profile by using a disk configuration file.

Installing a Solaris Flash Archive Instead of Upgrading

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 archive is created in a non-global zone

  • The archive is created in a global zone that has non-global zones installed

Creating an Archive That Contains Large Files

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.

Installation Program
For More Information
Solaris Live Upgrade
Custom JumpStart
Solaris interactive installation

Upgrading With Disk Space Reallocation

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 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:

  1. Backing up required files on the file systems that need to change.

  2. Repartitioning the disks on the basis of the file system changes.

  3. Restoring the backup files before the upgrade happens.

Using the Patch Analyzer When Upgrading

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.

If you are already running the Solaris OS and have installed individual patches, upgrading to a subsequent Solaris 10 release causes the following:

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 And Restarting Systems For an Upgrade

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.

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.