Storage Foundation 7.4.2 Configuration and Upgrade Guide - Linux
- 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
- Performing post-upgrade tasks
- Optional configuration steps
- Re-joining the backup boot disk group into the current disk group
- Reverting to the backup boot disk group after an unsuccessful upgrade
- 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
- 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 rsh for Linux
Getting ready for the upgrade
Complete the following tasks before you perform the upgrade:
Review the Veritas InfoScale 7.4.2 Release Notes for any late-breaking information on upgrading your system.
Review the Veritas Technical Support website for additional information:
You can configure the Veritas Telemetry Collector while upgrading, if you have do not already have it configured. For more information, refer to the About telemetry data collection in InfoScale section in the Veritas Installation guide.
Make sure that the administrator who performs the upgrade has root access and a good knowledge of the operating system's administration.
Make sure that all users are logged off and that all major user applications are properly shut down.
Make sure that you have created a valid backup.
Ensure that you have enough file system space to upgrade. Identify where you want to copy the RPMs, for example /packages/Veritas when the root file system has enough space or /var/tmp/packages if the /var file system has enough space.
Do not put the files under /tmp, which is erased during a system restart.
Do not put the files on a file system that is inaccessible before running the upgrade script.
You can use a Veritas-supplied disc for the upgrade as long as modifications to the upgrade script are not required.
If /usr/local was originally created as a slice, modifications are required.
Comment out any application commands or processes that are known to hang if their file systems are not present in the startup scripts.
In case of RHEL 7 and SLES 12 systems, some startup scripts are located at /etc/vx/, and the startup scripts of the following services are located at:
Service name
Startup script location and file name
amf.service
/opt/VRTSamf/bin/amfgab.service
/opt/VRTSgab/gabllt.service
/opt/VRTSllt/lltvcs.service
/opt/VRTSvcs/bin/vcsvcsmm.service
/opt/VRTSvcs/rac/bin/vcsmmvxfen.service
/opt/VRTSvcs/vxfen/bin/vxfenThe remaining startup scripts for RHEL 7 and SLES 12 are located at /etc/init.d/, like all the other startup scripts for the other supported RHEL distributions.
Make sure that the current operating system supports version 7.4.2 of the product. If the operating system does not support it, plan for a staged upgrade.
Note:
Before you upgrade RHEL 7.7 OS on a virtual machine, you need to first upgrade Veritas InfoScale 7.4.2. Later upgrade RHEL 7.7 OS, else the virtual machine may go in an unstable state.
Use -ignorechecks CPI option on RHEL 7.0 to RHEL 7.6 version to successfully upgrade Veritas InfoScale product.
Schedule sufficient outage time and downtime for the upgrade and any applications that use the Veritas InfoScale products. Depending on the configuration, the outage can take several hours.
Any swap partitions not in rootdg must be commented out of /etc/fstab. If possible, swap partitions other than those on the root disk should be commented out of /etc/fstab and not mounted during the upgrade. The active swap partitions that are not in rootdg cause upgrade_start to fail.
Make sure that the file systems are clean before upgrading.
Upgrade arrays (if required).
To reliably save information on a mirrored disk, shut down the system and physically remove the mirrored disk. Removing the disk in this manner offers a failback point.
Make sure that DMP support for native stack is disabled (dmp_native_support=off). If DMP support for native stack is enabled (dmp_native_support=on), the installer may detect it and ask you to restart the system.
If you want to upgrade the application clusters that use CP server based fencing to version 6.1 and later, make sure that you first upgrade VCS or SFHA on the CP server systems to version 6.1 and later. And then, from 7.0.1 onwards, CP server supports only HTTPS based communication with its clients and IPM-based communication is no longer supported. CP server needs to be reconfigured if you upgrade the CP server with IPM-based CP server configured.
For instructions to upgrade VCS or SFHA on the CP server systems, refer to the relevant Configuration and Upgrade Guides.
More Information