Veritas Access 7.3 Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- About configuring the Veritas Access network
- About bonding Ethernet interfaces
- Bonding Ethernet interfaces
- Configuring DNS settings
- About the IP addresses for the Ethernet interfaces
- About Ethernet interfaces
- Displaying current Ethernet interfaces and states
- Configuring IP addresses
- Configuring Veritas Access to use jumbo frames
- Configuring VLAN interfaces
- Configuring NIC devices
- Swapping network interfaces
- Excluding PCI IDs from the cluster
- About configuring routing tables
- Configuring routing tables
- Changing the firewall settings
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- About storage provisioning and management
- Displaying information for all disk devices associated with the nodes in a cluster
- About configuring storage pools
- Configuring storage pools
- About quotas for usage
- About quotas for CIFS home directories
- Enabling, disabling, and displaying the status of file system quotas
- Setting and displaying file system quotas
- Setting user quotas for users of specified groups
- About Flexible Storage Sharing
- Workflow for configuring and managing storage using the Veritas Access CLI
- Displaying WWN information
- Initiating host discovery of LUNs
- Importing new LUNs forcefully for new or existing pools
- Increasing the storage capacity of a LUN
- About configuring disks
- Configuring disks
- Formatting or reinitializing a disk
- Removing a disk
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your NFS server
- About using NFS server with Veritas Access
- Using the kernel-based NFS server
- Using the NFS-Ganesha server
- Switching between NFS servers
- Recommended tuning for NFS-Ganesha version 3 and version 4
- Accessing the NFS server
- Displaying and resetting NFS statistics
- Configuring Veritas Access for ID mapping for NFS version 4
- Configuring the NFS client for ID mapping for NFS version 4
- About authenticating NFS clients
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About configuring Veritas Access for CIFS
- About configuring CIFS for standalone mode
- Configuring CIFS server status for standalone mode
- Changing security settings
- Changing security settings after the CIFS server is stopped
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- Setting NTLM
- About setting trusted domains
- Specifying trusted domains that are allowed access to the CIFS server
- Allowing trusted domains access to CIFS when setting an IDMAP backend to rid
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ldap
- Allowing trusted domains access to CIFS when setting an IDMAP backend to hash
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ad
- About configuring Windows Active Directory as an IDMAP backend for CIFS
- Configuring the Active Directory schema with CIFS-schema extensions
- Configuring the LDAP client for authentication using the CLI
- Configuring the CIFS server with the LDAP backend
- Setting Active Directory trusted domains
- About storing account information
- Storing user and group accounts
- Reconfiguring the CIFS service
- About mapping user names for CIFS/NFS sharing
- About the mapuser commands
- Adding, removing, or displaying the mapping between CIFS and NFS users
- Automatically mapping of UNIX users from LDAP to Windows users
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- Setting the CIFS aio_fork option
- About managing local users and groups
- Enabling CIFS data migration
- Configuring Veritas Access to work with Oracle Direct NFS
- About using Veritas Access with Oracle Direct NFS
- About the Oracle Direct NFS architecture
- About Oracle Direct NFS node or storage connection failures
- Configuring an Oracle Direct NFS storage pool
- Configuring an Oracle Direct NFS file system
- Configuring an Oracle Direct NFS share
- Best practices for improving Oracle database performance
- Configuring an FTP server
- About FTP
- Creating the FTP home directory
- Using the FTP server commands
- About FTP server options
- Customizing the FTP server options
- Administering the FTP sessions
- Uploading the FTP logs
- Administering the FTP local user accounts
- About the settings for the FTP local user accounts
- Configuring settings for the FTP local user accounts
- Configuring your NFS server
- Section V. Managing the Veritas Access Object Store server
- Section VI. Monitoring and troubleshooting
- Section VII. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- About creating and maintaining file systems
- Considerations for creating a file system
- Best practices for creating file systems
- About scale-out file systems
- Characteristics of a scale-out file system
- About striping file systems
- About creating a tuned file system for a specific workload
- About FastResync
- About scale-out fsck
- About setting retention in files
- About managing application I/O workloads using maximum IOPS settings
- Choosing a file system layout type
- Determining the initial extent size for a file system
- Creating a file system
- Bringing the file system online or offline
- Listing all file systems and associated information
- Modifying a file system
- Managing a file system
- Destroying a file system
- Upgrading disk layout versions
- Creating and maintaining file systems
- Section VIII. Configuring cloud storage
- Configuring the cloud gateway
- Configuring cloud as a tier
- Configuring the cloud as a tier feature for scale-out file systems
- Moving files between tiers in a scale-out file system
- About policies for scale-out file systems
- Obtaining statistics on data usage in the cloud tier in scale-out file systems
- Workflow for moving on-premises storage to cloud storage for NFS shares
- Section IX. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About NFS file sharing
- Displaying file systems and snapshots that can be exported
- Exporting an NFS share
- Displaying exported directories
- About managing NFS shares using netgroups
- Unexporting a directory or deleting NFS options
- Exporting an NFS share for Kerberos authentication
- Mounting an NFS share with Kerberos security from the NFS client
- Exporting an NFS snapshot
- Creating and maintaining CIFS shares
- About managing CIFS shares
- Exporting a directory as a CIFS share
- Configuring a CIFS share as secondary storage for an Enterprise Vault store
- Exporting the same file system/directory as a different CIFS share
- About the CIFS export options
- Setting share properties
- Hiding system files when adding a CIFS normal share
- Displaying CIFS share properties
- Allowing specified users and groups access to the CIFS share
- Denying specified users and groups access to the CIFS share
- Exporting a CIFS snapshot
- Deleting a CIFS share
- Modifying a CIFS share
- Making a CIFS share shadow copy aware
- Using Veritas Access with OpenStack
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Use cases for compressing files
- Best practices for using compression
- Compression tasks
- Compressing files
- Scheduling compression jobs
- Listing compressed files
- Showing the scheduled compression job
- Uncompressing files
- Modifying the scheduled compression
- Removing the specified schedule
- Stopping the schedule for a file system
- Removing the pattern-related rule for a file system
- Removing the modified age related rule for a file system
- Configuring SmartTier
- About Veritas Access SmartTier
- How Veritas Access uses SmartTier
- Adding tiers to a file system
- Adding or removing a column from a secondary tier of a file system
- Configuring a mirror to a tier of a file system
- Listing all of the files on the specified tier
- Displaying a list of SmartTier file systems
- About tiering policies
- About configuring the policy of each tiered file system
- Configuring the policy of each tiered file system
- Best practices for setting relocation policies
- Relocating a file or directory of a tiered file system
- Displaying the tier location of a specified file
- About configuring schedules for all tiered file systems
- Configuring schedules for tiered file systems
- Displaying the files that may be moved or pruned by running a policy
- Allowing metadata information on the file system to be written on the secondary tier
- Restricting metadata information to the primary tier only
- Removing a tier from a file system
- Configuring SmartIO
- About SmartIO for solid-state drives
- About configuring SmartIO
- About SmartIO read caching for applications running on Veritas Access file systems
- Setting up SmartIO read caching for Veritas Access
- About SmartIO writeback caching for applications running on Veritas Access file systems
- Setting up SmartIO writeback caching for VxFS file systems
- Tuning the writeback caching
- Flushing dirty data from a writeback cache area
- Setting the caching mode
- Customizing the caching behavior
- Viewing the caching statistics for a cache area
- Verifying the VxFS cache area and monitoring the caching
- Configuring replication
- About Veritas Access file-level replication
- How Veritas Access replication works
- About Veritas Access sync replication
- How Veritas Access sync replication works
- Starting Veritas Access replication
- Setting up communication between the source and the destination clusters
- Setting up the file systems to replicate
- Setting up files to exclude from a replication unit
- Scheduling the replication
- Defining what to replicate
- About the maximum number of parallel replication jobs
- Managing a replication job
- Replicating compressed data
- Displaying replication job information and status
- Synchronizing a replication job
- Behavior of the file systems on the replication destination target
- Accessing file systems configured as replication destinations
- Creating a recovery point objective (RPO) report
- Replication job failover and failback
- Using snapshots
- Using instant rollbacks
- About instant rollbacks
- Creating a space-optimized rollback
- Creating a full-sized rollback
- Listing Veritas Access instant rollbacks
- Restoring a file system from an instant rollback
- Refreshing an instant rollback from a file system
- Bringing an instant rollback online
- Taking an instant rollback offline
- Destroying an instant rollback
- Creating a shared cache object for Veritas Access instant rollbacks
- Listing cache objects
- Destroying a cache object of a Veritas Access instant rollback
- Configuring Veritas Access with the NetBackup client
- About Veritas Access as a NetBackup client
- Prerequisites for configuring the NetBackup client
- About the NetBackup Snapshot Client
- About NetBackup snapshot methods
- About NetBackup instant recovery
- Enabling or disabling the NetBackup SAN client
- Workflow for configuring Veritas Access for NetBackup
- Registering a NetBackup master server, an EMM server, or adding an optional media server
- Displaying the excluded files from backup
- Displaying the included and excluded files for backups
- Adding or deleting patterns to the list of files in backups
- Configuring or resetting the virtual IP address used by NetBackup
- Configuring the virtual name of NetBackup
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Performing a backup or restore of a Veritas Access file system over a NetBackup SAN client
- Performing a backup or restore of a snapshot
- Installing or uninstalling the NetBackup client
- Configuring Veritas Access for NetBackup cloud storage
- Section XI. Reference
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.
Unlike a standard file system, a scale-out file system is Active/Passive, which means that the file system can be online on only one node of the cluster at a time. A scale-out file system is always active on the node where its virtual IP address is online. A virtual IP address is associated with a scale-out file system when the file system is created.
Veritas Access supports access to scale-out file systems using NFS-Ganesha and S3. NFS shares that are created on scale-out file systems must be mounted on the NFS clients using the virtual IP address that is associated with the scale-out file system, similarly S3 buckets created on a scale-out file system must be accessed using the same virtual IP address.
You can find the virtual IP address associated with a scale-out file system by using the NFS> share show command or by using the objectaccess> bucket show command based on the protocol that you are using.
S3 buckets created on a scale-out file system must be accessed using virtual-hosted-style URL (rather than the path-style URL) and the S3 client's DNS must be updated to this virtual IP address for the corresponding virtual-hosted-style URL. If a bucket "bucket1" is created by the S3 client, then its virtual-hosted-style URL would be "bucket1.s3.cluster_name:8143," where the cluster_name is the Veritas Access cluster name and 8143 is the port on which the Veritas Access S3 server is running.
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) and S3 (supports both AWS signature version 2 and version 4).
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.
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
Alibaba
Google cloud
IBM Cloud Object Storage
Veritas Access S3 and any S3-compatible storage provider
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, Veritas Access S3 and any S3-compatible storage provider 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.
See Characteristics of a scale-out file system.
Note:
You cannot use the CIFS protocol with a scale-out file system.
See Configuring the cloud as a tier feature for scale-out file systems.