Veritas Access Installation Guide
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux requirements
- Linux requirements
- Network and firewall requirements
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- 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
- 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
About Veritas Access
Veritas Access is a software-defined scale-out network-attached storage (NAS) solution for unstructured data that works on commodity hardware. Veritas Access provides resiliency, multi-protocol access, and data movement to and from the public or private cloud based on policies.
You can use Veritas Access in any of the following ways.
Table: Interfaces for using Veritas Access
Interface | Description |
---|---|
GUI | Centralized dashboard with operations for managing your storage. See the GUI and the Online Help for more information. |
RESTful APIs | Enables automation using scripts, which run storage administration commands against the Veritas Access cluster. See the Veritas Access RESTful API Guide for more information. |
Command-line interface (CLI or CLISH) | Single point of administration for the entire cluster. See the manual pages for more information. |
Table: Veritas Access key features describes the features of Veritas Access.
Table: Veritas Access key features
Feature | Description |
---|---|
Multi-protocol access | Veritas Access includes support for the following protocols:
|
WORM storage for Enterprise Vault Archiving | Veritas Access can be configured as WORM primary storage for archival by Enterprise Vault. Veritas Access is certified as a CIFS primary WORM storage for Enterprise Vault 12.1. For more information, see the Veritas Access Enterprise Vault Solutions Guide. |
WORM support over NFS | Veritas Access supports WORM over NFS. |
Creation of Partition Secure Notification (PSN) file for Enterprise Vault Archiving | A Partition Secure Notification (PSN) file is created at a source partition after the successful backup of the partition at the remote site. For more information, see the Veritas Access Enterprise Vault Solutions Guide. |
Managing application I/O workloads using maximum IOPS settings | The MAXIOPS limit determines the maximum number of I/Os processed per second collectively by the storage underlying the file system. |
Flexible Storage Sharing (FSS) | Enables cluster-wide network sharing of local storage. |
Scale-out file system | The following functionality is provided for a scale-out file system:
|
Cloud as a tier for a scale-out file system | Veritas Access supports adding a cloud service as a storage tier for a scale-out file system. You can move data between the tiers based on file name patterns and when the files were last accessed or modified. Use scheduled policies to move data between the tiers on a regular basis. Veritas Access moves the data from the on-premises tier to Amazon S3, Amazon Glacier, Amazon Web Services (AWS), GovCloud (US), Azure, Google cloud, Alibaba, Veritas Access S3, IBM Cloud Object Storage, and any S3-compatible storage provider based on automated policies. You can also retrieve data archived in Amazon Glacier. |
SmartIO | Veritas Access supports both read and writeback caching on solid state drives (SSDs) for applications running on Veritas Access file systems. |
SmartTier | Veritas Access's built-in SmartTier feature can reduce the cost of storage by moving data to lower-cost storage. Veritas Access storage tiering also facilitates the moving of data between different drive architectures and on-premises. |
Snapshot | Veritas Access supports snapshots for recovering from data corruption. If files, or an entire file system, are deleted or become corrupted, you can replace them from the latest uncorrupted snapshot. |
Deduplication | You can run post-process periodic deduplication in a file system, which eliminates duplicate data without any continuous cost. |
Compression | You can compress files to reduce the space used, while retaining the accessibility of the files and having the compression be transparent to applications. Compressed files look and behave almost exactly like uncompressed files: the compressed files have the same name, and can be read and written as with uncompressed files. |
Erasure-coding | Erasure-coding is configured with the EC log option for NFS use case. |
IP load balancing | With IP load balancing, a single virtual IP is used to act as a load balancer IP which distributes the incoming requests to the different nodes in the Veritas Access cluster for the services that are run on an active-active cluster. |
iSCSI target | Veritas Access as an iSCSI target can be configured to serve block storage. iSCSI target as service is hosted in an active-active mode in the Veritas Access cluster. |
NetBackup integration | Built-in NetBackup client for backing up your file systems to a NetBackup master or media server. Once data is backed up, a storage administrator can delete unwanted data from Veritas Access to free up expensive primary storage for more data. |
OpenStack plug-in | Integration with OpenStack:
|
Quotas | Support for setting file system quotas, user quotas, and hard quotas. |
Replication | Periodic replication of data over IP networks. See the episodic(1) man page for more information. Synchronous replication of data over IP networks See the continuous(1) man page for more information. |
Support for LDAP, NIS, and AD | Veritas Access uses the Lightweight Directory Access Protocol (LDAP) for user authentication. |
Partition Directory | With support for partitioned directories, directory entries are redistributed into various hash directories. These hash directories are not visible in the name-space view of the user or operating system. For every new create, delete, or lookup, this feature performs a lookup for the respective hashed directory and performs the operation in that directory. This leaves the parent directory inode and its other hash directories unobstructed for access, which vastly improves file system performance. By default this feature is not enabled. See the storage_fs(1) manual page to enable this feature. |
Isolated storage pools | Enables you to create an isolated storage pool with a self-contained configuration. An isolated storage pool protects the pool from losing the associated metadata even if all the configuration disks in the main storage pool fail. |
Performance and tuning | Workload-based tuning for the following workloads:
|