Veritas InfoScale™ 7.3 Installation Guide - Linux
- Section I. Introduction to Veritas InfoScale
- Introducing Veritas InfoScale
- Licensing Veritas InfoScale
- Section II. Planning and preparation
- System requirements
- Hardware requirements
- Preparing to install
- Setting up the private network
- Setting up shared storage
- Planning the installation setup for SF Oracle RAC and SF Sybase CE systems
- Planning your network configuration
- Planning the storage
- Planning the storage for Oracle RAC
- System requirements
- Section III. Installation of Veritas InfoScale
- Installing Veritas InfoScale using the installer
- Installing Veritas InfoScale using response files
- Installing Veritas Infoscale using operating system-specific methods
- Installing Veritas InfoScale using Kickstart
- Installing Veritas InfoScale using the Red Hat Satellite server
- Completing the post installation tasks
- Section IV. Uninstallation of Veritas InfoScale
- Uninstalling Veritas InfoScale using the installer
- Moving volumes to disk partitions
- Uninstalling Veritas InfoScale using response files
- Uninstalling Veritas InfoScale using the installer
- Section V. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- Appendix C. Troubleshooting installation issues
Installation script options
Table: Available command line options shows command line options for the installation script. For an initial install or upgrade, options are not usually required. The installation script options apply to all Veritas InfoScale product scripts, except where otherwise noted.
Table: Available command line options
Command Line Option
Displays all RPMs required for the specified product. The RPMs are listed in correct installation order. The output can be used to create scripts for command line installs, or for installations over a network.
The -comcleanup option removes the secure shell or remote shell configuration added by installer on the systems. The option is only required when installation routines that performed auto-configuration of the shell are abruptly terminated.
The -comsetup option is used to set up the ssh or rsh communication between systems without requests for passwords or passphrases.
Configures the product after installation.
Disables Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade. Retaining Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade increases RPM upgrade time depending on the number of LUNs and native LVM volume groups and ZFS pools configured on the system.
- hostfile full_path_to_file
Specifies the location of a file that contains a list of hostnames on which to install.
Used to install products on system
Used to perform online upgrade. Using this option, the installer upgrades the whole cluster and also supports customer's application zero down time during the upgrade procedure. Now this option is supported only in VCS.
Defines the path of a patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed .
Defines the path of a second patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.
Defines the path of a third patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.
Defines the path of a fourth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.
Defines the path of a fifth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.
- keyfile ssh_key_file
Specifies a key file for secure shell (SSH) installs. This option passes -I ssh_key_file to every SSH invocation.
- kickstart dir_path
Produces a kickstart configuration file for installing with Linux RHEL Kickstart. The file contains the list of required RPMs in the correct order for installing, in a format that can be used for Kickstart installations. The dir_path indicates the path to the directory in which to create the file.
Registers or updates product licenses on the specified systems.
- logpath log_path
Specifies a directory other than /opt/VRTS/install/logs as the location where installer log files, summary files, and response files are saved.
Disables the installer from making outbound networking calls to Veritas Services and Operations Readiness Tool (SORT) in order to automatically obtain patch and release information updates.
Allows installation of product RPMs without entering a license key. Licensed features cannot be configured, started, or used when this option is specified.
Displays product's RPMs in correct installation order by group.
Checks for different HA and file system-related processes, the availability of different ports, and the availability of cluster-related service groups.
Performs a preinstallation check to determine if systems meet all installation requirements. Veritas recommends doing a precheck before installing a product.
Specifies the product for operations.
Specifies the component for operations.
Displays progress details without showing the progress bar.
Specifies an installer patch file.
The -requirements option displays required OS version, required RPMs and patches, file system space, and other system requirements in order to install the product.
- responsefile response_file
Automates installation and configuration by using system and configuration information stored in a specified file instead of prompting for information. The response_file must be a full path name. You must edit the response file to use it for subsequent installations. Variable field definitions are defined within the file.
Starts a rolling upgrade. Using this option, the installer detects the rolling upgrade status on cluster systems automatically without the need to specify rolling upgrade phase 1 or phase 2 explicitly.
The -rollingupgrade_phase1 option is used to perform rolling upgrade Phase-I. In the phase, the product kernel RPMs get upgraded to the latest version.
The -rollingupgrade_phase2 option is used to perform rolling upgrade Phase-II. In the phase, VCS and other agent RPMs upgrade to the latest version. Product kernel drivers are rolling-upgraded to the latest protocol version.
Specify this option when you want to use rsh and RCP for communication between systems instead of the default ssh and SCP.
Specifies that the installation script performs install, uninstall, start, and stop operations on each system in a serial fashion. If this option is not specified, these operations are performed simultaneously on all systems.
Specify this option when you want to set tunable parameters after you install and configure a product. You may need to restart processes of the product for the tunable parameter values to take effect. You must use this option together with the -tunablesfile option.
Starts the daemons and processes for the specified product.
Stops the daemons and processes for the specified product.
The -timeout option is used to specify the number of seconds that the script should wait for each command to complete before timing out. Setting the -timeout option overrides the default value of 1200 seconds. Setting the -timeout option to 0 prevents the script from timing out. The -timeout option does not work with the -serial option
- tmppath tmp_path
Specifies a directory other than /var/tmp as the working directory for the installation scripts. This destination is where initial logging is performed and where RPMs are copied on remote systems before installation.
Lists all supported tunables and create a tunables file template.
Specify this option when you specify a tunables file. The tunables file should include tunable parameters.
This option is used to uninstall the products from systems
Specifies that an existing version of the product exists and you plan to upgrade it.
Checks and reports the installed products and their versions. Identifies the installed and missing RPMs and patches where applicable for the product. Provides a summary that includes the count of the installed and any missing RPMs and patches where applicable. Lists the installed patches, patches, and available updates for the installed product if an Internet connection is available.
The -yumgroupxml option is used to generate a yum group definition XML file. The createrepo command can use the file on Redhat Linux to create a yum group for automated installation of all RPMs for a product. An available location to store the XML file should be specified as a complete path. The -yumgroupxml option is supported on RHEL and supported RHEL-compatible distributions only.