Skip to main content
NetApp Knowledge Base

Why is TPS supported on fabricpool volumes in FSx but not on-prem ONTAP

Views:
38
Visibility:
Public
Votes:
0
Category:
snaplock
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • FSx
  • TPS (Tamper-proof snapshots)
  • Snaplock

Answer

  • On-prem data is not considered tamper-proof once it is tiered to an object-store.
    • Reasons for may be because object-stores can be modified and changed, and the underlying disks in the object-store are outside ONTAP's visibility and protection.
    • ONTAP will only support the feature on FabricPool volumes if the volume doesn't have any blocks tiered to the object-store and the tiering policy is set to “none”.
  • However, unlike on-prem ONTAP platforms, the ONTAP instance and object-store in FSx is fully managed and is not accessible.
  • This allows snaplock compliance and the ability to support Tamper-proof Snapshot Locking.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.