Skip to main content
NetApp Knowledge Base

SM-BC-Snapshot cannot be deleted after snapmirror delete and snapmirror release

Views:
518
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.8
  • SnapMirror Business Continuity (SM-BC)

Issue

  • Snapshots on DP type destination volume can't be deleted after deleting and releasing SM-BC type relationship
Error: command failed on vserver "SM-BC-DST" volume "dst1" snapshot
"snapmirrorCG.64c6dd08-92bd-11eb-91c0-0050569d3cf2_2148702777.2021-04-01_133413": Snapshot copy
"snapmirrorCG.64c6dd08-92bd-11eb-91c0-0050569d3cf2_2148702777.2021-04-01_133413" of volume "dst1" in Vserver "SM-BC-DST" has not expired or is locked.
Use the "snapshot show -fields owners, expiry-time" command toview the expiry and lock status of the Snapshot copy.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.