InfoScale™ 9.0 Cluster Server Configuration and Upgrade Guide - Linux
- Section I. Configuring Cluster Server using the script-based installer
- I/O fencing requirements
- Preparing to configure VCS clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring VCS
- Configuring a secure cluster node by node
- Completing the VCS configuration
- Verifying and updating licenses on the system
- Configuring VCS clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Section II. Automated configuration using response files
- Performing an automated VCS configuration
- Performing an automated I/O fencing configuration using response files
- Section III. Manual configuration
- Manually configuring VCS
- Configuring LLT manually
- Configuring VCS manually
- Configuring VCS in single node mode
- Modifying the VCS configuration
- Manually configuring the 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 VCS cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Manually configuring VCS
- Section IV. Upgrading VCS
- Planning to upgrade VCS
- Performing a VCS upgrade using the installer
- Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
- Performing an online upgrade
- Performing a phased upgrade of VCS
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated VCS upgrade using response files
- Upgrading VCS using YUM
- Planning to upgrade VCS
- Section V. Adding and removing cluster nodes
- Adding a node to a single-node cluster
- Adding a node to a single-node cluster
- Adding a node to a multi-node VCS cluster
- Manually adding a node to a cluster
- Setting up the node to run in secure mode
- Configuring I/O fencing on the new node
- Adding a node using response files
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Adding a node to a single-node cluster
- Section VI. Installation reference
- Appendix A. Services and ports
- Appendix B. Configuration files
- Appendix C. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Manually configuring LLT over UDP using IPv6
- About configuring LLT over UDP multiport
- Appendix D. Configuring LLT over TCP
- Manually configuring LLT over TCP using IPv4
- Manually configuring LLT over TCP using IPv6
- Appendix E. Migrating LLT links from IPv4 to IPv6 or dual-stack
- Appendix F. 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
- Appendix G. Configuring the secure shell or the remote shell for communications
- Appendix H. Installation script options
- Appendix I. Troubleshooting VCS configuration
- Appendix J. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix K. Upgrading the Steward process
Upgrade VCS using the YUM tool
The following procedure describes how to upgrade VCS 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 VCS upgrade support using YUM.
To upgrade VCS with the yum tool
- Configure a VCS 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-VCS9.0] name=Repository for VCS 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 VCS 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 VCS 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 VCS.
Run the following command to update the VCS rpms:
# yum update VRTS*
Note:
Arctera recommends that you update the OS and the VCS 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 VCS 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 VCS upgrade using the yum tool.