Release notes
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
SnapMirror delete operation fails in takover state
Contributors
Suggest changes
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
Issue:
When ONTAP 9.9.1 is installed on a cluster, executing the snapmirror delete command fails when an SnapMirror active sync consistency group relationship is in takeover state.
Example:
C2_cluster::> snapmirror delete vs1:/cg/dd Error: command failed: RPC: Couldn't make connection
Solution
When the nodes in an SnapMirror active sync relationship are in takeover state, perform the SnapMirror delete and release operation with the "-force" option set to true.
Example:
C2_cluster::> snapmirror delete vs1:/cg/dd -force true
Warning: The relationship between source "vs0:/cg/ss" and destination
"vs1:/cg/dd" will be deleted, however the items of the destination
Consistency Group might not be made writable, deletable, or modifiable
after the operation. Manual recovery might be required.
Do you want to continue? {y|n}: y
Operation succeeded: snapmirror delete for the relationship with destination "vs1:/cg/dd".
