test

Solaris 9 Installation Guide

Upgrading a Boot Environment

Use the Upgrade menu or 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:

When you upgrade a boot environment with the latest operating environment, 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.

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 the inactive boot environment critical file systems, but shareable file systems are not changed. See “Installing Solaris Flash Archives on a Boot Environment”.

Upgrading Metadevices and Volumes

To upgrade or install an archive on a new boot environment, the device must be a physical slice. If you have a boot environment that has a file system that is mounted either on a Solaris Volume Manager metadevice or a Veritas file system (VxFS) volume, the upgrade or installation of an archive fails. To upgrade or install an archive on such a boot environment, you must manually change the boot environment so that all slices are physical disk slices. You could use the lucreate command to create another boot environment or you could break the metadevices or volumes.

To use the lucreate command to make a copy of the boot environment, you would place the boot environment copy on physical disk slices. For example, suppose your current boot environment's disk configuration contains the following volumes and slices.

root (/)

Mounted on /dev/md/dsk/d10 

/usr

Mounted on /dev/md/dsk/d20 

/var

Mounted on /dev/dsk/c0t3d0s0 

Free slice 

c0t4d0s0 

Free slice 

c0t4d0s3 

Free slice 

c0t4d0s4 

You could then use the following lucreate command to copy the boot environment on physical disk slices. The boot environment could then be upgraded or be installed with an archive. In this example, the current boot environment is named currentBE, and the new boot environment is named nextBE.


# lucreate -s currentBE -n nextBE -m /:/dev/dsk/c0t4d0s0:ufs \
-m /usr:/dev/dsk/c0t4d0s3:ufs -m /var:/dev/dsk/c0t4d0s4:ufs

You would then be able to upgrade or install a archive on the new boot environment, activate it, and then re-mirror or encapsulate it manually.

If you choose to manually break the metadevice or volume, you would need to do the following:

The boot environment could then be upgraded or be installed with an archive.

Managing Packages and Patches With Solaris Live Upgrade

You can use Solaris Live Upgrade to add patches and packages to a system. As with upgrading a machine, by using Live Upgrade to add patches to a machine, the only downtime the system incurs is that of a reboot. You can add patches and packages directly to a boot environment with the luupgrade command. Or, you can apply patches and packages to a master system and apply a Solaris Flash archive of that system to a boot environment by using Live Upgrade.

To add patches to a boot environment directly, create a new boot environment and use the luupgrade command with the -t option. To add packages to a boot environment, use the luupgrade command with the -p option. For more information, see the man page, luupgrade(1M).

Or, you can use Solaris Live Upgrade to install a Solaris Flash archive that contains a complete copy of a boot environment with new packages and patches already included. This complete boot environment or single reference system is called a master system. The process of creating a Solaris Flash archive begins with creating a master system. After you have created a master system, add any patches and packages that you want to install. Then, create a Solaris Flash archive of the master system. Use Solaris Live Upgrade to install the archive on the new boot environment. You can copy the boot environment, change it, and distribute it as many times as necessary. For details about how to create a Solaris Flash archive, see Chapter 18, Creating Solaris Flash Archives (Tasks). For information on using Solaris Live Upgrade to install a Solaris Flash archive, see “Installing Solaris Flash Archives on a Boot Environment”.

Caution - Caution -

When upgrading and 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. A non-conformant package can cause the package-addition software during an upgrade to fail or worse, to alter the active boot environment.

For more information on adding and removing packages with Solaris Live Upgrade, see the man page, luupgrade(1M). For more information on packaging requirements, see Appendix C, Additional SVR4 Packaging Requirements (Reference).

To Upgrade an Operating System Image on a Boot Environment (Character Interface)

