The following table lists the applications that are compatible with Dedupe.
| Application | Interoperability |
|---|---|
| Object Replication | File data is not retained in the deduplicated state when replicating a file system using the Object Replication option. Deduplication is supported on object replication targets from release 13.6. |
| File Replication | File data is not retained in the deduplicated state during file replication. The target file system can have dedupe-enabled, in which case the files on the target will be eventually deduped. |
| Snapshots | Deduped file systems lack exact physical snapshot block usage reporting. There is no way to determine how much physical space is taken up by a given snapshot and, thus, how much will be freed up when they delete a snapshot. Additionally, running kill-snapshots on a deduped file system will leak all snapshot blocks and you will need to take further measures to reclaim the leaked space. snapshot-delete-all is the preferred tool for deleting all snapshots as it does not require the file system to be unmounted, no space is leaked, and it does not affect checkpoint selection. |
| Data Migration | With both local and external migrations, migrated files will be rehydrated. |
| NDMP file-based backup | Files to be deep copied during a NDMP file based backup are restored to single files from tape; a NDMP recovery however cannot be deduped supported or enabled. |
| Sync Image backup | Sync Image backups do not retain their deduplicated state. |
| Quotas | Quota calculations are based on the length of the file (size-based quotas), or the rehydrated usage of a file (usage-based quotas). |
| Tiered File Systems | User data can be deduplicated; however, metadata is not. |
| File system packing | Deduplication and File system packing use the same underlying file system mechanism to achieve space savings. It is impossible to calculate and report the amount of saved space separately for each of these features. |