Skip to main content
NetApp Knowledge Base

Why are SnapMirror snapshots not cleaned up automatically after DR-test or initialization?

  1. Last updated
  2. Save as PDF
Views:
2,577
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror
  • Storage Virtual Machine Disaster Recovery (SVM DR)
  • SnapMirror active sync (formerly SnapMirror Business Continuity, SM-BC) 

Answer

  • Baseline snapshots do not automatically roll-off at any point during
    • the reverse resync
    • when the relationship is back in its original direction
    • first synchronization for a newly configured relationship
  • Old baseline snapshots resulting from the reverse resync must be cleaned up (manually deleted) by the storage admin
  • This is normal and expected SnapMirror/Snapshot behavior
  • This is to prevent any baseline snapshot from being deleted within the role reversal steps which would prevent subsequent updates/resyncs and require an entire baseline transfer to re-establish the SnapMirror
  • Once they are no longer needed, refer to How to identify and delete unneeded SnapMirror snapshots for information on how to identify and delete these snapshots

Additional Information

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.