AWS fsx: Document FSx storage efficiency status and ONTAP settings
Summary
Adds a new 'Storage Efficiency status' section explaining when Amazon FSx reports a volume's storage efficiency as Enabled vs Disabled, the ONTAP settings FSx applies, and how to restore the FSx-managed configuration via AWS CLI or ONTAP CLI.
Security assessment
This change documents storage efficiency configuration behavior and remediation steps; it concerns data compression/deduplication rather than any security control, vulnerability, or credential handling.
Evidence
+Amazon FSx reports a volume's storage efficiency as **Enabled** in the console, API, and AWS CLI only when the volume's storage efficiency configuration in ONTAP matches the settings that Amazon FSx uses. When you enable storage efficiency on a volume, Amazon FSx applies the following ONTAP settings:
Diff
diff --git a/fsx/latest/ONTAPGuide/manage-vol-SE.md b/fsx/latest/ONTAPGuide/manage-vol-SE.md index 1a16c2c6f..679f31712 100644 --- a//fsx/latest/ONTAPGuide/manage-vol-SE.md +++ b//fsx/latest/ONTAPGuide/manage-vol-SE.md @@ -7 +7 @@ -Compression of data blocksDeduplication of data blocksCompaction of data blocksExample: storage efficiencies +Compression of data blocksDeduplication of data blocksCompaction of data blocksExample: storage efficienciesStorage Efficiency status @@ -70,0 +71,35 @@ The following image illustrates how storage efficiencies are applied to data. +## Storage Efficiency status + +Amazon FSx reports a volume's storage efficiency as **Enabled** in the console, API, and AWS CLI only when the volume's storage efficiency configuration in ONTAP matches the settings that Amazon FSx uses. When you enable storage efficiency on a volume, Amazon FSx applies the following ONTAP settings: + + * Compression: inline + + * Deduplication: inline and background (both) + + * Cross-volume deduplication: none + + * Compaction: inline + + + + +If you modify storage efficiency settings with the ONTAP CLI or REST API, or if you migrated your volumes from an on-premises ONTAP system, the volume's configuration might not match these settings. When that happens, Amazon FSx reports storage efficiency as **Disabled** , even if efficiency features are still active on the volume. + +To restore the Amazon FSx-managed configuration and have the console report **Enabled** , use one of the following methods: + + * **AWS CLI:** + + aws fsx update-volume --volume-id vol-id --ontap-configuration StorageEfficiencyEnabled=true + + * **ONTAP CLI:** + + ::> volume efficiency on -vserver svm-name -volume vol-name + ::> volume efficiency modify -vserver svm-name -volume vol-name -inline-dedupe true -inline-compression true -data-compaction true -compression true + + + + +###### Important + +For volumes migrated from Cloud Volumes ONTAP with a compression type of `secondary`, switching to the Amazon FSx-managed settings requires first undoing existing compression savings on the volume, then re-enabling compression with the `adaptive` compression type. This operation is resource-intensive. Plan this operation carefully before running it on production volumes. For more information, see [Moving between secondary compression and adaptive compression](https://docs.netapp.com/us-en/ontap/volumes/move-between-secondary-adaptive-compression-task.html) in the NetApp ONTAP documentation. +