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

Document Information

Preface

Part I Overall Planning of an Oracle Solaris Installation or Upgrade

1.  Where to Find Oracle Solaris Installation Planning Information

2.  Oracle Solaris Installation and Upgrade Roadmap

3.  System Requirements, Guidelines, and Upgrade Information

4.  Gathering Information Before an Installation or Upgrade

Part II Understanding Installations Related to ZFS, Booting, Oracle Solaris Zones, and RAID-1 Volumes

5.  ZFS Root File System Installation Planning

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

7.  Upgrading When Oracle Solaris Zones Are Installed on a System

Oracle Solaris Zones Overview

Upgrading With Non-Global Zones

Zones Parallel Patching

Choosing an Installation Program to Upgrade a System Using Non-Global Zones

Live Upgrade and Non-Global Zones

Interactive GUI Installation and Non-Global Zones

JumpStart Installation and Non-Global Zones

Limitations When Upgrading With Non-global Zones

Backing Up Your System Before Performing an Upgrade With Zones

Disk Space Requirements for Non-Global Zones

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

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

Glossary

Index

Oracle Solaris Zones Overview

The Oracle Solaris Zones partitioning technology is used to virtualize operating system services and provide an isolated and secure environment for running applications. A non-global zone is a virtualized operating system environment created within a single instance of the Oracle Solaris OS.

When you create a non-global zone, you produce an application execution environment in which processes are isolated from the rest of the system. This isolation prevents processes that are running in one non-global zone from monitoring or affecting processes that are running in other non-global zones. Even a process running with superuser credentials cannot view or affect activity in other zones. A non-global zone also provides an abstract layer that separates applications from the physical attributes of the machine on which they are deployed. Examples of these attributes include physical device paths.

Every Oracle Solaris system contains a global zone. The global zone has a dual function. The global zone is both the default zone for the system and the zone used for system-wide administrative control. All processes run in the global zone if no non-global zones are created by the global administrator. The global zone is the only zone from which a non-global zone can be configured, installed, managed, or uninstalled. Only the global zone is bootable from the system hardware. Administration of the system infrastructure, such as physical devices, routing, or dynamic reconfiguration (DR), is possible only in the global zone. Appropriately privileged processes running in the global zone can access objects associated with the non-global zones.

For complete information on creating and configuring non-global zones, see Chapter 16, Introduction to Solaris Zones, in System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones.