Veritas InfoScale™ 8.0.2 Installation Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.2)
Platform: Linux
  1. Section I. Planning and preparation
    1. Introducing Veritas InfoScale
      1.  
        About the Veritas InfoScale product suite
      2.  
        Components of the Veritas InfoScale product suite
      3.  
        About the co-existence of InfoScale products
    2. Licensing Veritas InfoScale
      1.  
        About Veritas InfoScale product licensing
      2.  
        About InfoScale Core Plus license meter
      3.  
        About telemetry data collection in InfoScale
      4.  
        Licensing notes
      5. About managing InfoScale licenses
        1.  
          About the vxlicinstupgrade utility
      6.  
        Generating license report with vxlicrep command
    3. System requirements
      1.  
        Important release information
      2.  
        Disk space requirements
      3. Hardware requirements
        1.  
          SF and SFHA hardware requirements
        2.  
          SFCFS and SFCFSHA hardware requirements
        3.  
          SF Oracle RAC hardware requirements
        4.  
          VCS hardware requirements
      4.  
        Supported operating systems and database versions
      5.  
        Number of nodes supported
      6.  
        Get the InfoScale cryptographic public keys (for Secure Boot-enabled systems)
    4. Preparing to install
      1.  
        Mounting the ISO image
      2.  
        Setting up ssh or rsh for inter-system communications
      3.  
        Obtaining installer patches
      4.  
        Disabling external network connection attempts
      5.  
        Verifying the systems before installation
      6. Setting up the private network
        1.  
          Optimizing LLT media speed settings on private NICs
        2.  
          Guidelines for setting the media speed for LLT interconnects
        3.  
          Guidelines for setting the maximum transmission unit (MTU) for LLT interconnects in Flexible Storage Sharing (FSS) environments
      7. Setting up shared storage
        1.  
          Setting up shared storage: SCSI
        2.  
          Setting up shared storage: Fibre Channel
      8.  
        Synchronizing time settings on cluster nodes
      9.  
        Setting the kernel.hung_task_panic tunable
      10. Planning the installation setup for SF Oracle RAC systems
        1. Planning your network configuration
          1.  
            Planning the public network configuration for Oracle RAC
          2. Planning the private network configuration for Oracle RAC
            1.  
              High availability solutions for Oracle RAC private network
          3.  
            Planning the public network configuration for Oracle RAC
          4.  
            Planning the private network configuration for Oracle RAC
        2. Planning the storage
          1.  
            Planning the storage
          2. Planning the storage for Oracle RAC
            1. Planning the storage for OCR and voting disk
              1.  
                OCR and voting disk storage configuration for external redundancy
              2.  
                OCR and voting disk storage configuration for normal redundancy
            2.  
              Planning the storage for Oracle RAC binaries and data files
            3.  
              Planning for Oracle RAC ASM over CVM
        3.  
          Planning volume layout
        4.  
          Planning file system design
        5.  
          Setting the umask before installation
        6.  
          Setting the kernel.panic tunable
        7.  
          Configuring the I/O scheduler
      11. Preparing for deployment in a Secure Boot environment
        1.  
          About enabling Secure Boot on InfoScale hosts
        2.  
          Enrolling the InfoScale public key
        3.  
          Considerations for working with InfoScale in a Secure Boot environment
  2. Section II. Installation of Veritas InfoScale
    1. Installing Veritas InfoScale using the installer
      1.  
        Installing Veritas InfoScale using the installer
      2.  
        Installing or upgrading Veritas InfoScale by using the installer as a sudo user
      3.  
        Installing or upgrading Veritas InfoScale using the installer with the -yum option
      4.  
        Executive Order logging
    2. Installing Veritas InfoScale using response files
      1. About response files
        1.  
          Syntax in the response file
      2.  
        Installing InfoScale using response files
      3.  
        Response file variables to install Veritas InfoScale
      4.  
        Sample response files for Veritas InfoScale installation
    3. Installing Veritas Infoscale using operating system-specific methods
      1.  
        Verifying Veritas InfoScale RPMs
      2.  
        About installing InfoScale using operating system-specific methods
      3. Installing InfoScale using Kickstart
        1.  
          Sample Kickstart configuration file
      4.  
        Installing Veritas InfoScale using yum
      5. Installing InfoScale using the Red Hat Satellite server
        1.  
          Using Red Hat Satellite server to install InfoScale products
    4. Completing the post installation tasks
      1.  
        Verifying product installation
      2.  
        Setting environment variables
      3.  
        Commands to manage the Veritas telemetry collector on your server
      4.  
        Next steps after installation
  3. Section III. Uninstallation of Veritas InfoScale
    1. Uninstalling Veritas InfoScale using the installer
      1.  
        Removing VxFS file systems
      2.  
        Removing rootability
      3. Moving volumes to disk partitions
        1.  
          Moving volumes onto disk partitions using VxVM
      4.  
        Removing the Replicated Data Set
      5.  
        Uninstalling InfoScale RPMs using the installer
      6.  
        Removing the Storage Foundation for Databases (SFDB) repository
    2. Uninstalling Veritas InfoScale using response files
      1.  
        Uninstalling InfoScale using response files
      2.  
        Response file variables to uninstall Veritas InfoScale
      3.  
        Sample response file for Veritas InfoScale uninstallation
  4. Section IV. Installation reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
    2. Appendix B. Tunable files for installation
      1.  
        About setting tunable parameters using the installer or a response file
      2.  
        Setting tunables for an installation, configuration, or upgrade
      3.  
        Setting tunables with no other installer-related operations
      4.  
        Setting tunables with an un-integrated response file
      5.  
        Preparing the tunables file
      6.  
        Setting parameters for the tunables file
      7.  
        Tunables value parameter definitions
    3. Appendix C. Troubleshooting installation issues
      1.  
        Restarting the installer after a failed network connection
      2.  
        About the VRTSspt RPM troubleshooting tools
      3.  
        Incorrect permissions for root on remote system
      4.  
        Inaccessible system
    4. Appendix D. Managing InfoScale digital signatures (Secure Boot environment)
      1.  
        Verify an InfoScale module signature key
      2.  
        Removing the InfoScale public key

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 Install a product or Upgrade a product 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

  1. Specify each RPM name and its yum equivalent. For example: # yum install VRTSvlic VRTSperl ... VRTSsfcpi
  2. Specify all the Veritas InfoScale RPMs using RPM glob. For example: # yum install 'VRTS*'
  3. 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

  1. Disable all the service groups on a cluster.
  2. Unmount the file system which is not under the VCS control.
  3. Use the following command to disable the dmp native support:

    # vxdmpadm settune dmp_native_support=off

  4. 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.

  5. 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.

  6. Run the following commands to refresh the yum repository:
    • # yum repolist

    • # yum updateinfo

    • # yum grouplist

  7. 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>>

  8. Repeat steps 5 to 8 on each node of the cluster.
  9. After completing all above steps, run the following command to manually generate installer scripts for configuration.

    # /opt/VRTS/install/bin/UXRT802/add_install_scripts

  10. Run the following command to manually install the VRTSrest package on all the cluster nodes.

    # yum install VRTSrest

  11. 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;