Help on File System > Deduplication > Summary
The following information and controls appear on
.- Used Space
- Displays the amount of storage space that is currently consumed by data on the cluster followed by the total amount of storage space on the cluster.
- Deduplicated Data
- Displays the total amount of storage space that deduplicated data is currently occupying followed by the amount of storage space that the data originally occupied.
- Savings From Deduplication
- Displays the total amount of storage space that was saved by deduplication.
- Space Savings
- The total amount of physical disk space saved by deduplication, including protection overhead and metadata. For example, if you have three identical files that are all 5 GB, the estimated physical savings would be greater than 10 GB because deduplication saved space that would have been occupied by file metadata and protection overhead.
- Other Data
- The amount of space on the cluster occupied by directories that were not deduplicated.
- Start Deduplication Job
- Links to the page.
- Deduplication Reports
- This table describes deduplication reports.
- Job ID
- Displays the job ID of the deduplication job that created the report.
- Job Type
- Displays the type of the deduplication job that created the report.
- Time
- Displays the time that the deduplication job started.
- Duration
- Displays how long the deduplication job ran.
- Savings
- Displays the percentage of scanned blocks that were deduplicated.
- Action
- Displays actions that can be performed for a report.
- View Report
- Displays the contents of a deduplication report.
- Job ID
- Displays the job ID of the deduplication job that created the report.
- Job Type
- Displays the type of deduplication job that created the report.
- Time
- Displays the time that the deduplication job started.
- Duration
- Displays how long the deduplication job ran.
- Savings
- Displays the percentage of scanned blocks that were deduplicated.
- Start time
- Displays the time the deduplication job started.
- End time
- Displays the time the deduplication job ended.
- Iteration count
- Displays the number of times that the deduplication job interrupted the sampling process. If the deduplication job samples a large amount of data, the deduplication job might interrupt sampling in order to start deduplicating the data. After the deduplication job finishes deduplicating the sampled data, the job will continue sampling the remaining data.
- Scanned blocks
- Displays the total number of blocks located underneath the specified deduplicated directories.
- Sampled blocks
- Displays the number of blocks that the deduplication job created index entries for.
- Deduped blocks
- Displays the number of blocks that were deduplicated.
- Dedupe percent
- Displays the percentage of scanned blocks that were deduplicated.
- Created dedupe requests
- Displays the total number of deduplication requests created. A deduplication request is created for each matching pair of data blocks. For example, if you have 3 data blocks that all match, the deduplication job creates 2 requests. One of the requests could pair file1 and file2 together and the other request could pair file2 and file3 together.
- Successful dedupe requests
- Displays the number of deduplication requests that completed successfully.
- Unsuccessful dedupe requests
- Displays the number of deduplication requests that failed. If a deduplication request fails, it does not mean that the job failed too. A deduplication request can fail for any number of reasons. For example, the file might have been modified since it was sampled.
- Skipped files
- Displays the number of files that were not scanned by the deduplication job. SmartDedupe skips files for a number of reasons. For example, SmartDedupe skips files that have already been scanned and haven't been modified since. SmartDedupe also skips all files that are smaller than 4 KB.
- Index entries
- Displays the number of entries that currently exist in the index.
- Index lookup attempts
- Displays the total number of lookups that have been done by earlier deduplication jobs plus the number of lookups done by this deduplication job. A lookup is when the deduplication job attempts to match a block that was indexed with a block that hasn't been indexed.
- Index lookup hits
- Displays the number of blocks that matched index entries.
- Elapsed time
- Displays how long the deduplication job ran.
- Aborts
- Displays the number of times the job failed to unlink a file. Because deduplication jobs do not unlink files, this field is not relevant to deduplication jobs.
- Errors
- Displays the number of errors that the deduplication job encountered.
- Scanned files
- Displays how many files were scanned by the deduplication job.
- Directories
- Displays how many directories were scanned by the deduplication job.
- CPU usage
- Displays the maximum, minimum, and average amount of CPU used by the deduplication job.
- Virtual memory size
- Displays how much virtual memory was consumed by the deduplication job.
- Resident memory size
- Displays how much physical memory was consumed by the deduplication job.
- Read
- The number of read operations performed by the deduplication job followed by the number of bytes that were read by the deduplication job.
- Write
- The number of write operations performed by the deduplication job followed by the number of bytes that were written by the deduplication job.
- Other jobs read
- The number of read operations and total number of bytes that were read by other job engine jobs while the deduplication job was running.
- Other jobs write
- The number of write operations and total number of bytes that were written by other job engine jobs while the deduplication job was running.
- Non-JE read
- The number of read operations and total number of bytes that were read by non-job-engine operations while the deduplication job was running.
- Non-JE write
- The number of write operations and total number of bytes that were written by non-job-engine operations while the deduplication job was running.