Search

SnapMirror Synchronous doesn't show changes on destination volume
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_Synchronous_doesn_t_show_changes_on_destination_volume
Applies to ONTAP 9.5 and later Snapmirror Synchronous (SM-S) Issue When viewing a read-only SnapMirror Synchronous (SM-S) destination volume, users do not immediately see changes made to the source vo...Applies to ONTAP 9.5 and later Snapmirror Synchronous (SM-S) Issue When viewing a read-only SnapMirror Synchronous (SM-S) destination volume, users do not immediately see changes made to the source volume, or only see changes after some period of time.
Failed to delete SnapMirror snapshot - Resolution Guide
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Failed_to_delete_SnapMirror_snapshot_-_Resolution_Guide
Resolution guide for snapshot delete issues related to SnapMirror
SnapMirror stuck in "Finalizing" state in ONTAP
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_stuck_in_Finalizing_state_in_ONTAP
Applies to ONTAP 9 SnapMirror Issue SnapMirror type-XDP relationship reports a Relationship Status of Finalizing without increasing Total Progress verified in: ONTAP System Manager Command output: sna...Applies to ONTAP 9 SnapMirror Issue SnapMirror type-XDP relationship reports a Relationship Status of Finalizing without increasing Total Progress verified in: ONTAP System Manager Command output: snapmirror show ::> snapmirror show Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated svmProd:volProd XDP svmDR:volDR Uninitialized Finalizing 6.55TB true 09/07 14:53:54 This behavior does not impact vol move
SVMDR with fabric pool fails with error "Transfer failed. (Volume access error (No space available in capacity tier staging area))"
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVMDR_Volume_access_error_No_space_available_in_capacity_tier_staging_area
Applies to ONTAP 9 FabricPool Issue All the SVMDR relations are failing to update. Parent relationship reports error: Failed to start transfer for Snapshot copy "vserverdr.2.5e5df5f0-759e-11ea-8657-00...Applies to ONTAP 9 FabricPool Issue All the SVMDR relations are failing to update. Parent relationship reports error: Failed to start transfer for Snapshot copy "vserverdr.2.5e5df5f0-759e-11ea-8657-00a0b8c2dc19.2020-05-17_130000". (Failed to start transfer. (Duplicate transfer specified (Replication engine error))) While volume level relationships in SVMDR reports error: Transfer failed. (Volume access error (No space available in capacity tier staging area))
ONTAP 9 SnapMirror fails after transferring a portion of the data
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/ONTAP_9_SnapMirror_fails_after_transferring_a_portion_of_the_data
Mon Jan 01 01:00:00 EST 2017 Initialize[Jan 01 00:00:00]:a0b1c2d3-0123-0123-0123-0123456789abOperation-Uuid=a0b1c2d3-0123-0123-0123-0123456789ab Group=none Operation-Cookie=0action=Defer source=source...Mon Jan 01 01:00:00 EST 2017 Initialize[Jan 01 00:00:00]:a0b1c2d3-0123-0123-0123-0123456789abOperation-Uuid=a0b1c2d3-0123-0123-0123-0123456789ab Group=none Operation-Cookie=0action=Defer source=sourceSVM:sourceVol destination=destSVM:destVol status=Failuremessage=Transfer failed.(Replication operation request failed from Cluster Id: a0b1c2d3-0123-0123-0123-0123456789ab, Node Id: a0b1c2d3-0123-0123-0123-0123456789ab to Cluster Id: a0b1c2d3-0123-0123-0123-0123456789ab, Node Id: a0b1c2d3-0123-0123…
SnapMirror initialization or update fails after transferring a portion of the data
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_initialization_or_update_fails_after_transferring_a_portion_of_the_data
Transfers using the same source and different destinations, or different sources and the same destination, are also successful. The failed transfer might appear to have normal throughput at the start ...Transfers using the same source and different destinations, or different sources and the same destination, are also successful. The failed transfer might appear to have normal throughput at the start of the transfer but slow down or decrease throughput until it eventually fails. The failed transfer might appear to transfer the same amount of data during each attempt.
How to view all SnapMirror/SnapVault relationships
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/How_to_view_all_SnapMirror_SnapVault_relationships
Applies to ONTAP 9 Data ONTAP 8.2 7-Mode Description This article describes how to view all SnapMirror/SnapVault relationship types
Cluster peering fails on clusters with customized cipher suites in ONTAP 9.5
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Cluster_peering_fails_on_clusters_with_customized_cipher_suites_in_ONTAP_9.5
Error: command failed: Using peer-address XX.XXX.XX.X: An introductory RPC to the peer address "XX.XX.XX.XX" failed to connect: RPC: Remote system error These errors may also appear for an existing cl...Error: command failed: Using peer-address XX.XXX.XX.X: An introductory RPC to the peer address "XX.XX.XX.XX" failed to connect: RPC: Remote system error These errors may also appear for an existing cluster peer relationship after an upgrade to one of the releases mentioned in the "Applies to" section of this KB. Mon Jul 13 2020 12:58:30 +05:30 [kern_mgwd:info:1668] 0x81b004200: 0: ERR: RpcConnectionCache: getXcContext: Could not find any PSK cipher suites (0).
Cluster peering fails on clusters with customized cipher suites in ONTAP 9.6 and later
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Cluster_peering_fails_on_clusters_with_customized_cipher_suites_in_ONTAP_9.6_and_later
Error: command failed: Using peer-address XX.XXX.XX.X: An introductory RPC to the peer address "XX.XX.XX.XX" failed to connect: RPC: Remote system error [from mgwd on node "XXXXXXXXX" (VSID: -1) to xc...Error: command failed: Using peer-address XX.XXX.XX.X: An introductory RPC to the peer address "XX.XX.XX.XX" failed to connect: RPC: Remote system error [from mgwd on node "XXXXXXXXX" (VSID: -1) to xcintro at XX.XX.XX.XX]. These errors may also appear for an existing cluster peer relationship after an upgrade to one of the releases mentioned in the "Applies to" section of this KB. cluster peer show output reports the availability of the Remote Cluster as Unavailable.
SVM DR snapshots not rolling off
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM_DR_snapshots_not_rolling_off
Some SVM DR source volumes are full of vserverdr snapshots, which are not rolling off The SVM-DR relationship continues to have successful updates and remain healthy unless the impacted source volume(...Some SVM DR source volumes are full of vserverdr snapshots, which are not rolling off The SVM-DR relationship continues to have successful updates and remain healthy unless the impacted source volume(s) hit the 255 snapshot limit Impacted volumes will also not create or roll off snapshots managed via the volume's snapshot policy. Individual volumes involved in SVM-DR may retain multiple vserverdr.* Snapshots if their underlying SnapMirror relationship is failing for other reasons.
SVM DR update fails with error failed to set field "cmddirname" to "volume constituent"
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM_DR_update_fails_with_error_failed_to_set_field_cmddirname_to_volume_constituent
Applies to ONTAP 9.5 and later SVM DR Issue SVM DR update fails with error Last Transfer Error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: aclview_ui Method: ba...Applies to ONTAP 9.5 and later SVM DR Issue SVM DR update fails with error Last Transfer Error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: aclview_ui Method: baseline. Reason: failed to set field "cmddirname" to "volume constituent".