InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Solaris
- Section I. Introduction to SFHA
- Section II. Configuration of SFHA
- Preparing to configure
- Preparing to configure SFHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring CP server using response files
- Configuring SFHA
- Configuring Storage Foundation High Availability using the installer
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring Storage Foundation High Availability using the installer
- Configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Manually configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing manually
- Setting up server-based I/O fencing manually
- Configuring server-based fencing on the SFHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Performing an automated SFHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Section III. Upgrade of SFHA
- Planning to upgrade SFHA
- Preparing to upgrade SFHA
- Upgrading Storage Foundation and High Availability
- Performing a rolling upgrade of SFHA
- Performing a phased upgrade of SFHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFHA upgrade using response files
- Upgrading SFHA using Boot Environment upgrade
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- Upgrading the Array Support Library
- About enabling LDAP authentication for clusters that run in secure mode
- Planning to upgrade SFHA
- Section IV. Post-installation tasks
- Section V. Adding and removing nodes
- Adding a node to SFHA clusters
- Adding the node to a cluster manually
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFHA clusters
- Removing a node from a SFHA cluster
- Removing a node from a SFHA cluster
- Adding a node to SFHA clusters
- Section VI. Configuration and upgrade reference
- Appendix A. Installation scripts
- Appendix B. SFHA services and ports
- Appendix C. Configuration files
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. Sample SFHA cluster setup diagrams for CP server-based I/O fencing
- Appendix F. Reconciling major/minor numbers for NFS shared disks
- Appendix G. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
Upgrading SFHA using the installer for upgrading BE on Solaris 11
You can use the Arctera InfoScale product installer to upgrade SFHA on a BE.
On a node in the cluster, run the installer on the primary boot disk to upgrade SFHA on all the nodes in the cluster.
At the end of the process, the Storage Foundation and High Availability 9.0 is installed on the alternate BE.
To perform BE upgrade of SFHA using the installer
- Insert the product disc with Storage Foundation and High Availability 9.0 or access your copy of the software on the network.
- Run the installer script specifying the root path as the alternate BE:
# ./installer -upgrade -rootpath /altroot.7.3
- Enter the names of the nodes that you want to upgrade to Storage Foundation and High Availability 9.0.
The installer displays the list of packages to be installed or upgraded on the nodes.
- Press Return to continue with the installation.
During BE upgrade, if the OS of the alternate BE is upgraded, the installer does not update the VCS configurations for Oracle, Netlsnr, and Sybase resources. If cluster configurations include these resources, you are prompted to run a list of commands to manually update the configurations after the cluster restarts from the alternate BE.
- Verify that the version of the VCS packages on the alternate BE is 9.0.
# pkg -R /altroot.7.3 list VRTS\*
Review the installation logs at
/altroot.7.3/opt/VRTS/install/logs
.