InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Linux
- 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
- Completing the SFHA configuration
- 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 YUM
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- 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. 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
- About configuring LLT over UDP multiport
- Appendix G. Using LLT over RDMA
- Configuring LLT over RDMA
- Configuring RDMA over an Ethernet network
- Configuring RDMA over an InfiniBand network
- Tuning system performance
- Manually configuring LLT over RDMA
- Troubleshooting LLT over RDMA
Upgrade SFHA using the YUM tool
The following procedure describes how to upgrade SFHA using the yum tool. Refer to the Red Hat Enterprise Linux documentation for more information about yum repository configuration.
Before you proceed, ensure that you review the limitations of using this process.
See About SFHA upgrade support using YUM.
To upgrade SFHA with the yum tool
- Configure a SFHA repository on a node.
Create a repository file (
.repo
) under/etc/yum.repos.d
.Run the following command:
# cat /etc/yum.repos.d/infoscale90.repo
Add the following contents to the repository file:
[repo-SFHA9.0] name=Repository for SFHA 9.0 baseurl=file:///<image_dir>/rpms/ enabled=1 gpgcheck=1 gpgkey=file:///<image_dir>/rpms/RPM-GPG-KEY-veritas-infoscale
The values for the
baseurl
attribute can start with http://, ftp://, or file:///. The URL you choose should be able to access the repodata directory. It also needs to access all the SFHA RPMs in the repository that you create or update.Save the changes and exit the file editor.
Update the yum repository.
Run the following commands:
# yum repoList
# yum updateinfo
- If applicable, perform a minor OS version upgrade as follows:
Disable the SFHA repo.
Run the following command:
# yum update --disablerepo=[Infoscale repo]
Update the operating system minor version.
- Temporarily freeze the Cluster Volume Manager (CVM) and other service groups that contain the CVMVoldg or DiskGroup resources, or forcefully stop the Cluster Server (VCS) high availability daemon
HAD
.Run the following commands:
# /opt/VRTSvcs/bin/hagrp -freeze cvm
# /opt/VRTSvcs/bin/hagrp -freeze <service_group>
Or,
# /opt/VRTSvcs/bin/hastop -local -force
- Upgrade SFHA.
Run the following command to update the SFHA rpms:
# yum update VRTS*
Note:
Arctera recommends that you update the OS and the SFHA rpms separately.
- Unfreeze the service groups or start
HAD
, if you had stopped the daemon earlier in step 3.Run the following commands:
# /opt/VRTSvcs/bin/hagrp -unfreeze cvm
# /opt/VRTSvcs/bin/hagrp -unfreeze <service_group>
Or,
# /opt/VRTSvcs/bin/hastart
- Run the following command to manually generate and install the installer scripts for configuration:
# /opt/VRTS/install/bin/UXRT9.0/add_install_scripts
- Reboot the cluster nodes, one node at a time.
Do the following:
Before you reboot a node, ensure that you fail over the application service group to an alternative cluster node.
Run the following commands on the node you want to reboot:
# /opt/VRTSvcs/bin/hagrp -switch <app_service_group> -to <alternate_node_name>
Stop the VCS high availability daemon (
HAD
) locally on the node.Run the following command:
# /opt/VRTSvcs/bin/hastop -local
Gracefully reboot that node.
Run the following command:
# shutdown -r now
Repeat these steps on each subsequent node.
- Repeat steps 1 to 7 on each SFHA cluster node, one node at a time.
- After all the nodes are upgraded, update the Cluster Server (VCS) protocol version from any one node in the cluster.
Run the following command:
# /opt/VRTSvcs/bin/haclus -version -update 9.0.0.0000
- Update the type definition from any one node in the cluster.
Run the following command:
# /opt/VRTSvcs/bin/hatrigger -updatetypes 1 <node_name> 1
- Update the CVM protocol version, the disk group version, and the file system disk group layout version (DLV).
Run the following commands:
# vxdctl upgrade
# vxdg upgrade <diskgroup>
# vxupgrade <mount_point>
This process completes the SFHA upgrade using the yum tool.