Skip to main content
NetApp Knowledge Base

Can you enable SnapLock on the SVM root volume on a CVO?

  1. Last updated
  2. Save as PDF
Views:
9
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
cloud
Last Updated:

Applies to

NetApp Cloud Volumes ONTAP

Answer

SnapLock on SVM root volumes is technically supported but not recommended due to ONTAP architectural principles and operational risks:
  • SVM root volumes contain only namespace/junction paths and SVM metadata, not business data.
  • Locked snapshots on small root volumes can lead to space exhaustion, causing SVM outages and blocking remediation.
  • Locked snapshots cannot be deleted or altered until expiry, making SVM or volume deletion/migration impossible until all retention periods are met.
  • Anti-Ransomware Protection (ARP) and FPolicy do not protect root volumes.
If SnapLock has been enabled on the SVM root volume in error:
  • There is no supported way to disable SnapLock until all locked snapshots expire.
  • To avoid operational impact, schedule root volume snapshots as infrequently as possible to minimize retention burden.
  • Monitor root volume space closely and use load-sharing mirrors to ensure recoverability in case of issues.

Additional Information

additionalInformation_text
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.