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)

Task Map: Installing or Upgrading the Solaris Software

Installing From the Network or From DVD or CDs?

Initial Installation, or Upgrade?

Initial Installation


Choosing a Solaris Installation Method

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

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)



Choosing a Solaris Installation Method

The Solaris OS provides several programs for installation or upgrade. Each installation technology offers different features that are designed for specific installation requirements and environments. Use the following table to help you decide which installation method to use.

Table 3-2 Choosing Your Installation Method

Installation Method
Reasons for Choosing This Program
Install one system from CD-ROM or DVD-ROM media with an interactive program.
Solaris installation program
  • This program divides tasks into panels, prompts you for information, and offers default values.
  • This program is not an efficient method when you have to install or upgrade multiple systems. For batch installations of multiple systems, use custom JumpStart or the Solaris Flash installation feature.

Install one system over a local area network.
Solaris installation program over the network
This program enables you to set up an image of the software you want to install on a server and install this image on a remote system. If you need to install multiple systems, you can use the network installation image with the custom JumpStart and Solaris Flash installation methods to efficiently install or upgrade systems on your network.
Automate the installation or upgrade of multiple systems based on profiles you create.
Custom JumpStart
This program efficiently installs multiple systems. But if you only have a few systems, the creation of a custom JumpStart environment might be time consuming. For a few systems, use the Solaris interactive installation program.
Replicate the same software and configuration on multiple systems.
Solaris Flash archives
  • This program saves installation time by installing all Solaris packages at once on your system. Other programs install each individual Solaris package and update the package map for each package.
  • Solaris Flash archives are large files and require a significant amount of disk space. To manage different installation configurations or to change your installation configuration, you might consider using the custom JumpStart installation method. Alternatively, you can accomplish system-specific customizations by using a JumpStart finish script or an embedded Solaris Flash postdeployment script.

Install systems over a wide area network (WAN) or the Internet.
WAN boot
If you want to install a Solaris Flash archive over the network, this program enables a secure installation.
Upgrade a system while it is running.
Solaris Live Upgrade
  • This program enables you to upgrade or add patches to avoid the system down time related to a standard upgrade
  • This program enables you to test an upgrade or new patches without affecting the current OS

After installing the Solaris OS, create an isolated application environment.
Solaris Zones partitioning technology
This program creates isolated non-global zones that provide a secure application environment. This isolation prevents processes that are running in one zone from monitoring or affecting processes that are running in any other zones.