Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
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 | Getting Started wizard with operations for managing the Veritas Access 3340 Appliance Centralized dashboard and Quick Actions 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) | 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 |
---|---|
Supported protocols | Veritas Access includes support for the following protocols:
|
WORM storage for Enterprise Vault Archiving over CIFS | 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 Solutions Guide for Enterprise Vault. |
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 Solutions Guide for Enterprise Vault. |
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. See About managing application I/O workloads using maximum IOPS settings. |
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:
See Read performance tunables for a cloud tier in 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, and IBM Cloud Object Storage based on automated policies. You can also retrieve data archived in Amazon Glacier. See Configuring the cloud as a tier for scale-out file systems. |
SmartIO | Veritas Access supports read 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. See About snapshots. |
Deduplication | Using Veritas Data Deduplication Veritas Access participates in a NetBackup Media Server Deduplication Pool-based backup policy by storing and indexing deduplicated blocks for a NetBackup server. See the Veritas Access Solutions Guide for NetBackup for more information. In cases where Veritas Access is used to store deduplicated backup data from another source, there is no need to set up a separate deduplication mechanism. Note: It is recommended to use Veritas Deduplication for long-term data retention instead of the OpenDedup solution. |
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 the NFS use case. |
Veritas Access as an iSCSI target for RHEL 7.x | Veritas Access as an iSCSI target can be configured to serve block storage. An iSCSI target as service is hosted in an active-active mode in the Veritas Access cluster. |
Configuring Veritas Access in IPv4 and IPv6 mixed mode | Support for configuring the Veritas Access cluster in an IPv4 environment, or an IPV6 environment, or in a mixed mode environment where you have both IPv4 and IPv6 addresses. |
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. See the Veritas Access Solutions Guide for NetBackup for more information. |
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 About Veritas Access episodic replication. See the episodic(1) man page for more information. Synchronous replication of data over IP networks See About Veritas Access continuous replication. 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. See About configuring LDAP settings. |
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:
|