Veritas InfoScale™ 8.0.2 Installation Guide - Linux
- Section I. Planning and preparation
- Introducing Veritas InfoScale
- Licensing Veritas InfoScale
- System requirements
- Preparing to install
- Setting up the private network
- Setting up shared storage
- Planning the installation setup for SF Oracle RAC systems
- Preparing for deployment in a Secure Boot environment
- Section II. Installation of Veritas InfoScale
- Installing Veritas InfoScale using the installer
- Installing Veritas InfoScale using response files
- Installing Veritas Infoscale using operating system-specific methods
- Completing the post installation tasks
- Section III. Uninstallation of Veritas InfoScale
- Section IV. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- Appendix C. Troubleshooting installation issues
- Appendix D. Managing InfoScale digital signatures (Secure Boot environment)
Installing or upgrading Veritas InfoScale using the installer with the -yum option
Starting with InfoScale 8.0, you can use yum commands with Common Product Installer and install or upgrade InfoScale 8.0 running on Red Hat and Oracle Linux.
Yum is a command-line package management tool that you can use for installing, updating, removing, and managing the InfoScale package. Yum performs dependency resolution when install, update, and remove the InfoScale package. Yum can also manage the package from installed repositories in the system or from the InfoScale .rpm packages. The following new options are supported for the installation and upgrade of InfoScale:
-yum
-matrixpath
-upgradestart
-upgradestop
Note:
The new installer options are supported only with InfoScale 8.0. You can perform upgrades from an earlier version to 8.0.2. The supported versions for upgrades are 7.4.1, 7.4.2, and 8.0.
Before you begin
Before you begin the configuration of yum, and installation or upgrade of InfoScale, ensure that you:
Deploy InfoScale in a development or UAT environment first, which is as similar to your production environment as possible. Perform tests in that environment and ensure that there is no incompatibility with your current deployment.
Perform necessary backups and snapshots of your production system and establish a rollback plan.
Installation or upgrade
There are two ways of yum based installation or upgrade. You can either use the -yum option with installer, or use direct/manual yum method.
Using the yum option with installer
The following is the syntax and examples for installing InfoScale using the yum installer option. After running any of the following yum installation commands, select the
or option from the menu displays by installer script.Syntax:
./installer -yum [repo_name | repo_url]
Example for yum installation with repository name:
./installer -yum repo-Infoscale802
Example for yum installation using repository URL:
./installer -yum http://xyz.com/rhel8_x86_64/rpms/
Notes:
If a repository URL is passed as an argument with the -yum option, you do not need to set the yum repository manually. The CPI installer creates the repository on each node. The repository URL is the base URL that you specify in the repository file while configuring yum repository, and the values for the base URL attribute begins with http://, ftp:/, file:///, or sftp:/
If a repository name is passed as an argument with the -yum option, the CPI installer assumes that the repository is already configured and enabled on the node, hence, you need not to configure the repository. If a repository name is used and the repository has not yet been configured, then the CPI installer exits with an appropriate error.
Using -yum and -patch_path options together with -matrixpath
The following is the syntax and examples for performing patch installation or patch upgrade along with GA upgrade of InfoScale with RPM files:
Note:
After running any of the following yum installation commands, select the Install a product or upgrade a product option from the menu displayed by installer script.
Syntax:
./installer -yum [repo_name | repo_url] -patch_path [repo_name | repo_url] -matrixpath
Example for performing patch installation or patch upgrade
./installer -yum repo-Infoscale802 -patch_path repo-Infoscale802P -matrixpath /root/patch_matrix
When you run this command, you need to enter the release matrix data path in the command. You must use the matrixpath option when there is no SORT connectivity on a machine and the -yum and -patch_path options are used together. As installer has pre-checks on the release matrix data, if a correct release matrix data path is not provided, the patch installation or patch upgrade may fail.
Direct or manual yum installation
Ensure that you set the yum repository manually on each node of the cluster before running the yum install command.
For more details on Installing Veritas InfoScale using yum, refer to the topic:
To install InfoScale RPMs using manual yum method
- Specify each RPM name and its yum equivalent. For example: # yum install VRTSvlic VRTSperl ... VRTSsfcpi
- Specify all the Veritas InfoScale RPMs using RPM glob. For example: # yum install 'VRTS*'
- Specify the group name if a group is configured for Veritas InfoScale's RPMs.
Note:
Ensure that the specified name is consistent with the one in the xml file. For example, consider the group name usage as ENTERPRISE802: # yum install @ENTERPRISE802 or # yum groupinstall -y ENTERPRISE802.
Using Direct or manual yum upgrade
You can upgrade InfoScale by manually configuring yum repositories on each node of a cluster, and then run the yum upgrade command. You need to use the upgradestop and upgradestart options for manual yum upgrade. The following are the syntax and examples:
Syntax for upgradestop:
/opt/VRTS/install/installer -upgradestop
Use the upgradestop option before you begin to upgrade InfoScale using the yum upgrade command. This command performs required pre-upgrade checks and backups all the configuration files before the upgrade.
Syntax for upgradestart:
/opt/VRTS/install/installer -upgradestart
Use the upgradestart option to start the services after upgrading InfoScale rpms using yum such as starting CVM agents, registering extra types.cf files, and updating protocol version.
To upgrade InfoScale using yum
- Disable all the service groups on a cluster.
- Unmount the file system which is not under the VCS control.
- Use the following command to disable the dmp native support:
# vxdmpadm settune dmp_native_support=off
- Stop the installer to stop all the services as follows:
# ./installer -upgradestop
Note:
The base version for upgradestop is 8.0. You cannot perform direct yum upgrade from earlier versions of InfoScale to 8.0 or later using upgradestop. You may use -stop option with installer, post running ./installer -stop command. Ensure that all the modules and services are stopped using lsmod and systemctl status commands and verify the status before proceeding with yum upgrade.
- Copy the
infoscale802.repo
to/etc/yum.repos.d/
on the YUM client machine from the installation media, or you can manually create the.repo file
using the following steps:i. Create
.repo
file using any editor [vi,vim or nano] as shown below:# vi /etc/yum.repos.d/Infoscale802.repo
ii. After executing the above command insert the following values in the .repo file as follows:
[repo-InfoScale802] name=Repository for Veritas InfoScale 802 baseurl=file:///<image_dir>/rpms/ enabled=1 gpgcheck=1 gpgkey=file:///<image_dir>/rpms/RPM-GPG-KEY-veritas-infoscale7
Note: The values for the baseurl attribute can start with
http://, ftp://, or file://.
The URL you choose needs to be able to access the repodata directory. It also needs to access all the InfoScale RPMs in the repository that you create or update.iii. Save and exit the text editor
Note:
If you copy the .repo file directly from installation media then you need to update the 'baseurl' and 'gpgkey' entry in
/etc/yum.repos.d/Infoscale802.repo
for yum repository directory using any text editor. - Run the following commands to refresh the yum repository:
# yum repolist
# yum updateinfo
# yum grouplist
- Run the following command to upgrade Veritas InfoScale product: # yum upgrade VRTS*
If OS upgrade is involved and a reboot is required, then upgrade both OS and IS at the same time :# yum upgrade <--releasever=<version>>
- Repeat steps 5 to 8 on each node of the cluster.
- After completing all above steps, run the following command to manually generate installer scripts for configuration.
# /opt/VRTS/install/bin/UXRT802/add_install_scripts
Run the following command to manually install the
VRTSrest
package on all the cluster nodes.# yum install VRTSrest
- Run the following command to start:# /opt/VRTS/install/installer -upgradestart
After successful completion of yum upgrade ensure that cluster is up and running. You may verify the CVM protocol version using vxdctl protocolversion command and VCS protocol version as follows:
/opt/VRTS/bin/haclus -value ProtocolNumber
Note:
Ensure that you set the yum repository manually on each node of the cluster before running the yum install and upgrade command.
Yum install or upgrade with response files
Yum based install or upgrade can be performed using either menu driven program or response-file.
Table:
Variable | Description | List or Scalar | Mandatory or Optional |
---|---|---|---|
CFG{opt}{yum} | The -yum option is used to define the yum repository path or the repository name to be used for performing yum-based tasks. This option is supported on Red Hat Linux and Oracle Linux only. | Scalar | Optional |
CFG{opt}{matrixpath} | The -matrixpath option is used to accept a user-specified release matrix data path. | Scalar | Optional |
CFG{opt}{upgradestop} | The -upgradestop option stops all the drivers and the processes. This option is supported only on Red Hat Linux and Oracle Linux. | Scalar | Optional |
CFG{opt}{upgradestart} | The -upgradestart option starts all drivers and processes of a product where product is upgraded using yum. The option is supported only on Red Hat Linux and Oracle Linux. | Scalar | Optional |
The following are the sample response files:
Installation using -yum with reponame:
# # Configuration Values: # our %CFG; $CFG{accepteula}=1;
$CFG{opt}{install}=1;
$CFG{opt}{yum}="repo-InfoScale802";
$CFG{prod}="ENTERPRISE802";
$CFG{systems}=[ "dl380g10-10-vip17" ];
1;
Installation using -yum with repo URL:
# # Configuration Values: # our %CFG; $CFG{accepteula}=1;
$CFG{opt}{install}=1;
$CFG{opt}{yum}="http://xyz.com/rhel8_x86_64/rpms/";
$CFG{prod}="ENTERPRISE802";
$CFG{systems}=[ "dl380g10-10-vip17" ];
1;
Installation using -yum, -matrixpath and -patch_path:
# # Configuration Values: # our %CFG; $CFG{accepteula}=1;
$CFG{opt}{install}=1;
$CFG{opt}{matrixpath}="/root/patch_matrix/";
$CFG{opt}{patch_path}="repo-InfoScale802P";
$CFG{opt}{yum}="repo-InfoScale802";
$CFG{prod}="ENTERPRISE802";
$CFG{systems}=[ "dl380g10-10-vip17" ];
1;
Note:
For all upgrade operations, you need to enter the newly added options wherever required. Rest of the configuration values are same as per traditional installation and upgrade.
Upgradestop before manual yum upgrade:
#
# Configuration Values:
#
our %CFG;
$CFG{opt}{gco}=1;
$CFG{opt}{stop}=1;
$CFG{opt}{upgradestop}=1;
$CFG{opt}{vr}=1;
$CFG{prod}="ENTERPRISE802";
$CFG{systems}=[ "dl380g10-10-vip17","dl380g10-10-vip18" ];
$CFG{vcs_allowcomms}=1;
1;
Upgradestart after manual yum upgrade:
#
# Configuration Values:
#
our %CFG;
$CFG{opt}{gco}=1;
$CFG{opt}{start}=1;
$CFG{opt}{upgradestart}=1;
$CFG{opt}{vr}=1;
$CFG{prod}="ENTERPRISE802";
$CFG{systems}=[ "dl380g10-10-vip14" ];
$CFG{vcs_allowcomms}=1;
1;
More Information