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
Troubleshooting pre-upgrade issues for LTR
Following are the pre-upgrade scenarios with the recommended workaround:
Failure in provisioning of
odd_cache_fs: Ensure that sufficient storage space is available in default pool(s) that is configured for Objectaccess.
Failure in backup of configuration file
: Ensure that the
odd_vipgrp_map.conffile is successfully copied to/shared/opendedup/.Failure in backup of XML configuration files
: Ensure that all the OpenDedup volume configuration XML files are successfully copied to
/shared/opendedup/sdfs/.Failure in shutdown of OpenDedup volume(s)
:
Ensure that the volume is unmounted by using the mount -t fuse command.
Ensure all the jsvc processes are stopped. If the processes are not stopped, use the kill command to stop them.
Shutdown of the OpenDedup volume may result in java stack trace to be printed on console. This can be ignored as long as the volume is unmounted.
Failure in backup of the OpenDedup cache data
: Ensure that the size of the local cache location, that is,
/opt/sdfs/ volumes/<vol-name>is equivalent to the shared cache location, that is,/vx/odd_cache_fs/volumes/<vol-name>.