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
Verifying deduplication
To obtain status information for a specified deduplicated-enabled file system or all deduplicated-enabled file systems
- Enter the following command:
Storage> dedup status [fs_name]
where fs_name is the specified deduplicated-enabled file system for which you want to obtain current status information.
If you issue the command without fs_name, you get status information for all deduplicated-enabled file systems. For example:
If you issue the command with fs_name, you get the detailed status information for the specified file system, along with any error messages or warnings.
The following describes the output from the Storage> dedup status command:
Filesystem
Displays the directory where the file system is mounted.
Savings
Displays the savings as a percentage. The value can mean different things during the course of deduplication.
When the deduplication is in a COMPLETED state, or when the deduplication process is computing the expected deduplication, the value in this column shows the actual sharing in the file system. However, when the expected deduplication calculation is complete, this column value shows the expected deduplication. The expected deduplication calculation is based on user data only; therefore, at the end of deduplication, the saving percentage may vary from the expected deduplication percentage. This is because the actual file system deduplication percentage not only takes into consideration the user data, but also file system and deduplication metadata. This difference may be pronounced if the user data is very small. For a failed deduplication, the value is undefined.
Status
Displays one of the following status values:
RUNNING
COMPLETED
STOPPED
FAILED
FAILOVER
NONE - indicates that deduplication has not been previously run on this file system.
Node
Indicates the node name where the deduplication job is either running or has completed for a file system.
Type
The following are the types of deduplication jobs:
MANUAL - the deduplication job is started by using either the Storage> dedup start command or the Storage> dedup dryrun command.
SCHEDULED - the deduplication job is started by the deduplication scheduler.
Details
Displays the status of the file system deduplication activity.
The deduplication process writes its status in the status log. The relevant status log is displayed in this column. For a long-running deduplication process, the status log may also show the actual file system sharing as a progress indicator. This actual file system sharing percentage along with the expected saving percentage in the Saving column gives a good estimate of the progress. When displaying deduplication status for a specific file system, any errors, or warnings for the deduplication run are also shown. The Details column gives a detailed idea of what to look for in case of any issues.