Installing Solaris Flash Archives on a Boot Environment

This section provides the procedure for using Solaris Live Upgrade to install Solaris Flash archives. Installing a Solaris 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 Solaris Flash archive.

Description Example Caution - When you install the Solaris OS with a Solaris Flash archive, the archive and the installation media must contain identical OS versions. 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: archive_location keyword in a profile luupgrade command with -s, -a, -j, and -J options 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. Caution - A Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not compatible with the Solaris Zones feature. If you create a Solaris Flash archive in a non-global zone or create an archive in a global zone that has non-global zones installed, the resulting archive does not install properly when the archive is deployed.

To Install a Solaris Flash Archive on a Boot Environment

1. Install the Solaris Live Upgrade SUNWlucfg, SUNWlur, and SUNWluu packages on your system. These packages must be from the release you are upgrading to. For step-by-step procedures, see To Install Solaris Live Upgrade With the pkgadd Command.
2. Become superuser or assume an equivalent role.

   Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

3. Type:

   # luupgrade -f -n BE_name -s os_image_path -a archive

   -f

   Indicates to install an operating system from a Solaris Flash archive.

   -n BE_name

   Specifies the name of the boot environment that is to be installed with an archive.

   -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. This OS image provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Solaris Flash archive. The miniroot is not the image that is installed. The -a option provides the operating system image.

   -a archive

   Path to the Solaris 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 Solaris 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 Solaris 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 Solaris 10 9/10 releases. All files are overwritten on second_disk except shareable files. The pkgadd command adds the Solaris 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.

To Install a Solaris Flash Archive With a Profile

This procedure provides the steps to install a Solaris 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.

1. Install the Solaris Live Upgrade SUNWlucfg, SUNWlur, and SUNWluu packages on your system. These packages must be from the release you are upgrading to. For step-by-step procedures, see To Install Solaris Live Upgrade With the pkgadd Command.
2. Become superuser or assume an equivalent role.

   Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

3. Create a profile.

   See To Create a Profile to be Used by Solaris Live Upgrade for a list of keywords that can be used in a Solaris Live Upgrade profile.

4. Type:

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

   -f

   Indicates to install an operating system from a Solaris Flash archive.

   -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. This OS image provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Solaris Flash archive. The miniroot is not the image that is installed. The -j option provides the path to the profile that contains the Solaris Flash archive operating system image.

   -j profile_path

   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 Solaris 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 Solaris 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 Solaris 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 Solaris Flash archive operating system image. The -j option is used to access the profile. The pkgadd command adds the Solaris 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 Solaris Live Upgrade.

To Install a Solaris Flash Archive With a Profile Keyword

This procedure enables you to install a Solaris 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.

1. Install the Solaris Live Upgrade SUNWlucfg, SUNWlur, and SUNWluu packages on your system. These packages must be from the release you are upgrading to. For step-by-step procedures, see To Install Solaris Live Upgrade With the pkgadd Command.
2. Become superuser or assume an equivalent role.

   Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

3. Type:

   # luupgrade -f -n BE_name -s os_image_path -J 'archive_location path-to-profile'

   -f

   Specifies to upgrade an operating system from a Solaris Flash archive.

   -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. This OS image provides a miniroot that boots a minimal, bootable root (/) file system to facilitate the installation of the Solaris Flash archive. The miniroot is not the image that is installed. The -j option provides the path to the profile that contains the Solaris Flash archive operating system image.

   -J 'archive_location path-to-profile'

   Specifies the archive_location profile keyword and the path to the JumpStart profile. The -s option's operating system version and the Solaris Flash archive operating system version must be identical. For the keyword values, see archive_location Keyword in Oracle Solaris 10 9/10 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 Solaris 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 Solaris Flash archive. The miniroot is not the image that is installed. The -j option provides the path to the Solaris 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 Solaris 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'