Working with Non-Dedupe File Types

Article ID: DD0074 Working with Non-Dedupe File Types


Working with Non-Dedupe File Types

Best Practices

One of the best practices recommended for better deduplication is to keep similar type files together in the same storage policy. For example; you might group together subclients containing database files into one storage policy and subclients containing regular files into another.

However, some files, such as compressed, video, and image files don’t deduplicate well at all. These types of files rarely, if ever, change after creation and would be best handled by an incremental forever approach to a non-deduplicated storage policy with days-only retention.

If, on the chance, cycle retention is used and a synthetic full is required for aging or space reclamation, then a dedupe storage policy can be used with very large block size.  This would allow the use of a DASH synthetic full to minimize disk IO on the media.

Additionally, you should carefully weigh the use of compression with these file types to save media space.  In some cases, compressing files that are already compressed can slightly expand the file size