Storage Foundation 7.2 Configuration and Upgrade Guide - Solaris
- Section I. Introduction and configuration of Storage Foundation
- Section II. Upgrade of Storage Foundation
- Planning to upgrade Storage Foundation
- About the upgrade
- Supported upgrade paths
- Preparing to upgrade SF
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Upgrading Storage Foundation
- Performing an automated SF upgrade using response files
- Upgrading SF using Boot Environment upgrade
- Performing post-upgrade tasks
- Optional configuration steps
- Recovering VVR if automatic upgrade fails
- Resetting DAS disk names to include host name in FSS environments
- Upgrading disk layout versions
- Upgrading VxVM disk group versions
- Updating variables
- Setting the default disk group
- Upgrading the Array Support Library
- Converting from QuickLog to Multi-Volume support
- Verifying the Storage Foundation upgrade
- Planning to upgrade Storage Foundation
- Section III. Post configuration tasks
- Section IV. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling and disabling rsh for Solaris
Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
Beginning with version 6.1, you can easily install or upgrade your systems directly to a base, maintenance, patch level or a combination of multiple patches and packages together in one step using Install Bundles. With Install Bundles, the installer has the ability to merge so that customers can install or upgrade directly to maintenance or patch levels in one execution. The various scripts, packages, and patch components are merged, and multiple releases are installed together as if they are one combined release. You do not have to perform two or more install actions to install or upgrade systems to maintenance levels or patch levels.
Releases are divided into the following categories:
Table: Release Levels
Level | Content | Form factor | Applies to | Release types | Download location |
|---|---|---|---|---|---|
Base | Features | packages | All products | Major, minor, Service Pack (SP), Platform Release (PR) | FileConnect |
Maintenance | Fixes, new features | packages | All products | Maintenance Release (MR), Rolling Patch (RP) | Veritas Services and Operations Readiness Tools (SORT) |
Patch | Fixes | packages | Single product | P-Patch, Private Patch, Public patch | SORT, Support site |
When you install or upgrade using Install Bundles:
Veritas InfoScale products are discovered and assigned as a single version to the maintenance level. Each system can also have one or more patches applied.
Base releases are accessible from FileConnect that requires customer serial numbers. Maintenance and patch releases can be automatically downloaded from SORT.
Patches can be installed using automated installers from the 6.0.1 version or later.
Patches can now be detected to prevent upgrade conflict. Patch releases are not offered as a combined release. They are only available from Veritas Technical Support on a need basis.
You can use the -base_path and -patch_path options to import installation code from multiple releases. You can find packages and patches from different media paths, and merge package and patch definitions for multiple releases. You can use these options to use new task and phase functionality to correctly perform required operations for each release component. You can install the packages and patches in defined phases using these options, which helps you when you want to perform a single start or stop process and perform pre and post operations for all level in a single operation.
Four possible methods of integration exist. All commands must be executed from the highest base or maintenance level install script.
In the example below:
7.2 is the base version
7.2.1 is the maintenance version
7.2.1.100 is the patch version for 7.2.1
7.2.0.100 is the patch version for 7.2
Base + maintenance:
This integration method can be used when you install or upgrade from a lower version to 7.2.1.
Enter the following command:
# installmr -base_path <path_to_base>
Base + patch:
This integration method can be used when you install or upgrade from a lower version to 7.2.0.100.
Enter the following command:
# installer -patch_path <path_to_patch>
Maintenance + patch:
This integration method can be used when you upgrade from version 7.2 to 7.2.1.100.
Enter the following command:
# installmr -patch_path <path_to_patch>
Base + maintenance + patch:
This integration method can be used when you install or upgrade from a lower version to 7.2.1.100.
Enter the following command:
# installmr -base_path <path_to_base> -patch_path <path_to_patch>
Note:
From the 6.1 or later release, you can add a maximum of five patches using -patch_path <path_to_patch> -patch2_path <path_to_patch> ... -patch5_path <path_to_patch>