Veritas Access Installation Guide

Last Published:
Product(s): Access (7.3.1)
Platform: Linux
  1. Introducing Veritas Access
    1.  
      About Veritas Access
  2. Licensing in Veritas Access
    1.  
      About Veritas Access product licensing
  3. System requirements
    1.  
      Important release information
    2. System requirements
      1. Linux requirements
        1.  
          Operating system RPM installation requirements and operating system patching
        2.  
          Kernel RPMs that are required to be installed with exact predefined RPM versions
        3.  
          OL kernel RPMs that are required to be installed with exact predefined RPM versions
        4.  
          Required operating system RPMs for OL 6.8
        5.  
          Required operating system RPMs for OL 7.3
        6.  
          Required operating system RPMs for OL 7.4
        7.  
          Required operating system RPMs for RHEL 6.6
        8.  
          Required operating system RPMs for RHEL 6.7
        9.  
          Required operating system RPMs for RHEL 6.8
        10.  
          Required operating system RPMs for RHEL 7.3
        11.  
          Required operating system RPMs for RHEL 7.4
      2.  
        Software requirements for installing Veritas Access in a VMware ESXi environment
      3.  
        Hardware requirements for installing Veritas Access virtual machines
      4.  
        Management Server Web browser support
      5.  
        Supported NetBackup versions
      6.  
        Supported OpenStack versions
      7.  
        Supported Oracle versions and host operating systems
      8.  
        Supported IP version 6 Internet standard protocol
    3. Network and firewall requirements
      1.  
        NetBackup ports
      2.  
        OpenDedup ports and disabling the iptable rules
      3.  
        CIFS protocols and firewall ports
    4.  
      Maximum configuration limits
  4. Preparing to install Veritas Access
    1.  
      Overview of the installation process
    2.  
      Hardware requirements for the nodes
    3. About using LLT over the RDMA network for Veritas Access
      1.  
        RDMA over InfiniBand networks in the Veritas Access clustering environment
      2.  
        How LLT supports RDMA for faster interconnections between applications
      3.  
        Configuring LLT over RDMA for Veritas Access
      4.  
        How the Veritas Access installer configures LLT over RDMA
      5.  
        LLT over RDMA sample /etc/llttab
    4.  
      Connecting the network hardware
    5. About obtaining IP addresses
      1.  
        About calculating IP address requirements
      2.  
        Reducing the number of IP addresses required at installation time
    6.  
      About checking the storage configuration
  5. Deploying virtual machines in VMware ESXi for Veritas Access installation
    1.  
      Setting up networking in VMware ESXi
    2.  
      Creating a datastore for the boot disk and LUNs
    3.  
      Creating a virtual machine for Veritas Access installation
  6. Installing and configuring a cluster
    1.  
      Installation overview
    2.  
      Summary of the installation steps
    3.  
      Before you install
    4. Installing the operating system on each node of the cluster
      1.  
        About the driver node
      2.  
        Installing the operating system on the target Veritas Access cluster
      3.  
        Installing the Oracle Linux operating system on the target Veritas Access cluster
      4.  
        Obtaining the Red Hat Enterprise Linux compatible kernels
    5. Installing Veritas Access on the target cluster nodes
      1.  
        Installing and configuring the Veritas Access software on the cluster
      2.  
        Veritas Access Graphical User Interface
    6. About NIC bonding and NIC exclusion
      1.  
        Excluding a NIC
      2.  
        Including a NIC
      3.  
        Creating a new NIC bond
      4.  
        Removing a NIC bond
      5.  
        Removing a NIC from the bond list
    7. About VLAN Tagging
      1.  
        Adding a VLAN device on a particular NIC
      2.  
        Limitations of VLAN Tagging
    8.  
      Replacing an Ethernet interface card
    9.  
      Configuring I/O fencing
    10.  
      About configuring Veritas NetBackup
    11.  
      About enabling kdump during an Veritas Access configuration
    12.  
      Reconfiguring the Veritas Access cluster name and network
    13.  
      Configuring a KMS server on the Veritas Access cluster
  7. Automating Veritas Access installation and configuration using response files
    1.  
      About response files
    2.  
      Performing a silent Veritas Access installation
    3.  
      Response file variables to install and configure Veritas Access
    4.  
      Sample response file for Veritas Access installation and configuration
  8. Displaying and adding nodes to a cluster
    1.  
      About the Veritas Access installation states and conditions
    2.  
      Displaying the nodes in the cluster
    3.  
      Before adding new nodes in the cluster
    4.  
      Adding a node to the cluster
    5.  
      Deleting a node from the cluster
    6.  
      Shutting down the cluster nodes
  9. Upgrading Veritas Access and operating system
    1.  
      Upgrading the operating system and Veritas Access
  10. Upgrading Veritas Access using a rolling upgrade
    1.  
      About rolling upgrades
    2.  
      Supported rolling upgrade paths for upgrades on RHEL
    3.  
      Performing a rolling upgrade using the installer
  11. Uninstalling Veritas Access
    1.  
      Before you uninstall Veritas Access
    2. Uninstalling Veritas Access using the installer
      1.  
        Removing Veritas Access 7.3.1 RPMs
      2.  
        Running uninstall from the Veritas Access 7.3.1 disc
  12. Appendix A. Installation reference
    1.  
      Installation script options
  13. Appendix B. Troubleshooting the LTR upgrade
    1.  
      Locating the log files for troubleshooting the LTR upgrade
    2.  
      Troubleshooting pre-upgrade issues for LTR
    3.  
      Troubleshooting post-upgrade issues for LTR
  14. Appendix C. Configuring the secure shell for communications
    1.  
      Manually configuring passwordless secure shell (ssh)
    2.  
      Setting up ssh and rsh connections using the pwdutil.pl utility

