Veritas Access Installation Guide
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- Important release information
- System requirements
- Linux requirements
- Operating system RPM installation requirements and operating system patching
- Kernel RPMs that are required to be installed with exact predefined RPM versions
- OL kernel RPMs that are required to be installed with exact predefined RPM versions
- Required operating system RPMs for OL 6.8
- Required operating system RPMs for OL 7.3
- Required operating system RPMs for OL 7.4
- Required operating system RPMs for RHEL 6.6
- Required operating system RPMs for RHEL 6.7
- Required operating system RPMs for RHEL 6.8
- Required operating system RPMs for RHEL 7.3
- Required operating system RPMs for RHEL 7.4
- Software requirements for installing Veritas Access in a VMware ESXi environment
- Hardware requirements for installing Veritas Access virtual machines
- Management Server Web browser support
- Supported NetBackup versions
- Supported OpenStack versions
- Supported Oracle versions and host operating systems
- Supported IP version 6 Internet standard protocol
- Linux requirements
- Network and firewall requirements
- Maximum configuration limits
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- Installation overview
- Summary of the installation steps
- Before you install
- Installing the operating system on each node of the cluster
- Installing Veritas Access on the target cluster nodes
- About NIC bonding and NIC exclusion
- About VLAN Tagging
- Replacing an Ethernet interface card
- Configuring I/O fencing
- About configuring Veritas NetBackup
- About enabling kdump during an Veritas Access configuration
- Reconfiguring the Veritas Access cluster name and network
- Configuring a KMS server on the Veritas Access cluster
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading Veritas Access and operating system
- Upgrading Veritas Access using a rolling upgrade
- Uninstalling Veritas Access
- Appendix A. Installation reference
- Appendix B. Troubleshooting the LTR upgrade
- Appendix C. Configuring the secure shell for communications
System requirements
Table: System requirements for Veritas Access lists the per-node system requirements for running the Veritas Access system software.
Table: System requirements for Veritas Access
Minimum | Recommended |
|---|---|
Each Veritas Access node using a 64-bit Intel-based server architecture that is compatible with RHEL 6 Update 6, 7, and 8, RHEL 7 Update 3 and 4 or AMD64 and Intel EMT. Itanium is not supported. | Two nodes of dual or quad core processors at 2.0 GHz or later for optimal performance. |
32 GB error-correcting code (ECC) random-access memory (RAM). | The recommended values depend on the expected workload. |
One internal drive with size equal to size of RAM + 60GB. | Dual boot drives each of size RAM + 60 GB or more capacity. In an FSS-based environment, additional internal drives (SSD + HDD) are recommended. |
Two gigabit Ethernet interfaces | Embedded Ethernet interfaces are recommended. |
Two additional gigabit Ethernet interfaces (Embedded or peripheral component interconnect (PCI) based.) | N/A |
One Fibre Channel Host Bus Adapters (HBA). | Two Fibre Channel Host Bus Adapters (HBAs) are recommended for high availability (HA) if you are using shared LUNs that need to be mapped over a Fibre Channel protocol. If the environment has only DAS or iSCSI disks, then the HBA requirement is optional. |
Internal/external USB DVD-ROM DVD drive. | N/A |
Redundant power supply. | Recommended, but not required. |
SmartIO caching feature | A PCI-based SSD card is recommended if you want to use the SmartIO caching feature. |
Minimum number of servers required is 1 | N/A |