To upgrade by using this procedure, you must use only one CD, a DVD, or a combined installation image. For an installation that requires more than one CD, you must use the procedure: “To Upgrade an Operating System Image From Multiple CDs (Command-Line Interface)”.

  1. From the Solaris Live Upgrade main menu, select Upgrade.

    The Upgrade menu screen is displayed.

  2. Type the new boot environment's name.

  3. Type the path to where the Solaris installation image is located.

    Installation Media Type 

    Description 

    Network File System 

    Specify the path to the network file system where the installation image is located.  

    Local file 

    Specify the path to the local file system where the installation image is located. 

    Local tape 

    Specify the local tape device and the position on the tape where the installation image is located. 

    Local device, DVD, or CD 

    Specify the local device and the path to the installation image. 

    • If you are using DVD or one CD, type the path to that disc, as in this example:


      Package Media: /cdrom/solaris9/s0

    • If you have a combined image on the network, type the path to the network file system as in this example:


      Package Media: /net/installmachine/export/solaris9/os_image

  4. To upgrade, press F3.

  5. When the upgrade is completed, the main menu is displayed.

To Upgrade an Operating System Image on a Boot Environment (Command-Line Interface)

To upgrade by using this procedure, you must use only one CD, a DVD, or a combined installation image. If the installation requires more than one CD, you must use the procedure: “To Upgrade an Operating System Image From Multiple CDs (Command-Line Interface)”.

  1. Log in as superuser.

  2. Indicate the boot environment to upgrade and the path to the installation software by typing:


    # luupgrade -u -n BE_name -s os_image_path

    -u

    Upgrades an operating system image on a boot environment 

    -n BE_name

    Specifies the name of the boot environment that is to be upgraded 

    -s os_image_path

    Specifies the path name of a directory that contains an operating system image 

    Example 33-1 Upgrading an Operating System Image on a Boot Environment (Command-Line Interface)

    In this example, the second_disk boot environment is upgraded.


    # luupgrade -u -n second_disk \
-s /net/installmachine/export/solaris9/OS_image

To Upgrade an Operating System Image From Multiple CDs (Command-Line Interface)

