Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning |
Part I Upgrading With Solaris Live Upgrade
1. Where to Find Solaris Installation Planning Information
2. Solaris Live Upgrade (Overview)
3. Solaris Live Upgrade (Planning)
4. Using Solaris Live Upgrade to Create a Boot Environment (Tasks)
5. Upgrading With Solaris Live Upgrade (Tasks)
Task Map: Upgrading a Boot Environment
Upgrading a System With Packages or Patches
To Upgrade a Network Installation Image on a Boot Environment
To Upgrade a Network Installation Image From Multiple CDs
To Add Packages to a Network Installation Image on a Boot Environment
To Add Patches to a Network Installation Image on a Boot Environment
To Obtain Information on Packages Installed on a Boot Environment
Upgrading by Using a JumpStart Profile
To Create a Profile to be Used by Solaris Live Upgrade
Installing Solaris Flash Archives on a Boot Environment
To Install a Solaris Flash Archive on a Boot Environment
To Install a Solaris Flash Archive With a Profile
To Install a Solaris Flash Archive With a Profile Keyword
Requirements and Limitations for Activating a Boot Environment
To Activate a Boot Environment
To Activate a Boot Environment and Synchronize Files
x86: Activating a Boot Environment With the GRUB Menu
x86: To Activate a Boot Environment With the GRUB Menu
6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks)
7. Maintaining Solaris Live Upgrade Boot Environments (Tasks)
8. Upgrading the Solaris OS on a System With Non-Global Zones Installed
9. Solaris Live Upgrade (Examples)
10. Solaris Live Upgrade (Command Reference)
Part II Upgrading and Migrating With Solaris Live Upgrade to a ZFS Root Pool
11. Solaris Live Upgrade and ZFS (Overview)
12. Solaris Live Upgrade for ZFS (Planning)
13. Creating a Boot Environment for ZFS Root Pools
14. Solaris Live Upgrade For ZFS With Non-Global Zones Installed
B. Additional SVR4 Packaging Requirements (Reference)
Use the luupgrade command to upgrade a boot environment. This section provides the procedure for upgrading an inactive boot environment from files that are located on the following media:
NFS server
Local file
Local tape
Local device, including DVD or CD
When you upgrade a boot environment with the latest OS, you do not affect the active boot environment. The new files merge with the inactive boot environment critical file systems, but shareable file systems are not changed.
You can upgrade when RAID-1 volumes are installed, or if non-global zones are installed, or you can install a Solaris Flash:
You can upgrade an inactive boot environment that contains any combination of physical disk slices, Solaris Volume Manager volumes, or Veritas Volume Manager volumes. The slice that is chosen for the root (/) file system must be a single-slice concatenation that is included in a RAID–1 volume (mirror). For procedures about creating a boot environment with mirrored file systems, see To Create a Boot Environment With RAID-1 Volumes (Mirrors).
Note - If VxVM volumes are configured on your current system, the lucreate command can create a new boot environment. When the data is copied to the new boot environment, the Veritas file system configuration is lost and a UFS file system is created on the new boot environment.
You can upgrade a system that has non-global zones installed with any installation program. For procedures about upgrading with non-global zones, see Chapter 8, Upgrading the Solaris OS on a System With Non-Global Zones Installed.
Rather than upgrading, if you have created a Solaris Flash archive, you could install the archive on an inactive boot environment. The new files overwrite critical file systems of the inactive boot environment, but shareable file systems are not changed. See Installing Solaris Flash Archives on a Boot Environment.
You can use Solaris Live Upgrade to add patches and packages to a system. Solaris Live Upgrade creates a copy of the currently running system. This new boot environment can be upgraded or you can add packages or patches. When you use Solaris Live Upgrade, the only downtime the system incurs is that of a reboot. You can add patches and packages to a new boot environment with the luupgrade command.
Caution - When adding and removing packages or patches, Solaris Live Upgrade requires packages or patches that comply with the SVR4 advanced packaging guidelines. While Sun packages conform to these guidelines, Sun cannot guarantee the conformance of packages from third-party vendors. If a package violates these guidelines, the package can cause the package-addition software to fail or alter the active boot environment during an upgrade. For more information about packaging requirements, see Appendix B, Additional SVR4 Packaging Requirements (Reference). |
Table 5-2 Upgrading a Boot Environment With Packages and Patches
|
To upgrade by using this procedure, you must use a DVD or a network installation image. If the installation requires more than one CD, you must use the procedure To Upgrade a Network Installation Image From Multiple CDs.
Note - Starting with the Oracle Solaris 10 9/10 release, only a DVD is provided. Solaris Software CDs are no longer provided.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -u -n BE_name -s os_image_path
Upgrades a network installation image on a boot environment
Specifies the name of the boot environment that is to be upgraded
Specifies the path name of a directory that contains a network installation image
Example 5-1 Upgrading a Network Installation Image on a Boot Environment From DVD Media
In this example, the second_disk boot environment is upgraded by using DVD media. The pkgadd command adds the Solaris Live Upgrade packages from the release you are upgrading to.
# pkgadd -d /server/packages SUNWlucfg SUNWlur SUNWluu # luupgrade -u -n second_disk -s /cdrom/cdrom0
Example 5-2 Upgrading a Network Installation Image on a Boot Environment From a Network Installation Image
In this example, the second_disk boot environment is upgraded. The pkgadd command adds the Solaris Live Upgrade packages from the release you are upgrading to.
# pkgadd -d /server/packages SUNWlucfg SUNWlur SUNWluu # luupgrade -u -n second_disk \ -s /net/installmachine/export/Solaris_10/OS_image
Note - Starting with the Oracle Solaris 10 9/10 release, only a DVD is provided. Solaris Software CDs are no longer provided.
Because the network installation image resides on more than one CD, you must use this upgrade procedure. Use the luupgrade command with the -i option to install any additional CDs.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -u -n BE_name -s os_image_path
Upgrades a network installation image on a boot environment
Specifies the name of the boot environment that is to be upgraded
Specifies the path name of a directory that contains a network installation image
This command runs the installer on the second CD with menus.
# luupgrade -i -n BE_name -s os_image_path
This command runs the installer on the second CD with text and requires no user interaction.
# luupgrade -i -n BE_name -s os_image_path -O '-nodisplay -noconsole'
Installs additional CDs. The software looks for an installation program on the specified medium and runs that program. The installer program is specified with -s.
Specifies the name of the boot environment that is to be upgraded.
Specifies the path name of a directory that contains an network installation image.
(Optional) Runs the installer on the second CD in text mode and requires no user interaction.
The boot environment is ready to be activated. See Activating a Boot Environment.
Example 5-3 SPARC: Upgrading a Network Installation Image From Multiple CDs
In this example, the second_disk boot environment is upgraded and the installation image is on two CDs: the Solaris Software - 1 and the Solaris Software - 2 CDs. The -u option determines if sufficient space for all the packages is on the CD set. The -O option with the -nodisplay and -noconsole options prevents the character user interface from displaying after the reading of the second CD. If you use these options, you are not prompted to type information.
Note: If you do not use the -O option with the -nodisplay and -noconsole options, the character user interface (CUI) is displayed. Sun no longer recommends using the CUI to do Solaris Live Upgrade tasks.
Install the Solaris Live Upgrade packages from the release you are upgrading to.
# pkgadd -d /server/packages SUNWlucfg SUNWlur SUNWluu
Insert the Solaris Software - 1 CD and type:
# luupgrade -u -n second_disk -s /cdrom/cdrom0/
Insert the Solaris Software - 2 CD and type the following.
# luupgrade -i -n second_disk -s /cdrom/cdrom0 -O '-nodisplay \ -noconsole' Repeat this step for each CD that you need.
Repeat the previous step for each CD that you want to install.
In the following procedure, packages are removed from and added to a new boot environment.
Caution - When you are upgrading. adding and removing packages or patches, Solaris Live Upgrade requires packages or patches that comply with the SVR4 advanced packaging guidelines. While Sun packages conform to these guidelines, Sun cannot guarantee the conformance of packages from third-party vendors. If a package violates these guidelines, the package can cause the package-addition software to fail or can alter the active boot environment. For more information about packaging requirements, see Appendix B, Additional SVR4 Packaging Requirements (Reference). |
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -P -n second_disk package-name
Indicates to remove the named package or packages from the boot environment
Specifies the name of the boot environment where the package is to be removed
Specifies the names of the packages to be removed. Separate multiple package names with spaces.
# luupgrade -p -n second_disk -s /path-to-packages package-name
Indicates to add packages to the boot environment.
Specifies the name of the boot environment where the package is to be added.
Specifies the path to a directory that contains the package or packages that are to be added.
Specifies the names of the package or packages to be added. Separate multiple package names with a space.
Example 5-4 Adding packages to a Network Installation Image on a Boot Environment
In this example, packages are removed then added to the second_disk boot environment.
# luupgrade -P -n second_disk SUNWabc SUNWdef SUNWghi # luupgrade -p -n second_disk -s /net/installmachine/export/packages \ SUNWijk SUNWlmn SUNWpkr
In the following procedure, patches are removed from and added to a new boot environment.
Caution - When you are adding and removing packages or patches, Solaris Live Upgrade requires packages or patches that comply with the SVR4 advanced packaging guidelines. While Sun packages conform to these guidelines, Sun cannot guarantee the conformance of packages from third-party vendors. If a package violates these guidelines, the package can cause the package-addition software to fail or can alter the active boot environment. |
Caution - 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. For an example of upgrading and patching from the Solaris 8 to the Solaris 10 release, see Restrictions for Using Solaris Live Upgrade. |
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -T -n second_disk patch_name
Indicates to remove the named patch or patches from the boot environment.
Specifies the name of the boot environment where the patch or patches are to be removed.
Specifies the names of the patches to be removed. Separate multiple patch names with spaces.
# luupgrade -t -n second_disk -s /path-to-patches patch-name
Indicates to add patches to the boot environment.
Specifies the name of the boot environment where the patch is to be added.
Specifies the path to the directory that contains the patches that are to be added.
Specifies the names of the patch or patches that are to be added. Separate multiple patch names with a space.
Example 5-5 Adding Patches to a Network Installation Image on a Boot Environment
In this example, patches are removed then added to the second_disk boot environment .
# luupgrade -T -n second_disk 222222-01 # luupgrade -t -n second_disk -s /net/installmachine/export/packages \ 333333-01 4444444-01
The follow procedure checks the integrity of the packages installed on the new boot environment.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -C -n BE_name -O "-v" package-name
Indicates to run the pkgchk command on the named packages
Specifies the name of the boot environment where the check is to be performed
Passes the options directly to the pkgchk command
Specifies the names of the packages to be checked. Separate multiple package names with spaces. If package names are omitted, the check is done on all packages in the specified boot environment.
Specifies to run the command in verbose mode
Example 5-6 Checking the Integrity of Packages on a Boot Environment
In this example, the packages SUNWabc, SUNWdef, and SUNWghi are checked to make sure they were installed properly and are not damaged.
# luupgrade -C -n second_disk SUNWabc SUNWdef SUNWghi
You can create a JumpStart profile to use with Solaris Live Upgrade. If you are familiar with the custom JumpStart program, this is the same profile that custom JumpStart uses. The following procedures enable you to create a profile, test the profile, and install by using the luupgrade command with the -j option.
Caution - When you install the Solaris OS with a Solaris Flash archive, the archive and the installation media must contain identical OS versions. For example, if the archive is the Solaris 10 operating system and you are using DVD media, then you must use Solaris 10 DVD media to install the archive. If the OS versions do not match, the installation on the target system fails. Identical operating systems are necessary when you use the following keyword or command:
|
For more information see the following:
For creating a JumpStart profile, see Creating a Profile in Oracle Solaris 10 9/10 Installation Guide: Custom JumpStart and Advanced Installations
This procedure shows you how to create a profile for use with Solaris Live Upgrade. You can use this profile to upgrade an inactive boot environment by using the luupgrade command with the -j option.
For procedures to use this profile, see the following sections:
For an upgrade with a profile, see To Upgrade With a Profile by Using Solaris Live Upgrade.
For a Solaris Flash installation with a profile, see To Install a Solaris Flash Archive With a Profile.
Name the file descriptively. Ensure that the name of the profile reflects how you intend to use the profile to install the Solaris software on a system. For example, you might name this profile upgrade_Solaris_10.
Only the upgrade keywords in the following tables can be used in a Solaris Live Upgrade profile.
The following table lists the keywords you can use with the Install_type keyword values of upgrade or flash_install.
|
The following table lists the keywords you can use with the Install_type keyword value flash_update.
|
For a procedure to test the profile, see To Test a Profile to Be Used by Solaris Live Upgrade.
Example 5-7 Creating a Solaris Live Upgrade Profile
In this example, a profile provides the upgrade parameters. This profile is to be used to upgrade an inactive boot environment with the Solaris Live Upgrade luupgrade command and the -u and -j options. This profile adds a package and a cluster. A regional locale and additional locales are also added to the profile. If you add locales to the profile, make sure that you have created a boot environment with additional disk space.
# profile keywords profile values # ---------------- ------------------- install_type upgrade package SUNWxwman add cluster SUNWCacc add geo C_Europe locale zh_TW locale zh_TW.BIG5 locale zh_TW.UTF-8 locale zh_HK.UTF-8 locale zh_HK.BIG5HK locale zh locale zh_CN.GB18030 locale zh_CN.GBK locale zh_CN.UTF-8
Example 5-8 Creating a Solaris Live Upgrade Profile to Install a Differential Archive
The following example of a profile is to be used by Solaris Live Upgrade to install a differential archive on a clone system. Only files that are specified by the differential archive are added, deleted, or changed. The Solaris Flash archive is retrieved from an NFS server. Because the image was built by the original master system, the clone system is not checked for a valid system image. This profile is to be used with the Solaris Live Upgrade luupgrade command and the -u and -j options.
# profile keywords profile values # ---------------- ------------------- install_type flash_update archive_location nfs installserver:/export/solaris/archive/solarisarchive no_master_check
To use the luupgrade command to install the differential archive, see To Install a Solaris Flash Archive With a Profile.
After you create a profile, use the luupgrade command to test the profile. By looking at the installation output that is generated by luupgrade, you can quickly determine if a profile works as you intended.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -u -n BE_name -D -s os_image_path -j profile_path
Upgrades an operating system image on a boot environment.
Specifies the name of the boot environment that is to be upgraded.
luupgrade command uses the selected boot environment's disk configuration to test the profile options that are passed with the -j option.
Specifies the path name of a directory that contains an operating system image. This directory can be on an installation medium, such as a DVD-ROM, CD-ROM, or it can be an NFS or UFS directory.
Path to a profile that is configured for an upgrade. The profile must be in a directory on the local machine.
Example 5-9 Testing a Profile by Using Solaris Live Upgrade
In the following example, the profile is named Flash_profile. The profile is successfully tested on the inactive boot environment that is named second_disk.
# luupgrade -u -n u1b08 -D -s /net/installsvr/export/u1/combined.u1wos \ -j /var/tmp/flash_profile Validating the contents of the media /net/installsvr/export/u1/combined.u1wos. The media is a standard Solaris media. The media contains an operating system upgrade image. The media contains Solaris version 10. Locating upgrade profile template to use. Locating the operating system upgrade program. Checking for existence of previously scheduled Live Upgrade requests. Creating upgrade profile for BE second_disk. Determining packages to install or upgrade for BE second_disk. Simulating the operating system upgrade of the BE second_disk. The operating system upgrade simulation is complete. INFORMATION: var/sadm/system/data/upgrade_cleanup contains a log of the upgrade operation. INFORMATION: var/sadm/system/data/upgrade_cleanup contains a log of cleanup operations required. The Solaris upgrade of the boot environment second_disk is complete.
You can now use the profile to upgrade an inactive boot environment.
This procedure provides step-by-step instructions for upgrading an OS by using a profile.
If you want to install a Solaris Flash archive by using a profile, see To Install a Solaris Flash Archive With a Profile.
If you added locales to the profile, make sure that you have created a boot environment with additional disk space.
Caution - When you install the Solaris OS with a Solaris Flash archive, the archive and the installation media must contain identical OS versions. For example, if the archive is the Solaris 10 operating system and you are using DVD media, then you must use Solaris 10 DVD media to install the archive. If the OS versions do not match, the installation on the target system fails. Identical operating systems are necessary when you use the following keyword or command:
|
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
See To Create a Profile to be Used by Solaris Live Upgrade for a list of upgrade keywords that can be used in a Solaris Live Upgrade profile.
# luupgrade -u -n BE_name -s os_image_path -j profile_path
Upgrades an operating system image on a boot environment.
Specifies the name of the boot environment that is to be upgraded.
Specifies the path name of a directory that contains an operating system image. This directory can be on an installation medium, such as a DVD-ROM, CD-ROM, or it can be an NFS or UFS directory.
Path to a profile. The profile must be in a directory on the local machine. For information about creating a profile, see To Create a Profile to be Used by Solaris Live Upgrade.
Example 5-10 Upgrading a Boot Environment by Using a Custom JumpStart Profile
In this example, the second_disk boot environment is upgraded by using a profile. The -j option is used to access the profile. The boot environment is then ready to be activated. To create a profile, see To Create a Profile to be Used by Solaris Live Upgrade. The pkgadd command adds the Solaris Live Upgrade packages from the release you are upgrading to.
# pkgadd -d /server/packages SUNWlucfg SUNWlur SUNWluu # luupgrade -u -n second_disk \ -s /net/installmachine/export/solarisX/OS_image \ -j /var/tmp/profile
The boot environment is ready to be activated. See Activating a Boot Environment.