Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Installation Guide: Live Upgrade and Upgrade Planning Oracle Solaris 10 8/11 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)
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 Live Upgrade
To Test a Profile to Be Used by Live Upgrade
To Upgrade With a Profile by Using Live Upgrade
Installing Flash Archives on a Boot Environment
To Install a Flash Archive on a Boot Environment
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 Live Upgrade Boot Environments (Tasks)
8. Upgrading the Oracle Solaris OS on a System With Non-Global Zones Installed
10. Live Upgrade (Command Reference)
Part II Upgrading and Migrating With Live Upgrade to a ZFS Root Pool
11. Live Upgrade and ZFS (Overview)
12. Live Upgrade for ZFS (Planning)
13. Creating a Boot Environment for ZFS Root Pools
14. Live Upgrade For ZFS With Non-Global Zones Installed
B. Additional SVR4 Packaging Requirements (Reference)
This section provides the procedure for using Live Upgrade to install Flash Archives. Installing a Flash Archive overwrites all files on the new boot environment except for shared files. Archives are stored on the following media:
HTTP server
FTP server – Use this path from the command line only
NFS server
Local file
Local tape
Local device, including DVD or CD
Note the following issues with installing and creating a Flash Archive.
|
|
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -f -n BE_name -s os_image_path -a archive
Indicates to install an operating system from a Flash Archive.
Specifies the name of the boot environment that is to be installed with an archive.
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. This OS image provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Flash Archive. The miniroot is not the image that is installed. The -a option provides the operating system image.
Path to the Flash Archive when the archive is available on the local file system. The operating system image versions that are specified with the -s option and the -a option must be identical.
Example 5-11 Installing Flash Archives on a Boot Environment
In this example, an archive is installed on the second_disk boot environment. The archive is located on the local system. The -s option provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Flash Archive. The miniroot is not the image that is installed. The -a option provides the operating system image. The operating system versions for the -s and -a options are both Oracle Solaris 10 8/11 releases. All files are overwritten on second_disk except shareable files. The pkgadd command adds the Live Upgrade packages from the release you are upgrading to.
# pkgadd -d /server/packages SUNWlucfg SUNWlur SUNWluu # luupgrade -f -n second_disk \ -s /net/installmachine/export/Solaris_10/OS_image \ -a /net/server/archive/10
The boot environment is ready to be activated. See Activating a Boot Environment.
This procedure provides the steps to install a Flash Archive or differential archive by using a profile.
If you added locales to the profile, make sure that you have created a boot environment with additional disk space.
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 Live Upgrade for a list of keywords that can be used in a Live Upgrade profile.
# luupgrade -f -n BE_name -s os_image_path -j profile_path
Indicates to install an operating system from a Flash Archive.
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. This OS image provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Flash Archive. The miniroot is not the image that is installed. The -j option provides the path to the profile that contains the Flash Archive operating system image.
Path to a JumpStart profile that is configured for a flash installation. The profile must be in a directory on the local machine. The -s option's operating system version and the Flash Archive operating system version must be identical.
The boot environment is ready to be activated. See Activating a Boot Environment.
Example 5-12 Install a Flash Archive on a Boot Environment With a Profile
In this example, a profile provides the location of the archive to be installed.
# profile keywords profile values # ---------------- ------------------- install_type flash_install archive_location nfs installserver:/export/solaris/flasharchive/solarisarchive
After creating the profile, you can run the luupgrade command and install the archive. The -s option provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Flash Archive. The miniroot is not the image that is installed. The -j option provides the path to the profile that contains the path to the Flash Archive operating system image. The -j option is used to access the profile. The pkgadd command adds the Live Upgrade packages from the release you are upgrading to.
# pkgadd -d /server/packages SUNWlucfg SUNWlur SUNWluu # luupgrade -f -n second_disk \ -s /net/installmachine/export/solarisX/OS_image \ -j /var/tmp/profile
The boot environment is then ready to be activated. See Activating a Boot Environment.
To create a profile, see To Create a Profile to be Used by Live Upgrade.
This procedure enables you to install a Flash Archive and use the archive_location keyword at the command line rather than from a profile file. You can quickly retrieve an archive without the use of a profile file.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# luupgrade -f -n BE_name -s os_image_path -J 'archive_location path-to-profile'
Specifies to upgrade an operating system from a Flash Archive.
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. This OS image provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Flash Archive. The miniroot is not the image that is installed. The -j option provides the path to the profile that contains the Flash Archive operating system image.
Specifies the archive_location profile keyword and the path to the JumpStart profile. The -s option's operating system version and the Flash Archive operating system version must be identical. For the keyword values, see archive_location Keyword in Oracle Solaris 10 8/11 Installation Guide: Custom JumpStart and Advanced Installations.
The boot environment is ready to be activated. See Activating a Boot Environment.
Example 5-13 Installing a Flash Archive By Using a Profile Keyword
In this example, an archive is installed on the second_disk boot environment. The -s option provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Flash Archive. The miniroot is not the image that is installed. The -j option provides the path to the Flash Archive operating system image. The -J option and the archive_location keywords are used to retrieve the archive. All files are overwritten on second_disk except shareable files. The pkgadd command adds the Live Upgrade packages from the release you are upgrading to.
# pkgadd -d /server/packages SUNWlucfg SUNWlur SUNWluu # luupgrade -f -n second_disk \ -s /net/installmachine/export/solarisX/OS_image \ -J 'archive_location http://example.com/myflash.flar'