Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • The snapmirror status is pending after deleting the old non-base snapshots
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/The_snapmirror_status_is_pending_after_deleting_the_old_non-base_snapshots
      The snapmirror status is pending after deleting the old non-base snapshots on the destination： The snapshot can not be deleted on the destination by the snapmirror update: Fri May 8 18:05:05 CST [Dest...The snapmirror status is pending after deleting the old non-base snapshots on the destination： The snapshot can not be deleted on the destination by the snapmirror update: Fri May 8 18:05:05 CST [Destination:replication.dst.err:error]: SnapMirror: destination transfer from source_mirror:vol001 to destination:vol001 : replication transfer failed to complete. Use the snap list to show the cannot delete snapshot status of the destination volume that is acs (Application Consistent Snapshot) status.
    • Rubrik backup displays "Failed 'NETAPP' 'Snapdiff' metadata scan for fileset...Falling back to regular metadata scan."
      https://kb.netapp.com/on-prem/ontap/DP/SnapDiff/SnapDiff-KBs/Rubrik_backup_displays_Failed_NETAPP_Snapdiff_metadata_scan_for_fileset_Falling_back_to_regular_metadata_scan
      Failed 'NETAPP' 'Snapdiff' metadata scan for fileset [fileset name] from [path to share]'. Falling back to regular metadata scan As the metadata scan falls back to "regular metadata scan" when SnapDif...Failed 'NETAPP' 'Snapdiff' metadata scan for fileset [fileset name] from [path to share]'. Falling back to regular metadata scan As the metadata scan falls back to "regular metadata scan" when SnapDiff metadata scan fails, the job can still complete successfully. Rubrik reports "Failed 'NETAPP' 'Snapdiff' metadata scan for fileset [fileset name] from [path to share]'. Falling back to regular metadata scan."
    • My Mirror-Vault relationship does not copy the snapshots I want it to
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/My_Mirror-Vault_relationship_does_not_copy_the_snapshots_I_want_it_to
      Applies to ONTAP 9 Snapmirror policy type: Vault Mirror-Vault Issue My mirror-vault relationship is healthy but does not copy the snapshots I want it to
    • Newly created SnapMirror shows as "broken-off"
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Newly_created_SnapMirror_shows_as_broken_off
      Applies to Clustered Mode 8.X ONTAP 9 SnapMirror Issue Newly created SnapMirror shows as "broken-off" and attempts to initialize fail with "<destination_volume> must be a data-protection volume"
    • Volume Move of a transitioned Volumes fails with error : "Moving a volume undergoing transition is not supported"
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Volume_Move_fails_for_transitioned_Volumes_with_error_Moving_a_volume_undergoing_transition_is_not_supported
      Applies to ONTAP 9.x Transition Data Protection (TDP) Volume move of a transitioned volume fails with error : "cannot move volume in Vserver . Reason: Moving a volume undergoing transition is not supp...Applies to ONTAP 9.x Transition Data Protection (TDP) Volume move of a transitioned volume fails with error : "cannot move volume in Vserver . Reason: Moving a volume undergoing transition is not supported" Breaking Transition Data Protection (TDP) Mirrors between ONTAP 7-mode and ONTAP 9 fails with error : command failed: Cannot break the volume "svm1:vol1" as the previous resync transfer on this relationship was aborted. Complete the resync operation, and then try the break operation again.
    • All nodes detects cpeer.unavailable:alert due to mgwd restart in the peered cluster
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/All_nodes_detects_cpeer_unavailable_alert_due_to_mgwd_restart_in_the_peered_cluster
      [＜NODE＞: mgwd: cpeer.unavailable:alert]: Peer cluster ＜CLUSTER_NAME＞ is no longer available. The mgwd process in one or more nodes in the peered cluster has restarted due to error. [＜NODE＞: mgwd: ucor...[＜NODE＞: mgwd: cpeer.unavailable:alert]: Peer cluster ＜CLUSTER_NAME＞ is no longer available. The mgwd process in one or more nodes in the peered cluster has restarted due to error. [＜NODE＞: mgwd: ucore.panicString:error]: 'mgwd: Received SIGSEGV (Signal 11) at RIP 0x80fe217ca accessing address 0x40 (pid 2261, uid 0, timestamp 1588431655)' [＜NODE＞: spmd: spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 2261 exited as a result of signal normal exit (0).