The following table lists the maximum volume size allowed for different
storage systems, with and without deduplication.
Table 1. Maximum volume size allowed for different
storage systems, with and without deduplication
| Storage system model |
Maximum size of volume without deduplication (TB) |
Maximum size of volume with deduplication (TB) |
Total data size of volume with deduplication (TB) |
|
FAS2020
|
16 |
1 |
17 |
| FAS2050
|
16 |
2 |
18 |
| FAS3020
|
16 |
2 |
18 |
| FAS3040
|
16 |
4 |
20 |
| FAS3050
|
16 |
3 |
19 |
| FAS3070
|
16 |
16 |
32 |
| FAS3140
|
16 |
4 |
20 |
|
FAS3160
|
16 |
16 |
32 |
| FAS3170
|
16 |
16 |
32 |
| FAS6030
|
16 |
16 |
32 |
| FAS6040
|
16 |
16 |
32 |
| FAS6070
|
16 |
16 |
32 |
| FAS6080
|
16 |
16 |
32 |
|
R200
|
16 |
4 |
20 |
Note:
- All storage systems listed in preceding table must have the NearStore personality license enabled to use deduplication except R200 that does not require this license.
- The following storage systems
do not support deduplication:
- FAS200 series
- FAS900 series
- Synchronous SnapMirror cannot be used to replicate volumes with deduplication.
The size of a volume containing deduplicated data cannot be increased, either manually or by using the autogrow option, beyond the maximum supported size limit mentioned in the preceding table. In addition, you cannot enable deduplication on the volume if its size is greater than the supported maximum volume size. However, starting from Data ONTAP 7.3.1, you can enable deduplication on a volume after shrinking it within the supported size limit.
Deduplication
is supported on an
active/active configuration. The maximum number of concurrent
deduplication
operations allowed on each node of an
active/active configuration
is eight.
If one of the node fails, the other node takes over the operations of the failed node. In the take-over mode, the working node continues with its
deduplication
operations as usual. However, the working node does not start any
deduplication
operations of the failed node.
Note: Change logging for deduplication-enabled volumes will continue for the failed node in takeover mode. Therefore, deduplication operations can be performed on data written during takeover mode after the failed node is active, and there is no loss in space savings. To disable the change logging for volumes that belong to a failed node, turn off deduplication on those volumes. You can also view the status of deduplication-enabled volumes for a failed node in takeover mode.
