Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 1/13 Installation Guide: Live Upgrade and Upgrade Planning Oracle Solaris 10 1/13 Information Library |
Part I Upgrading With Live Upgrade
1. Where to Find Oracle Solaris Installation Planning Information
4. Using Live Upgrade to Create a Boot Environment (Tasks)
5. Upgrading With Live Upgrade (Tasks)
6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks)
7. Maintaining Live Upgrade Boot Environments (Tasks)
8. Upgrading the Oracle Solaris OS on a System With Non-Global Zones Installed
Part II Upgrading and Migrating With Live Upgrade to a ZFS Root Pool
10. Live Upgrade and ZFS (Overview)
11. Live Upgrade for ZFS (Planning)
12. Creating a Boot Environment for ZFS Root Pools
13. Live Upgrade for ZFS With Non-Global Zones Installed
A. Live Upgrade Command Reference
C. Additional SVR4 Packaging Requirements (Reference)
A file that contains a collection of files that were copied from a master system. The file also contains identification information about the archive, such as a name and the date that you created the archive. After you install an archive on a system, the system contains the exact configuration of the master system.
An archive could be a differential archive, which is a flash archive that contains only the differences between two system images, an unchanged master image and an updated master image. The differential archive contains files to be retained, modified, or deleted from the clone system. A differential update changes only the files specified and is restricted to systems that contain software consistent with the unchanged master image.
A user-defined Bourne shell script, specified within the rules file, that performs tasks before the Oracle Solaris software is installed on the system. You can use begin scripts only with JumpStart installations.
To load the system software into memory and start it.
x86 only: A boot archive is a collection of critical files that is used to boot the Oracle Solaris OS. These files are needed during system startup before the root (/) file system is mounted. Two boot archives are maintained on a system:
The boot archive that is used to boot the Oracle Solaris OS on a system. This boot archive is sometimes called the primary boot archive.
The boot archive that is used for recovery when the primary boot archive is damaged. This boot archive starts the system without mounting the root (/) file system. On the GRUB menu, this boot archive is called failsafe. The archive's essential purpose is to regenerate the primary boot archive, which is usually used to boot the system.
A collection of mandatory file systems (disk slices and mount points) that are critical to the operation of the Oracle Solaris OS. These disk slices might be on the same disk or distributed across multiple disks.
The active boot environment is the one that is currently booted. Exactly one active boot environment can be booted. An inactive boot environment is not currently booted, but can be in a state of waiting for activation on the next reboot.
x86 only: The boot loader is the first software program that runs after you turn on a system. This program begins the booting process.
A server system that provides client systems on the same network subnet with the programs and information that they need to start. A boot server is required to install over the network if the install server is on a different subnet than the systems on which Oracle Solaris software is to be installed.
A software group that contains the minimum software that is required to boot and run the Oracle Solaris OS on a system. Core includes some networking software and the drivers that are required to run the Common Desktop Environment (CDE) desktop. Core does not include the CDE software.
File systems that are required by the Oracle Solaris OS. When you use Live Upgrade, a feature of Oracle Solaris, these file systems are separate mount points in the vfstab file of the active and inactive boot environments. Example file systems are root (/), /usr, /var, and /opt. These file systems are always copied from the source to the inactive boot environment.
A generic name for the following ZFS entities: clones, file systems, snapshots, or volumes.
A software group that contains the End User Oracle Solaris Software Group plus the libraries, include files, man pages, and programming tools for developing software.
(Dynamic Host Configuration Protocol) An application-layer protocol. Enables individual computers, or clients, on a TCP/IP network to extract an IP address and other network configuration information from a designated and centrally maintained DHCP server or servers. This facility reduces the overhead of maintaining and administering a large IP network.
A software group that contains the Core Software Group plus the recommended software for an end user, including the Common Desktop Environment (CDE) and DeskSet software.
A software group that contains the entire Oracle Solaris release.
A software group that contains the entire Oracle Solaris release plus additional hardware support for OEMs. This software group is recommended when installing Oracle Solaris software on SPARC based servers.
A directory that contains critical system configuration files and maintenance commands.
A file system on an OS server that is shared with other systems on a network. For example, the /export file system can contain the root (/) file system and swap space for diskless clients and the home directories for users on the network. Diskless clients rely on the /export file system on an OS server to boot and run.
x86 only: A boot archive that is used for recovery when the primary boot archive is damaged. This boot archive starts the system without mounting the root (/) file system. This boot archive is called failsafe on the GRUB menu. The archive's essential purpose is to regenerate the primary boot archive, which is usually used to boot the system. See boot archive.
A reversion to the environment that ran previously. Use fallback when you are activating an environment and the boot environment that is designated for booting fails or shows some undesirable behavior.
A logical partition of a disk drive that is dedicated to a particular operating system on x86 based systems. To install the Oracle Solaris software, you must set up at least one Oracle Solaris fdisk partition on an x86 based system. x86 based systems allow up to four different fdisk partitions on a disk. These partitions can be used to hold individual operating systems. Each operating system must be located on a unique fdisk partition. A system can only have one Oracle Solaris fdisk partition per disk.
A server that provides the software and file storage for systems on a network.
In the Oracle Solaris OS, a tree-structured network of files and directories that you can access.
A user-defined Bourne shell script, specified within the rules file, that performs tasks after the Oracle Oracle Solaris software is installed on the system but before the system reboots. You use finish scripts with JumpStart installations.
An Oracle Solaris installation feature that enables you to create an archive of the files on a system, called the master system. You can then use the archive to install other systems, making the other systems identical in their configuration to the master system. See also archive.
To put data into a structure or divide a disk into sectors for receiving data.
In Oracle Solaris Zones, the global zone is both the default zone for the system and the zone used for system-wide administrative control. The global zone is the only zone from which a non-global zone can be configured, installed, managed, or uninstalled. Administration of the system infrastructure, such as physical devices, routing, or dynamic reconfiguration (DR), is only possible in the global zone. Appropriately privileged processes running in the global zone can access objects associated with other zones. See also Oracle Solaris Zones and non-global zone.
x86 only: GNU GRand Unified Bootloader (GRUB) is an open source boot loader with a simple menu interface. The menu displays a list of operating systems that are installed on a system. GRUB enables you to easily boot these various operating systems, such as the Oracle Solaris OS, Linux, or Microsoft Windows.
x86 only: A boot menu that is a submenu of the GRUB main menu. GRUB commands are displayed on this menu. These commands can be edited to change boot behavior.
x86 only: A boot menu that lists the operating systems that are installed on a system. From this menu, you can easily boot an operating system without modifying the BIOS or fdisk partition settings.
An installation that overwrites the currently running software or initializes a blank disk.
An initial installation of the Oracle Solaris OS overwrites the system's disk or disks with the new version of the Oracle Solaris OS. If your system is not running the Oracle Solaris OS, you must perform an initial installation. If your system is running an upgradable version of the Oracle Solaris OS, an initial installation overwrites the disk and does not preserve the OS or local modifications.
A server that provides the Oracle Solaris DVD or CD images from which other systems on a network can install Oracle Solaris (also called a media server). You can create an install server by copying the Oracle Solaris DVD or CD images to the server's hard disk.
A type of installation in which the Oracle Solaris software is automatically installed on a system that is based on a user-defined profile. You can create customized profiles for different types of users and systems. A custom JumpStart installation is a JumpStart installation you create.
A type of installation in which the Oracle Solaris software is automatically installed on a system by using the factory-installed JumpStart software.
An upgrade method that enables a duplicate boot environment to be upgraded while the active boot environment is still running, thus eliminating downtime of the production environment.
A geographic or political region or community that shares the same language, customs, or cultural conventions (English for the U.S. is en_US, and English for the U.K. is en_UK).
x86 only: A file that lists all the operating systems that are installed on a system. The contents of this file dictate the list of operating systems that is displayed on the GRUB menu. From the GRUB menu, you can easily boot an operating system without modifying the BIOS or fdisk partition settings.
A minimal, bootable root (/) file system that is included in Oracle Solaris installation media. A miniroot consists of the Oracle Solaris software that is required to install and upgrade systems. On x86 based systems, the miniroot is copied to the system to be used as the failsafe boot archive. See failsafe boot archive.
See RAID-1 volume.
The process of accessing a directory from a disk that is attached to a machine that is making the mount request or a remote disk on a network. To mount a file system, you need a mount point on the local system and the name of the file system to be mounted (for example, /usr).
A workstation directory to which you mount a file system that exists on a remote machine.
A way to install software over the network from a system with a CD-ROM or DVD-ROM drive to a system without a CD-ROM or DVD-ROM drive. Network installations require a name server and an install server.
A group of systems (called hosts) that are connected through hardware and software so that they can communicate and share information. Referred to as a local area network (LAN). One or more servers are usually needed when systems are networked.
The SunOS 4.0 (minimum) Network Information Service. A distributed network database that contains key information about the systems and the users on the network. The NIS database is stored on the master server and all the slave servers.
The SunOS 5.0 (minimum) Network Information Service. NIS+ replaces NIS, the SunOS 4.0 (minimum) Network Information Service.
A virtualized operating system environment created within a single instance of the Oracle Solaris Operating System. One or more applications can run in a non-global zone without interacting with the rest of the system. Non-global zones are also called zones. See also Oracle Solaris Zones and global zone.
Systems that are not connected to a network or do not rely on other systems.
A file system that contains the mount points for third-party and unbundled software.
The Oracle Solaris software that is installed on a system, which you can access on the Oracle Solaris DVDs or CDs or an install server's hard disk to which you have copied the Oracle Solaris DVD or CD images.
A graphical user interface (GUI) or command-line interface (CLI) installation program that uses wizard panels to guide you step-by-step through installing the Oracle Solaris software and third-party software.
A software partitioning technology used to virtualize operating system services and provide an isolated and secure environment for running applications. When you create a non-global zone, you produce an application execution environment in which processes are isolated from all other zones. This isolation prevents processes that are running in a zone from monitoring or affecting processes that are running in any other zones. See also global zone and non-global zone.
A collection of software that is grouped into a single entity for modular installation. The Oracle Solaris software is divided into software groups, which are each composed of clusters and packages.
A script that you can run manually or as part of the Oracle Solaris installation program. The patch analyzer performs an analysis on your system to determine which (if any) patches will be removed by upgrading to a Oracle Solaris update.
A logical group of devices describing the layout and physical characteristics of the available ZFS storage. Space for datasets is allocated from a pool.
A boot archive that is used to boot the Oracle Solaris OS on a system. This boot archive is sometimes called the primary boot archive. See boot archive.
A text file that defines how to install the Oracle Solaris software when using the custom JumpStart method. For example, a profile defines which software group to install. Every rule specifies a profile that defines how a system is to be installed when the rule is matched. You usually create a different profile for every rule. However, the same profile can be used in more than one rule. See also rules file.
A class of volume that can be a stripe or a concatenation. These components are also called submirrors. A stripe or concatenation is the basic building block for mirrors.
A class of volume that replicates data by maintaining multiple copies. A RAID-1 volume is composed of one or more RAID-0 volumes called submirrors. A RAID-1 volume is sometimes called a mirror.
A virtual device that stores data and parity on multiple disks that can be used as a ZFS storage pool. RAID-Z is similar to RAID-5.
A software group that contains the minimum code that is required to boot and run a Oracle Solaris system with limited network service support. The Reduced Networking Software Group provides a multiuser text-based console and system administration utilities. This software group also enables the system to recognize network interfaces, but does not activate network services.
The top level of a hierarchy of items. Root is the one item from which all other items are descended. See root directory or root (/) file system.
The top-level file system from which all other file systems stem. The root (/) file system is the base on which all other file systems are mounted, and is never unmounted. The root (/) file system contains the directories and files critical for system operation, such as the kernel, device drivers, and the programs that are used to start (boot) a system.
The top-level directory from which all other directories stem.
A series of values that assigns one or more system attributes to a profile. A rule is used in a custom JumpStart installation.
A text file that contains a rule for each group of systems or single systems that you want to install automatically. Each rule distinguishes a group of systems, based on one or more system attributes. The rules file links each group to a profile, which is a text file that defines how the Oracle Solaris software is to be installed on each system in the group. A rules file is used in a custom JumpStart installation. See also profile.
A generated version of the rules file. The rules.ok file is required by the custom JumpStart installation software to match a system to a profile. You must use the check script to create the rules.ok file.
The unit into which the disk space is divided by the software.
A logical grouping of the Oracle Solaris software (clusters and packages). During a Oracle Solaris installation, you can install one of the following software groups: Core, End User Oracle Solaris Software, Developer Oracle Solaris Software, or Entire Oracle Solaris Software, and for SPARC systems only, Entire Oracle Solaris Software Group Plus OEM Support.
A database that stores information about the state of your Solaris Volume Manager configuration. The state database is a collection of multiple, replicated database copies. Each copy is referred to as a state database replica. The state database tracks the location and status of all known state database replicas.
A copy of a state database. The replica ensures that the data in the database is valid.
See RAID-0 volume.
A slice or file that temporarily holds the contents of a memory area till it can be reloaded in memory. Also called the /swap or swap volume.
The process of removing access to a directory on a disk that is attached to a machine or to a remote disk on a network.
An installation, or to perform an installation, on a system that changes software that is of the same type. Unlike an upgrade, an update might downgrade the system. Unlike an initial installation, software of the same type that is being installed must be present before an update can occur.
An installation that merges files with existing files and preserves modifications where possible.
An upgrade of the Oracle Solaris OS merges the new version of the Oracle Solaris OS with the existing files on the system's disk or disks. An upgrade saves as many modifications as possible that you have made to the previous version of the Oracle Solaris OS.
An option that is presented by the Oracle Solaris installation. The upgrade procedure merges the new version of Oracle Solaris with existing files on your disk or disks. An upgrade also saves as many local modifications as possible since the last time Oracle Solaris was installed.
A file system on a standalone system or server that contains many of the standard UNIX programs. Sharing the large /usr file system with a server rather than maintaining a local copy minimizes the overall disk space that is required to install and run the Oracle Solaris software on a system.
A file system or directory (on standalone systems) that contains system files that are likely to change or grow over the life of the system. These files include system logs, vi files, mail files, and UUCP files.
A logical device in a ZFS pool, which can be a physical device, a file, or a collection of devices.
A group of physical slices or other volumes that appear to the system as a single logical device. A volume is functionally identical to a physical disk for the purposes of an application or file system.
In some command-line utilities, a volume is called a metadevice. Volume is also called pseudo device or virtual device in standard UNIX terms.
A program that provides a mechanism to administer and obtain access to the data on DVD-ROMs, CD-ROMs, and diskettes.
A file system using storage pools to manage physical storage.
See non-global zone