Veritas Access 7.3 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
- About Flexible Storage Sharing
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your 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 Veritas Access to work with Oracle Direct NFS
- Configuring an FTP server
- 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
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Configuring cloud storage
- Configuring the cloud gateway
- Configuring cloud as a tier
- About policies for scale-out file systems
- Section IX. 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
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring replication
- Replication job failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring Veritas Access with the NetBackup client
- Section XI. Reference
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]