Veritas Access Installation Guide

Last Published:
Product(s): Access (7.4)
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 7.3
        5.  
          Required operating system RPMs for OL 7.4
        6.  
          Required operating system RPMs for RHEL 7.3
        7.  
          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.  
      Connecting the network hardware
    4. About obtaining IP addresses
      1.  
        About calculating IP address requirements
      2.  
        Reducing the number of IP addresses required at installation time
    5.  
      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
    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 managing the NICs, bonds, and VLAN devices
      1.  
        Selecting the public NICs
      2.  
        Selecting the private NICs
      3.  
        Excluding a NIC
      4.  
        Including a NIC
      5.  
        Creating a NIC bond
      6.  
        Removing a NIC bond
      7.  
        Removing a NIC from the bond list
    7. About VLAN tagging
      1.  
        Creating a VLAN device
      2.  
        Removing a VLAN device
      3.  
        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.  
      Adding a node in mixed mode environment
    6.  
      Deleting a node from the cluster
    7.  
      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 the rolling upgrades
    2.  
      Supported rolling upgrade paths for upgrades on RHEL and Oracle Linux
    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.4 RPMs
      2.  
        Running uninstall from the Veritas Access 7.4 disc
  12. Appendix A. Installation reference
    1.  
      Installation script options
  13. Appendix B. Configuring the secure shell for communications
    1.  
      Manually configuring passwordless SSH
    2.  
      Setting up the SSH and the RSH connections
  14. Appendix C. Manual deployment of Veritas Access
    1.  
      Deploying Veritas Access manually on a two-node cluster in a non-SSH environment
    2.  
      Enabling internal sudo user communication in Veritas Access

About Veritas Access product licensing

In this release, Veritas has introduced the TB-per-core licensing model for Veritas Access. The per-core and per-terabyte licensing model of earlier releases is also supported in this release.

The TB-per-core licensing model is based on both capacity per-core and time period. You can now license Veritas Access as per your requirement for raw capacity. This is managed through the software.

Depending on the capacity to core ratio, three types of capacity-based licenses are available. Each license has an allotted storage capacity in the range of 2001 TB - Unlimited.

  • Premium

  • Standard

  • Basic

The time-based license category includes the following licenses:

  • Perpetual: A license with unlimited validity period.

  • Subscription: A license that is valid for a subscribed period, and needs to be renewed from time to time. Typically, the subscription can be for a period of 1 year, 2 years, or 3 years, and so on.

  • Trialware: A license that is valid for 60 days.

Veritas recommends the tier that is best suited for your needs based on your current system configuration across the clusters. The new metering and recommended tier is based on capacity utilization to core ratio. Capacity utilization is the raw capacity utilized while the core refers to the physical cores present across the cluster. This information is also available in the GUI in the Recommended Tier.

Table: Licensing methods

Tiering model

TB-per-core meter capacity

Capacity tier range

Time-based licensing

Premium

TB to core ratio <= 4 TB/core

2001 TB - Unlimited

Subscription - 1 year, 2 years, and 3 years

Perpetual - Unlimited for a product version

Trialware- 60 days

Standard

TB to core ratio

Between 4 TB/core and 25 TB/core

2001 TB - Unlimited

Subscription - 1 year, 2 years, and 3 years

Perpetual - Unlimited for a product version

Basic

TB to core ratio > 25 TB/core

2001 TB - Unlimited

Subscription - 1 year, 2 years, and 3 years

Perpetual - Unlimited for a product version

You can download Veritas Access from the Veritas Access External Product page for evaluation.

The trialware has the premium tier licensing model with a storage capacity range of 2001 TB - Unlimited. You can upgrade to any valid per-core license from the trialware. If you have the Veritas Access 7.3.1 product with the per-core or per-terabyte licensing, and you upgrade to Veritas Access 7.4, you can continue to use the 7.3.1 per-core or 7.3.1 per-terabyte license.

Notes:

  • You must provide a valid license during the product installation. If you do not provide a valid license, a 60-days trialware license is installed.

  • If you exceed the licensed storage capacity, the product usage is not affected. However, Veritas recommends that in such cases, you must procure or renew your license to a higher capacity.

  • If you fail to procure or renew your license before the expiry date, a grace period of 60-days is provided without any effect on the product usage.

  • If you fail to procure or renew your license after the grace period, the services fails to start after a system restart or when services such as, CIFS, S3, NFS, and FTP are restarted.

  • Veritas reserves the right to ensure entitlement and compliance through auditing.

  • If you encounter problems while licensing this product, visit the Veritas Licensing Support website.

    https://www.veritas.com/licensing/process

Table: Functional enforcements of Veritas Access licensing

Enforcement

Action

During Validity

None

During Grace period

Persistent message (in the GUI only)

Post Grace Period

Before you restart the node, you can stop the NFS, CIFS, FTP, and S3 services, but you cannot start the services again (even if you have not restarted the node).

After you restart the node, the NFS, CIFS, FTP, and S3 services do not come online on the restarted node.

If you add the Veritas Access license using the GUI:

  • When a node is restarted after the license has expired, the NFS, CIFS, FTP, and S3 services are stopped on that node. The status of the service appears online if the service is running anywhere in the cluster, even if it is offline on this node. Check the alerts on each node individually to see if the service is online or offline locally.

  • An option to start, stop, and check the status of NFS, CIFS, and S3 services is available. You cannot start, stop, or check the status of the FTP service.

  • You can only provide the license file from the local system, the scp path is not supported through the GUI.

If you add the Veritas Access license using the CLISH:

  • When a node is restarted after the license has expired, the NFS, CIFS, FTP, and S3 services are stopped on that node. You can use the support services show command to display the node-wise status of the service.

  • An option to start, stop, and check the status of NFS, CIFS, FTP, and S3 services is available.

  • You can add the license using the license add command. The license add command provides support for scp path as well.

  • The license list and license list details commands provide details for the license that is installed on each node of the cluster.