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 InfoScale using YUM
This topic lists the procedures that you need to follow to upgrade InfoScale using YUM. For details about yum
repository configuration, refer to the RHEL documentation.
Before you proceed, make sure to review the requirements and limitations of using this method.
See About support for InfoScale upgrade using YUM.
Note:
Perform the following procedure on each cluster node, one at a time. Arctera recommends that you update the OS and the InfoScale RPMs separately.
To upgrade InfoScale using YUM
- Configure an InfoScale repository on the node.
Create a repository file (
.repo
) under/etc/yum.repos.d
.# cat /etc/yum.repos.d/infoscale<version>.repo
Add the following contents to the repository file:
[repo-infoscale<version>] name=Repository for InfoScale infoscale<version> 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.# yum repoList
# yum updateinfo
- If applicable, perform a minor OS version upgrade as follows:
Disable the InfoScale repository.
# yum update --disablerepo=[Infoscale repo]
Update the minor OS version.
- Take one of the following courses of action depending on the InfoScale version from which you are upgrading:
Upgrades from InfoScale 7.4.1.x (mixed-version clusters are not supported)
Run the following command on any node to stop the Cluster Server (VCS) high availability daemon (HAD) across the entire cluster:
# /opt/VRTSvcs/bin/hastop -all -force
Note: Do not start HAD on any node until all the nodes have been upgraded to the new version.
Upgrades from InfoScale 7.4.2.x onwards (rolling upgrades are supported)
Run the following command on a single node at a time to forcefully stop HAD:
# /opt/VRTSvcs/bin/hastop -local -force
Alternatively, run the following commands to temporarily freeze the Cluster Volume Manager (CVM) and other service groups that contain the CVMVoldg or DiskGroup resources.
# /opt/VRTSvcs/bin/hagrp -freeze cvm
# /opt/VRTSvcs/bin/hagrp -freeze <service_group>
- Upgrade InfoScale.
Run the following command to update the required rpms:
# yum update VRTS*
- Take one of the following courses of action depending on the InfoScale version from which you are upgrading:
Upgrades from InfoScale 7.4.1.x (mixed-version clusters are not supported)
After all the nodes have been upgraded, run the following command on each node to start HAD:
# /opt/VRTSvcs/bin/hastart
Note: Do not start HAD on any node until all the nodes in the cluster have been upgraded.
Upgrades from InfoScale 7.4.2.x onwards (rolling upgrades are supported)
Start HAD, if you had stopped it earlier.
# /opt/VRTSvcs/bin/hastart
Alternatively, if applicable, unfreeze the service groups.
# /opt/VRTSvcs/bin/hagrp -unfreeze cvm
# /opt/VRTSvcs/bin/hagrp -unfreeze <service_group>
- Manually generate and install the installer scripts for the configuration:
# /opt/VRTS/install/bin/UXRT<version>/add_install_scripts
- Reboot the node as follows:
If the application service group is online on the current node, fail it over to an alternate node.
# /opt/VRTSvcs/bin/hagrp -switch <app_service_group> -to <alternate_node_name>
Stop the VCS high availability daemon locally.
# /opt/VRTSvcs/bin/hastop -local
Gracefully reboot the node.
# shutdown -r now
Note:
After upgrading InfoScale on all the cluster nodes, perform the following procedure only once from any node in the cluster.
To update the protocol versions and types definition manually
- Update the VCS protocol version.
# /opt/VRTSvcs/bin/haclus -version -update <protocol_version>
- Update the types definition.
# /opt/VRTSvcs/bin/hatrigger -updatetypes 1 <node_name> 1
- Update the CFS protocol version.
# vxupgrade -n <protocol_version> <file_system_name>
- Update the CVM protocol version.
# vxdctl upgrade
Note:
Alternatively, after upgrading InfoScale on all the cluster nodes, perform the following procedure on each cluster node, one at a time.
(Optional - InfoScale 9.0.2 onwards) To update the protocol versions and types definition using the script
- Execute the following script to update the VCS, CVM, and CFS protocol versions and the VCS types definition:
# python3 /opt/VRTS/install/yum_postupgrade.py
Note:
Perform the following procedure only once from any node in the cluster.
To update the storage component versions
- Update the disk group (DG) version.
# vxdg upgrade <disk_group_name>
- Update the file system disk group layout version (DLV).
# vxupgrade <mount_point>