Storage Foundation 7.4.2 Configuration and Upgrade Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Linux
  1. Section I. Introduction and configuration of Storage Foundation
    1. Introducing Storage Foundation
      1. About Storage Foundation
        1.  
          About Veritas Replicator Option
      2.  
        About Veritas InfoScale Operations Manager
      3.  
        About Veritas Services and Operations Readiness Tools (SORT)
    2. Configuring Storage Foundation
      1.  
        Configuring Storage Foundation using the installer
      2. Configuring SF manually
        1.  
          Configuring Veritas Volume Manager
        2. Configuring Veritas File System
          1.  
            Loading and unloading the file system module
      3.  
        Configuring SFDB
  2. Section II. Upgrade of Storage Foundation
    1. Planning to upgrade Storage Foundation
      1.  
        About the upgrade
      2.  
        Supported upgrade paths
      3. Preparing to upgrade SF
        1.  
          Getting ready for the upgrade
        2.  
          Creating backups
        3.  
          Determining if the root disk is encapsulated
        4. Pre-upgrade planning when VVR is configured
          1.  
            Considerations for upgrading SF to 7.4 or later on systems with an ongoing or a paused replication
          2. Planning an upgrade from the previous VVR version
            1.  
              Planning and upgrading VVR to use IPv6 as connection protocol
        5.  
          Upgrading the array support
      4.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Upgrading Storage Foundation
      1. Upgrading Storage Foundation from previous versions to 7.4.2
        1.  
          Upgrading Storage Foundation using the product installer
      2. Upgrading Volume Replicator
        1. Upgrading VVR without disrupting replication
          1.  
            Upgrading VVR on the Secondary
          2.  
            Upgrading VVR on the Primary
      3.  
        Upgrading SFDB
    3. Performing an automated SF upgrade using response files
      1.  
        Upgrading SF using response files
      2.  
        Response file variables to upgrade SF
      3.  
        Sample response file for SF upgrade
    4. Performing post-upgrade tasks
      1.  
        Optional configuration steps
      2.  
        Re-joining the backup boot disk group into the current disk group
      3.  
        Reverting to the backup boot disk group after an unsuccessful upgrade
      4.  
        Recovering VVR if automatic upgrade fails
      5.  
        Resetting DAS disk names to include host name in FSS environments
      6.  
        Upgrading disk layout versions
      7.  
        Upgrading VxVM disk group versions
      8.  
        Updating variables
      9.  
        Setting the default disk group
      10.  
        Verifying the Storage Foundation upgrade
  3. Section III. Post configuration tasks
    1. Performing configuration tasks
      1.  
        Switching on Quotas
      2.  
        Enabling DMP support for native devices
      3. About configuring authentication for SFDB tools
        1.  
          Configuring vxdbd for SFDB tools authentication
  4. Section IV. Configuration and Upgrade reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
      2.  
        About using the postcheck option
    2. Appendix B. Configuring the secure shell or the remote shell for communications
      1.  
        About configuring secure shell or remote shell communication modes before installing products
      2.  
        Manually configuring passwordless ssh
      3.  
        Setting up ssh and rsh connection using the installer -comsetup command
      4.  
        Setting up ssh and rsh connection using the pwdutil.pl utility
      5.  
        Restarting the ssh session
      6.  
        Enabling rsh for Linux

Response file variables to upgrade SF

Table: Response file variables for upgrading SF lists the response file variables that you can define to configure SF.

Table: Response file variables for upgrading SF

Variable

Description

CFG{accepteula}

Specifies whether you agree with the EULA.pdf file on the media.

List or scalar: scalar

Optional or required: required

CFG{systems}

List of systems on which the product is to be installed or uninstalled.

List or scalar: list

Optional or required: required

CFG{upgrade}

Upgrades all RPMs installed.

List or scalar: list

Optional or required: required

CFG{keys}{keyless}

CFG{keys}{licensefile}

CFG{keys}{keyless} gives a list of keyless keys to be registered on the system.

CFG{keys}{licensefile} gives the absolute file path to the permanent license key to be registered on the system.

List or scalar: list

Optional or required: required

CFG{opt}{keyfile}

Defines the location of an ssh keyfile that is used to communicate with all remote systems.

List or scalar: scalar

Optional or required: optional

CFG{opt}{tmppath}

Defines the location where a working directory is created to store temporary files and the RPMs that are needed during the install. The default location is /opt/VRTStmp.

List or scalar: scalar

Optional or required: optional

CFG{opt}{logpath}

Mentions the location where the log files are to be copied. The default location is /opt/VRTS/install/logs.

List or scalar: scalar

Optional or required: optional

$CFG{edgeserver_host}

Use this parameter to configure the edge server.

Enter telemetry.veritas.com to use the Veritas Cloud Receiver, which is a preconfigured, cloud-based edge server deployed by Veritas.

Optional or required: required

Note:

An edge server is used to collect licensing and platform related information from InfoScale products as part of the Veritas Product Improvement Program. The information collected helps identify how customers deploy and use the product, and enables Veritas to manage customer licenses more efficiently.

$CFG{edgeserver_port}

Use this parameter to configure the port number of the edge server.

Enter 443, which is the port number used by the Veritas Cloud Receiver.

Optional or required: required

Note:

An edge server is used to collect licensing and platform related information from InfoScale products as part of the Veritas Product Improvement Program. The information collected helps identify how customers deploy and use the product, and enables Veritas to manage customer licenses more efficiently.

  

CFG{mirrordgname}{system}

If the root dg is encapsulated and you select split mirror is selected:

Splits the target disk group name for a system.

List or scalar: scalar

Optional or required: optional

CFG{splitmirror}{system}

If the root dg is encapsulated and you select split mirror is selected:

Indicates the system where you want a split mirror backup disk group created.

List or scalar: scalar

Optional or required: optional

CFG{opt}{disable_dmp_native_support}

If it is set to 1, Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools is disabled after 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.

List or scalar: scalar

Optional or required: optional

CFG{opt}{patch_path}

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 .

List or scalar: scalar

Optional or required: optional

CFG{opt}{patch2_path}

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.

List or scalar: scalar

Optional or required: optional

CFG{opt}{patch3_path}

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.

List or scalar: scalar

Optional or required: optional

CFG{opt}{patch4_path}

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.

List or scalar: scalar

Optional or required: optional

CFG{opt}{patch5_path}

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.

List or scalar: scalar

Optional or required: optional