AWS fsx documentation change
Summary
Removed note about compression savings preservation limitations and inactive-data-compression behavior
Security assessment
The changes relate to storage efficiency technical details without security implications. No evidence of security context in the removed content.
Diff
diff --git a/fsx/latest/ONTAPGuide/manage-vol-SE.md b/fsx/latest/ONTAPGuide/manage-vol-SE.md index 439ffc449..2000f7462 100644 --- a//fsx/latest/ONTAPGuide/manage-vol-SE.md +++ b//fsx/latest/ONTAPGuide/manage-vol-SE.md @@ -13,4 +12,0 @@ ONTAP organizes files into 4 kibibyte (KiB) data blocks. Storage efficiencies ta -###### Note - -ONTAP does not preserve post-process compression savings achieved at the source in the destination DP volume when the destination volume's tiering policy is `All`. To preserve post-process compression savings, you should set the destination volume tiering policy to `Auto` and enable inactive-data-compression on the destination file system to re-apply post-process compression savings at the destination. - @@ -21 +17 @@ Storage efficiencies are applied in two ways. They are applied to data inline (b -ONTAP doesn't support enabling storage efficiencies on data protection (DP) volumes. However, storage savings achieved in the source read-writable (RW) volume are preserved when data is replicated to the destination DP volume except when inactive-data-compression is enabled on the destination DP volume. Enabling inactive-data-compression results in the loss all storage efficiency savings on the destination DP volume. +ONTAP doesn't support enabling storage efficiencies on data protection (DP) volumes. However, storage savings achieved in the source read-writable (RW) volume are preserved when data is replicated to the destination DP volume.