Please enter search query.
Search <book_title>...
Veritas Access Administrator's Guide
Last Published:
2021-04-15
Product(s):
Access (7.4.2)
Platform: Linux
- 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 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
- IP load balancing
- Configuring Veritas Access in IPv4 and IPv6 mixed mode
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- About storage provisioning and management
- About configuring disks
- About configuring storage pools
- Configuring storage pools
- About quotas for usage
- 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 quotas for CIFS home directories
- About Flexible Storage Sharing
- Limitations of Flexible Storage Sharing
- Configuring erasure coding for a Flexible Storage Sharing file system
- Workflow for configuring and managing storage using the Veritas Access CLI
- Displaying information for all disk devices associated with the nodes in a cluster
- Displaying WWN information
- Importing new LUNs forcefully for new or existing pools
- Initiating host discovery of LUNs
- Increasing the storage capacity of a LUN
- Formatting or reinitializing a disk
- Removing a disk
- 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
- About using the 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
- 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 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 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
- File sharing for a scale-out file system using FTP
- 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
- About creating and maintaining file systems
- About scale-out file systems
- Read performance tunables for a cloud tier in a scale-out file system
- About encryption at rest
- Considerations for creating a file system
- Best practices for creating file systems
- Choosing a file system layout type
- Determining the initial extent size for a file system
- About striping file systems
- About creating a tuned file system for a specific workload
- About FastResync
- About fsck operation
- Setting retention in files
- Setting WORM over NFS
- Manually setting WORM-retention on a file over CIFS
- About managing application I/O workloads using maximum IOPS settings
- 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 VII. Configuring cloud storage
- Configuring the cloud gateway
- Configuring cloud as a tier
- Section VIII. 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
- Displaying CIFS share properties
- Hiding system files when adding a CIFS normal share
- 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
- Creating CIFS shares for a scale-out file system
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. 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
- Showing the scheduled compression job
- Scheduling compression jobs
- Listing compressed files
- 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
- Configuring the policy of each tiered file system
- 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
- 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
- Verifying the VxFS cache area and monitoring the caching
- Setting the caching mode
- Customizing the caching behavior
- Viewing the caching statistics for a cache area
- Configuring episodic replication
- About Veritas Access episodic replication
- How Veritas Access episodic replication works
- Starting Veritas Access episodic replication
- Setting up communication between the source and the destination clusters
- Setting up the file systems to replicate
- Setting up files to exclude from an episodic replication unit
- Scheduling the episodic replication
- Defining what to replicate
- About the maximum number of parallel episodic replication jobs
- Managing an episodic replication job
- Replicating compressed data
- Displaying episodic replication job information and status
- Synchronizing an episodic replication job
- Behavior of the file systems on the episodic replication destination target
- Accessing file systems configured as episodic replication destinations
- Episodic replication job failover and failback
- Configuring continuous replication
- About Veritas Access continuous replication
- How Veritas Access continuous replication works
- Starting Veritas Access continuous replication
- Setting up communication between the source and the destination clusters
- Setting up the file system to replicate
- Managing continuous replication
- Displaying continuous replication information and status
- Unconfiguring continuous replication
- Continuous replication 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
- Section X. Reference
- Index
Setting up deduplication
This is an end-to-end sample scenario of deduplication.
To deduplicate data
- Ensure that the file system is deduplication-enbled. For example:
Storage> dedup list
See Configuring deduplication.
If the file system is not deduplication-enbled, you will need to enable it. For example:
Storage> dedup enable fs_name blksize
- (Optional) Once deduplication is enabled, you can set the CPU usage, the memory, and priority for the deduplication-enabled file system.
- Veritas recommends running a dryrun.
The dryrun provides you the space savings in percentage, if the threshold value is provided then the fsdedup command deduplicates data only if the expected savings cross the specified threshold.
Storage> dedup dryrun fs_name [threshold]
See Manually running deduplication.
Note:
You cannot perform a dryrun on a file that has already been deduplicated.
- You can either choose to start deduplication now or set up the deduplication schedule:
To start deduplication now
Start deduplication now. For example:
Storage> dedup start fs_name [nodename]
See Manually running deduplication.
Note:
If the system where you started deduplication crashes, the deduplication job fails over to one of the other nodes in the cluster. Run the dedup status fs_name command to find out the status. The dedup status command can temporarily show status as "FAILOVER" which means dedup job is currently being failed over and will resume shortly. dedup failover is applicable for deduplication jobs started with the dedup start command only. It is not applicable for scheduled dedup jobs.
To set up the deduplication schedule
Set up the deduplication schedule. For example:
Storage> dedup schedule set fs_name hours day [freq]
- You can check the status of the deduplication process. For example:
Storage> dedup status [fs_name]