If the operating system image resides on two or more CDs, use this upgrade procedure.

  1. Log in as superuser.

  2. Indicate the boot environment to upgrade and the path to the installation software by typing:


    # luupgrade -u -n BE_name -s os_image_path

    -u

    Upgrades an operating system image on a boot environment 

    -n BE_name

    Specifies the name of the boot environment that is to be upgraded 

    -s os_image_path

    Specifies the path name of a directory that contains an operating system image 

  3. When the installer is finished with the contents of the first CD, insert the second CD.

  4. This step is identical to the previous step, but the -u option is replaced by the -i option. Also, choose to run the installer on the second CD with menus or with text.

    • 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'

    -i

    Looks for an installation program on the specified medium and runs that program. The installer program is specified with -s.

    -n BE_name

    Specifies the name of the boot environment that is to be upgraded. 

    -s os_image_path

    Specifies the path name of a directory that contains an operating system image. 

    -O '-nodisplay -noconsole'

    (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 33-2 SPARC: Upgrading an Operating System Image From Multiple CDs (Command-Line Interface)

    In this example, the second_disk boot environment is upgraded and the installation image is on two CDs: the Solaris 9 Software 1 of 2 and the Solaris 9 Software 2 of 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 input information. Omit these options to display the interface.

    Insert the Solaris 9 Software 1 of 2 CD and type:


    # luupgrade -u -n second_disk -s /dev/cdrom/cdrom0/s0

    Insert the Solaris 9 Software 2 of 2 CD and type:


    # luupgrade -i -n second_disk -s /dev/cdrom/cdrom0 -O '-nodisplay \
-noconsole'
    Note -

    Use the luupgrade command with the -i option to install any additional CDs.

To Create a Profile to be Used by Solaris Live Upgrade

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:

  1. Use a text editor to create a text file.

    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_solaris9.

  2. Add profile keywords and values to the profile.

    Only the following upgrade keywords can be used in a Solaris Live Upgrade profile.

    Table 33-2 Live Upgrade Profile Keywords and Descriptions

    Keyword 

    Description 

    (Required) Install_type

    Defines whether to upgrade the existing Solaris environment on a system or install a Solaris Flash archive on the system. The values are upgrade or flash_install.

    (Optional) archive_location

    Retrieves a Solaris Flash archive from a designated location. For a list of values that can be used with this keyword, see “archive_location Keyword”.

    (Optional) cluster (adding or deleting clusters)

    Designates whether a cluster is to be added or deleted from the software group that is to be installed on the system. For a list of values that can be used with this keyword, see “cluster Profile Keyword (Adding Software Groups)”.

    (Optional) geo

    Designates the regional locale or locales that you want to install on a system or to add when upgrading a system. For a list of values that can be used with this keyword, see “geo Profile Keyword”.

    (Optional) isa_bits

    Specifies whether 64-bit or 32-bit Solaris 9 packages are to be installed. For a list of values that can be used with this keyword, see “isa_bits Profile Keyword”.

    (Optional) locale

    Designates the locale packages you want to install or add when upgrading. For a list of values that can be used with this keyword, see “locale Profile Keyword”.

    (Optional) package

    Designates whether a package is to be added to or deleted from the software group that is to be installed on the system. For a list of values that can be used with this keyword, see “package Profile Keyword”.

  3. Save the profile in a directory on the local system.

  4. Ensure that root owns the profile and that the permissions are set to 644.

  5. Test the profile (optional).

    For a procedure to test the profile, see “To Test a Profile to Be Used By Solaris Live Upgrade”.

Example 33-3 Creating a Profile to Be Used With Solaris Live Upgrade

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

To Test a Profile to Be Used By Solaris Live Upgrade

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.

  1. Test the profile.


    # luupgrade -u -n BE_name -D -s os_image_path -j profile_path

    -u

    Upgrades an operating system image on a boot environment. 

    -n BE_name

    Specifies the name of the boot environment that is to be upgraded. 

    -D

    luupgrade command uses the selected boot environment's disk configuration to test the profile options passed with the -j option.

    -s os_image_path

    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. 

    -j profile_path

    Path to a profile that is configured for an upgrade. The profile must be in a directory on the local machine. 

Example 33-4 Testing a Profile by Using Solaris Live Upgrade

In the following example, the profile is named upgrade_solaris9, The profile is successfully tested on the inactive boot environment named, s9u1b08. 


# luupgrade -u -n s9u1b08 -D -s /net/installsvr/export/s9u1/combined.s9s_u1wos \
 -j /var/tmp/flash_profile
Validating the contents of the media /net/installsvr/export/s9u1/combined.s9s_u1wos.
The media is a standard Solaris media.
The media contains an operating system upgrade image.
The media contains Solaris version 9.
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 s9u1b08.
Determining packages to install or upgrade for BE s9u1b08.
Simulating the operating system upgrade of the BE s9u1b08.
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 s9u1b08 is complete.

You can now use the profile to upgrade an inactive boot environment.

To Upgrade With a Profile by Using Solaris Live Upgrade (Command-Line Interface)

This procedure provides step-by-step instructions for upgrading a operating environment 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 (Command-Line Interface)”.

If you added locales to the profile, make sure that you have created a boot environment with additional disk space.

  1. Log in as superuser.

  2. Create a profile.

    See Table 33–2 for a list of upgrade keywords that can be used in a Solaris Live Upgrade profile.

  3. Type:


    # luupgrade -u -n BE_name -s os_image_path -j profile_path

    -u

    Upgrades an operating system image on a boot environment 

    -n BE_name

    Specifies the name of the boot environment that is to be upgraded. 

    -s os_image_path

    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. 

    -j profile_path

    Path to a profile. The profile must be in a directory on the local machine. For information on creating a profile, see “To Create a Profile to be Used by Solaris Live Upgrade”.

    The boot environment is ready to be activated.

    Example 33-5 Upgrading a Boot Environment By Using a Custom JumpStart Profile (Command-Line Interface)

    In this example, an archive is installed on the second_disk boot environment. 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”.


    # luupgrade -u -n second_disk \
-s /net/installmachine/export/solarisX/OS_image \
-j /var/tmp/profile