About rolling upgrades

This release of Veritas Access supports rolling upgrades from the Veritas Access 7.2.1.1 and later versions. Rolling upgrade is supported on RHEL 6.6, 6.7, and 6.8.

A rolling upgrade minimizes the service and application downtime for highly available clusters by limiting the upgrade time to the amount of time that it takes to perform a service group failover. Nodes with different product versions can be run in one cluster.

The rolling upgrade has two main phases. The installer upgrades kernel RPMs in phase 1 and VCS agent RPMs in phase 2. The upgrade process divides the cluster into two subclusters, called the first subcluster and the second subcluster. First, the upgrade is performed on the first subcluster. The upgrade process stops all services and resources on the nodes of the first subcluster. All services (including the VIP groups) fail over to the second subcluster. During the failover process, the clients that are connected to the VIP groups of the first subcluster nodes are intermittently interrupted. For those clients that do not time out, the service is resumed after the VIP groups become online on one of the nodes of the second subcluster.

While the upgrade process is running on the nodes of the first subcluster, the nodes of the second subcluster nodes continue to serve the clients. After the first subcluster node has been upgraded, it restarts the services and resources on first stage nodes. Immediately after the first subcluster comes up, the upgrade process stops the services and resources on the remaining nodes. All services and resources are online and serve clients. Meanwhile, the rolling upgrade starts the upgrade process on the remaining nodes. After the upgrade is complete on the remaining nodes, the cluster recovers and services are balanced across the cluster.

Workflow for the LTR upgrade

This process is required for upgrading Long-term Retention (LTR) on the Veritas Access cluster. All the backup and/or restore jobs from NetBackup must be stopped before you start the rolling upgrade process.

For the LTR upgrade scenarios, you need to use the following scripts:

  • preUpgrade_ltr_access731.py

  • postUpgrade_ltr_access731.py

Before you start the rolling upgrade for LTR:

  • You need to execute the preUpgrade_ltr_access731.py script where the odd_cache_fs file system is created to backup the cache data of OpenDedup volumes. Size of this file system is determined based on the current cache size (/opt/sdfs).

  • The pool(s) which is configured as a default pool for Objectaccess to create this file system. Therefore, sufficient space must be available in this pool(s). After the odd_cache_fs file system is provisioned, all the OpenDedup volumes are made offline and configuration and the cache data are backed up.

After the rolling upgrade of cluster is completed, you need to execute the postUpgrade_ltr_access731.py script where all the OpenDedup volumes are made online after restoring all the configurations.

A one-time tier policy is created for the configured cloud tiers to move the OpenDedup metadata files (ending with .6442 extension) from the cloud tier to an on-premises storage. OpenDedup need these metadata files to verify and restore configurations. If these files are stored on a cloud tier, performance of these operations may get degraded.

Workflow for a rolling upgrade

A rolling upgrade has two main phases where the installer upgrades the kernel RPMs in Phase 1 and VCS agent-related non-kernel RPMs in Phase 2.

  1. Use the following pre-upgrade steps only for LTR configured Veritas Access cluster.

    Note:

    These LTR related steps are required when OpenDedup volumes are provisioned on Veritas Access cluster.

    • Ensure that the backup and/or restore jobs from NetBackup are stopped.

    • From the ISO, copy the upgrade_scripts/preUpgrade_ltr_access731.py script to / on each node where the OpenDedup volume is online.

    • Execute the preUpgrade_ltr_access731.py script one-by-one on each node where the OpenDedup volume is online.

  2. The upgrade process divides the cluster into two subclusters, first subcluster and the second subcluster.

  3. In Phase 1, the upgrade is performed on the second subcluster. The upgrade process stops all services and resources on the nodes of the second subcluster. All services (including the VIP groups) failover to the first subcluster. The parallel service groups on the second subcluster are taken offline.

  4. During the failover process, the clients that are connected to the VIP groups of the second subcluster nodes are intermittently interrupted. For those clients that do not time out, the service is resumed after the VIP groups become online on one of the nodes of the first subcluster.

  5. The installer upgrades the kernel RPMs on the second subcluster. The nodes of the first subcluster nodes continue to serve the clients.

  6. Once Phase 1 of the rolling upgrade is complete on the second subcluster, Phase 1 of the rolling upgrade is performed on the first subcluster. The applications are failed over to the second subcluster. The parallel service groups are brought online on the second subcluster and are taken offline on the first subcluster.

  7. After Phase 1 is complete, the nodes run with new RPMs but with the old protocol version.

  8. During Phase 2 of the rolling upgrade, all remaining RPMs are upgraded on all the nodes of the cluster simultaneously. VCS and VCS agent packages are upgraded. The kernel drivers are upgraded to the new protocol version. Applications stay online during Phase 2. The High Availability Daemon (HAD) stops and starts again.

  9. Use the following post-upgrade steps only for LTR configured Veritas Access cluster.

    Note:

    These steps are required when the OpenDedup volumes are provisioned on Veritas Access cluster.

    • From the ISO, copy the upgrade_scripts/postUpgrade_ltr_access731.py script to / on the Management Console node.

    • Execute the postUpgrade_ltr_access731.py script.

More Information

Troubleshooting pre-upgrade issues for LTR

Performing a rolling upgrade using the installer

Supported rolling upgrade paths for upgrades on RHEL

Troubleshooting post-upgrade issues for LTR