Skip to content

Commit

Permalink
Merge pull request #2087 from NetAppDocs/pc-ontapdoc2488-9oct
Browse files Browse the repository at this point in the history
ontapdoc2488: Add storage efficiency information for FAS70 and 90
  • Loading branch information
netapp-dbagwell authored Oct 30, 2024
2 parents 63b2206 + 101f8e7 commit 4c0ccb3
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 7 deletions.
23 changes: 18 additions & 5 deletions concepts/builtin-storage-efficiency-concept.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,16 +9,29 @@ summary: "Beginning with ONTAP 9.15.1, built-in, automatically enabled storage e
:imagesdir: ../media/

[.lead]
Beginning with ONTAP 9.15.1, ONTAP provides storage efficiency and data compaction on AFF A70, AFF A90, and AFF A1K platforms. Depending on the platform, compression is performed using either the main CPU or with a dedicated offload processor. Storage efficiency is enabled automatically and requires no configuration. Storage efficiency is enabled by default on newly created thin-provisioned volumes and is applied to existing data, including volumes moved from other platforms to AFF A70, AFF A90, or AFF A1K platforms.
Beginning with ONTAP 9.15.1, ONTAP provides storage efficiency and data compaction on AFF A70, AFF A90, AFF A1K, FAS70, and FAS90 platforms.

Temperature-sensitive storage efficiency is not applied on AFF A70, AFF A90, and AFF A1K platforms. Compression is not based on hot or cold data on these platforms, so compression begins without waiting for data to become cold.
Depending on the platform, the following applies when you upgrade:

Storage efficiency on AFF A70, AFF A90, and AFF A1K platforms uses sequential packing of contiguous physical blocks to further improve storage efficiency for compressed data.
* Compression is performed using either the main CPU or with a dedicated offload processor.

Data that's migrated to AFF A70, AFF A90, or AFF A1K platforms using volume move or SnapMirror technology is converted automatically to 32k inline compression. Storage efficiency for data migrated from an AFF A70, A90, or A1K platform to an earlier platform is transformed automatically based on the destination platform's efficiency capabilities.
* Storage efficiency is enabled by default on all thin-provisioned volumes or just existing volumes.
+
For an FF A70, AFF A90, or AFF A1K platform, storage efficiency is enabled automatically and requires no configuration. This applies to all newly created thin-provisioned volumes and existing data, including volumes moved from other platforms to an AFF A70, AFF A90, or AFF A1K platform.
+
For a FAS70 or FAS90 platform, storage efficiency is enabled by default only on existing thin-provisioned volumes that had storage efficiency enabled before upgrading. You can enable storage efficiency on newly created volumes using the CLI or REST API method.
* Data that’s migrated using volume move or SnapMirror technology is converted automatically to 32k inline compression:
+
For an AFF A70, AFF A90, or AFF A1K platform, data is converted automatically.
+
For a FAS70 or FAS90 platform, data is converted only if compression was enabled on the original platform.

For information about upgrading a controller to an AFF A70, AFF A90, or AFF A1K, see the https://docs.netapp.com/us-en/ontap-systems-upgrade/choose_controller_upgrade_procedure.html[ONTAP Hardware Upgrade Documentation^].
Temperature-sensitive storage efficiency is not applied on AFF A70, AFF A90, AFF A1K, FAS70, and FAS90 platforms. Compression is not based on hot or cold data on these platforms, so compression begins without waiting for data to become cold.

Storage efficiency on AFF A70, AFF A90, AFF A1K, FAS70, and FAS90 platforms uses sequential packing of contiguous physical blocks to further improve storage efficiency for compressed data.

For information about upgrading a controller to an AFF A70, AFF A90, AFF A1K, FAS70, or FAS90, see the https://docs.netapp.com/us-en/ontap-systems-upgrade/choose_controller_upgrade_procedure.html[ONTAP Hardware Upgrade Documentation^].

// 2024-Oct-9, ONTAPDOC-2488
// 2024-June-21, IDR-370
// 2024-June-10, ONTAPDOC-1757 and ONTAPDOC-1851
4 changes: 2 additions & 2 deletions concepts/storage-efficiency-overview.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Temperature-sensitive storage efficiency (TSSE), introduced in ONTAP 9.8, is ena

* *CPU or dedicated offload processor storage efficiency*
+
Beginning with ONTAP 9.15.1, ONTAP provides link:builtin-storage-efficiency-concept.html[CPU or dedicated offload processor storage efficiency] and data compaction on AFF A70, AFF A90, and AFF A1K platforms. Storage efficiency is enabled automatically and requires no configuration.
Beginning with ONTAP 9.15.1, ONTAP provides link:builtin-storage-efficiency-concept.html[CPU or dedicated offload processor storage efficiency] and data compaction on AFF A70, AFF A90, AFF A1K, FAS70, and FAS90 platforms. On AFF A70, AFF A90, and AFF A1K systems, storage efficiency is enabled automatically and requires no configuration.

You can realize the benefit of these technologies in your day-to-day operations with minimal effort. For example, suppose you need to supply 5,000 users with storage for home directories, and you estimate that the maximum space needed by any user is 1 GB. You could reserve a 5 TB aggregate in advance to meet the total potential storage need. However, you also know that home directory capacity requirements vary greatly across your organization. Instead of reserving 5 TB of total space for your organization, you can create a 2 TB aggregate. Then you can use thin provisioning to nominally assign 1 GB of storage to each user but allocate the storage only as needed. You can actively monitor the aggregate over time and increase the actual physical size as necessary.

Expand All @@ -74,7 +74,7 @@ ONTAP disk partitioning technology delivers greater storage efficiency as well.

NetApp provides the same storage efficiency features available with on-premises ONTAP in the cloud. When you migrate data from on-premises ONTAP to the cloud, the existing storage efficiency is preserved. For example, suppose you have an SQL database containing business-critical data that you want to move from an on-premises system to the cloud. You can use data replication in BlueXP to migrate your data and, as part of the migration process, you can enable your latest on-premises policy for Snapshot copies in the cloud.


// 2024-Oct-9, ONTAPDOC-2488
// 2024-June-21, IDR-370
// 2024-June-10, ONTAPDOC-1757
// 2023 Dec 11, Jira 1424
Expand Down

0 comments on commit 4c0ccb3

Please sign in to comment.