Veritas Access Online Help
- Getting started
- About Veritas Access
- Enabling certificate-based authentication in Veritas Access
- About the dashboard
- Setting up the storage type for provisioning
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- About the NFS shares
- About an iSCSI target
- Creating an iSCSI target and provisioning LUNs
- About S3 buckets for NetBackup
- Using the Veritas Access product documentation
- Changing your password
- Important release information
- Managing storage
- About storage provisioning and management
- Adding disks to a storage pool
- Removing disks from a storage pool
- Removing disks from a cluster
- Viewing information about disks
- Accessing disk details
- Adding or removing a node
- Viewing information about a node in a cluster
- Accessing node details
- Configuring a disk
- Increasing the size of a disk
- Running scanbus
- Formatting a disk
- Marking a disk as spare
- About SmartIO for solid-state drives
- About storage provisioning and management
- Managing file sharing services
- Monitoring and troubleshooting
- Provisioning and managing file systems
- About scale-out file systems
- Generating the long-term data retention script
- Creating a file system
- Setting the maximum IOPS
- Creating a snapshot
- Restoring a snapshot
- Configuring a replication job
- Stopping or starting a replication job for VVR
- Pausing and resuming a replication job for VVR
- Enabling or disabling a replication job for VFR
- Synchronizing a replication job for VFR
- Failing over or failing back a replication job for VVR
- Failing over or failing back a replication job for VFR
- Unconfiguring a replication job for VFR
- Unconfiguring a replication job for VVR
- Viewing the list of iSCSI targets
- Adding an initiator for an iSCSI target
- Removing an initiator for an iSCSI target
- Adding portal IPs for an iSCSI target
- Setting up authentication for an iSCSI target
- Viewing the list of initiators for an iSCSI target
- Viewing the portal IPs for an iSCSI target
- Removing portal IPs for an iSCSI target
- Removing authentication settings for an iSCSI target
- Removing an iSCSI target
- Removing the file system store for an iSCSI target
- Viewing the list of LUNs for an iSCSI target
- Creating a LUN for an iSCSI target
- Increasing the size of a LUN for an iSCSI target
- Reducing the size of a LUN for an iSCSI target
- Removing a LUN for an iSCSI target
- Cloning a LUN for an iSCSI target
- Creating a snapshot of a LUN for an iSCSI target
- Viewing the list of snapshots for an iSCSI target
- Removing a LUN snapshot
- Restoring a LUN snapshot
- Provisioning and managing shares
- About file sharing protocols
- About concurrent access
- About concurrent access with NFS and S3
- Sharing directories using CIFS and NFS protocols
- Adding a share
- NFS protocol options
- CIFS protocol options
- About buckets and objects
- About Active Directory (AD)
- Logging on as an active directory user
- Creating access and secret keys for an active directory user
- Exporting an NFS share as an S3 bucket
- Viewing information about a share
- Accessing share details
- Configuring a favorite share
- Deleting a share
- Managing permissions for CIFS shares
- Managing clients for the NFS shares
- Managing policies
- About policies for storage provisioning
- About policies for long-term data retention
- About policies for archiving data using Enterprise Vault
- About policies for file systems
- About pattern matching for data movement policies
- Viewing information about policies
- Activating storage policy templates
- Activating long-term data retention policies
- Activating archival policies
- Creating an S3 bucket
- About cloud-storage tiering
- Adding a cloud tier for a scale-out file system
- About tiering policies
- Adding a secondary tier
- Viewing information about the secondary tier
- Adding or editing a tier policy on a secondary tier
- Creating a policy schedule
- Managing settings
- Viewing Veritas Access settings
- About the cloud gateway
- Viewing information about cloud services
- Adding and removing a cloud service
- Viewing discovery information about your cluster
- About the Lightweight Directory Access Protocol
- Configuring LDAP
- Configuring Active Directory
- About user management
- Managing local users
- Configuring the NTP server
- Starting or stopping the CIFS or NFS servers
- Starting or stopping the S3 server
- Adding or removing storage pools for S3 users
- Configuring the /etc/hosts file for mapping of S3 users
- Switching between NFS servers
- Accessing the RESTful APIs
- Registering a NetBackup master server or an EMM server
- Modifying a NetBackup media server list
- Viewing information about your NetBackup configuration with Veritas Access
- About cluster management
- Setting up the time and the time zone for the cluster
- About replication
- Viewing information about events
- Purging events
- About Veritas Access product licensing
- Configuring SmartIO
- Viewing information about SmartIO
- Setting object server default parameters
- Setting up the object server group-specific parameters
- Viewing information about S3
- About IP load balancing
- Configuring the KMS server
- About the CIFS service management
- Setting up the home directory
- About the File Transfer Protocol
- About Veritas Data Deduplication
- About alert management
- Index
About scale-out file systems
A scale-out file system consists of a set of on-premises file systems and set of cloud tier(s) all exposed in a single name space. One on-premises file system stores the metadata (including the attributes) and all the other file systems store the data. Data is distributed among the file systems using a consistent hashing algorithm. This separation of metadata and data allows the scale-out file system to scale linearly.
Veritas Access supports access to scale-out file systems using NFS-Ganesha, S3, CIFS and FTP.
Scale-out file system specifications:
Twenty percent of a scale-out file system's size is devoted to the metadata file system.
The maximum size of a metadata file system is 10 TB.
The minimum size of a scale-out file system is 10 GB.
The maximum size of a scale-out file system is 3 PB.
To create a scale-out file system above 522 TB, you need to provide the file system size in multiples of 128 GB.
You can grow a scale-out file system up to 3 PB.
To create or grow a scale-out file system above 522 TB, you need to provide the file system size in multiples of 128 GB.
Note:
Growing a scale-out file system beyond 522 TB creates additional data file systems (based on the grow size), and data movement is triggered from the old file systems to the newly added file systems, so that data is distributed evenly among all the data file systems.
You can shrink the scale-out file system only if its size is less than 522 TB.
Access the data present in a scale-out file system using NFS (both v3 and v4), S3 (supports both AWS signature version 2 and version 4), CIFS and FTP protocols.
Ability to tier infrequently accessed data to the cloud using the cloud as a tier feature:
There can be only one on-premises tier.
There can be up to eight cloud tiers per a scale-out file system.
You can move data between cloud tiers, for example, moving data from Azure to Glacier.
Configure policies to move data from or to on-premises or cloud tiers.
Policies can be configured based on the access time, modification time, or pattern.
Azure has a limitation of 500 TB per storage account. Azure users can have 200 storage accounts per subscription. A scale-out file system supports adding multiple Azure storage accounts in a single tier. Effectively, you can attach 100 PB of Azure storage to a single tier. When multiple storage accounts are used, Veritas Access selects one of the storage accounts to store data in a round-robin manner.
A scale-out file system can be configured for synchronous or asynchronous replication. Synchronous replication provides zero RPO for applications. Asynchronous replication provides non-zero RPO while providing improved performance compared to synchronous replication. This replication feature works even with cloud tier.
New data file systems are created when you grow the scale-out file system beyond 522 TB. The pool on which the scale-out file system is created is used to create these new file systems. There is also data movement to these new file systems so that data is distributed evenly among all the file systems (on-premises).
The following types of clouds can be added as storage tiers for a scale-out file system:
Amazon S3
Amazon Glacier
Amazon GovCloud (US)
Azure
Google cloud
Alibaba
IBM Cloud Object Storage
Veritas Access S3
If you want to add any other S3-compatible storage, then it can be qualified with Veritas Access and used.
The data is always written to the on-premises storage tier and then data can be moved to the cloud using a tiering mechanism. File metadata including any attributes set on the file resides on-premises even though the file is moved to the cloud. This cloud as a tier feature is best used for moving infrequently accessed data to the cloud.
Amazon Glacier is an offline cloud tier, which means that data moved to Amazon Glacier cannot be accessed immediately. An EIO error is returned if you try to read, write, or truncate the files moved to the Amazon Glacier tier. If you want to read or modify the data, move the data to on-premises using tier move or using policies. The data is available after some time based on the Amazon Glacier retrieval option you selected.
When Amazon S3, AWS GovCloud(US), Azure, Google cloud, Alibaba, IBM Cloud Object Storage, or Veritas Access S3 is used as the cloud tier, the data present on these clouds can be accessed any time (unlike in Amazon Glacier). An EIO error is returned if you try to write, or truncate the files moved to these clouds. If you want to modify the data, move the data to on-premises using tier move or using policies.
See the Veritas Access Cloud Storage Tiering Solutions Guide for more information.
Note:
Veritas Access support the CIFS protocol with a scale-out file system.