InfoScale™ 9.0 Storage Foundation for Oracle® RAC Configuration and Upgrade Guide - Linux
- Section I. Configuring SF Oracle RAC
- Preparing to configure SF Oracle RAC
- Configuring SF Oracle RAC using the script-based installer
- Configuring the SF Oracle RAC components using the script-based installer
- Configuring the SF Oracle RAC cluster
- Configuring SF Oracle RAC in secure mode
- Configuring a secure cluster node by node
- Configuring the SF Oracle RAC cluster
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Configuring the SF Oracle RAC components using the script-based installer
- Performing an automated SF Oracle RAC configuration
- Section II. Post-installation and configuration tasks
- Verifying the installation
- Performing additional post-installation and configuration tasks
- Section III. Upgrade of SF Oracle RAC
- Planning to upgrade SF Oracle RAC
- Performing a full upgrade of SF Oracle RAC using the product installer
- Performing an automated full upgrade of SF Oracle RAC using response files
- Performing a phased upgrade of SF Oracle RAC
- Performing a phased upgrade of SF Oracle RAC from version 7.4.1 and later release
- Performing a rolling upgrade of SF Oracle RAC
- Upgrading SF Oracle RAC using YUM
- Upgrading Volume Replicator
- Performing post-upgrade tasks
- Section IV. Installation of Oracle RAC
- Before installing Oracle RAC
- Preparing to install Oracle RAC using the SF Oracle RAC installer or manually
- Creating users and groups for Oracle RAC
- Creating storage for OCR and voting disk
- Configuring private IP addresses for Oracle RAC
- Installing Oracle RAC
- Performing an automated Oracle RAC installation
- Performing Oracle RAC post-installation tasks
- Configuring the CSSD resource
- Relinking the SF Oracle RAC libraries with Oracle RAC
- Configuring VCS service groups for Oracle RAC
- Upgrading Oracle RAC
- Before installing Oracle RAC
- Section V. Adding and removing nodes
- Adding a node to SF Oracle RAC clusters
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Configuring server-based fencing on the new node
- Preparing the new node manually for installing Oracle RAC
- Adding a node to the cluster using the SF Oracle RAC response file
- Configuring private IP addresses for Oracle RAC on the new node
- Removing a node from SF Oracle RAC clusters
- Adding a node to SF Oracle RAC clusters
- Section VI. Configuration of disaster recovery environments
- Configuring disaster recovery environments
- Configuring disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- Appendix C. Sample installation and configuration values
- SF Oracle RAC worksheet
- Appendix D. Configuration files
- Sample configuration files
- Sample configuration files for CP server
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. Automatic Storage Management
- Appendix G. Creating a test database
- Appendix H. High availability agent information
- About agents
- CVMCluster agent
- CVMVxconfigd agent
- CVMVolDg agent
- CFSMount agent
- CFSfsckd agent
- CSSD agent
- VCS agents for Oracle
- Oracle agent functions
- Resource type definition for the Oracle agent
- Resource type definition for the Netlsnr agent
- Resource type definition for the ASMDG agent
- Oracle agent functions
- CRSResource agent
- Appendix I. SF Oracle RAC deployment scenarios
- Appendix J. 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 K. 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 SF Oracle RAC 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>