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
- 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
- Creating and maintaining CIFS shares
- 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
- 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
- Section X. Reference
Setting deduplication parameters
To set the CPU usage for the deduplication-enabled file system
- To set the CPU usage for the file system, enter the following:
Storage> dedup set cpu cpuvalue fs_name
cpuvalue
Specify the CPU usage behavior for the deduplication-enabled file system.
The following are the available values:
IDLE - indicates that the deduplication process consumes as much CPU processing as is available. For example, if the CPUs are IDLE, then the deduplication process takes all of the idle CPUs, and performs the deduplication job faster. CPU usage may reach 100% on each available CPU.
YIELD (default) - indicates that the deduplication process yields the CPU periodically; that is, even if the CPUs are not busy, the deduplication process relinquishes the CPU. More time may be taken for the same job in some scenarios. However, the yield value ensures that the deduplication process does not hang onto the CPU, or cause CPU usage spikes.
fs_name
Specify the deduplication-enabled file system for which you want to set the CPU usage.
Note:
If a file system name is specified, the Storage> dedup set cpu command sets the CPU value for that file system. Otherwise, the CPU value is applicable to all file systems, which have not overridden the CPU value.
To set the deduplication memory allocation limit for the deduplication-enabled file system
- To set the deduplication memory limit in MB for the deduplication-enabled file system, enter the following:
Storage> dedup set memory memvalue
where memvalue is the memory value in MB, for example, 1024.
The memvalue controls the maximum memory per deduplication process.
Note:
Care must be taken to increase memvalue if large file systems are present. Otherwise, deduplication efficiency may be affected. Since this is a limit value, only the required memory is consumed for smaller file system deduplication jobs. Note that scheduled deduplication jobs start deduplication based on the available memory; therefore, if available RAM in the system falls below the configured memory allocation limit for deduplication, the deduplication scheduler on that system postpones the scheduled deduplication. At this point, other systems with available memory starts deduplication. If the job remains postponed for 1 hour, the job will be abandoned.
To set the deduplication priority for the deduplication-enabled file system
- To set the deduplication priority (importance) for the deduplication-enabled file system, enter the following:
Storage> dedup set priority priorityvalue [fs_name]
priorityvalue
Specify the importance of deduplication for the file system. The setting of this parameter is local (specific to a file system). The priorityvalue parameter is used by the deduplication scheduler to evaluate if starting deduplication at the scheduled time is appropriate or not based on the state of the file system at that time.
priorityvalue is also a load-balancing mechanism whereby a less-loaded system in the cluster may pick up a scheduled deduplication job.
Available values are the following:
LOW (default) - indicates that if the system has sustained CPU usage of 50% or more in the last one hour, the file systems marked as LOW have their deduplication schedules skipped with a message in the syslog
NORMAL - indicates that if the system has sustained CPU usage of 80% or more in the last one hour, the file systems marked as NORMAL have their deduplication schedules skipped with a message in the syslog
HIGH - indicates that starting deduplication is a must for this file system, and without evaluating any system state, deduplication is started at the scheduled time.
fs_name
Specify the file system where you want to set the deduplication priority.