Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 15 results
    • Replicating volume pairs stopped due to there is no target volume
      https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/Replicating_volume_pairs_stopped_due_to_there_is_no_target_volume
      Applies to NetApp Element software NetApp SolidFire NetApp SolidFire Cluster Pairs NetApp SolidFire Volume Replication Issue Alerts in NetApp SolidFire Active IQ: Error Code:remoteRepAsyncDelayExceede...Applies to NetApp Element software NetApp SolidFire NetApp SolidFire Cluster Pairs NetApp SolidFire Volume Replication Issue Alerts in NetApp SolidFire Active IQ: Error Code:remoteRepAsyncDelayExceeded Details: Volume pairing is Paused. Neither volume is a target. New State = PausedMisconfigured. Details in NetApp Element software 12.7: Volume pairing is Paused. Volume ID does not exist.
    • Remote Replication pauses in Element due to fullness of target cluster
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Remote_Replication_pauses_in_Element_due_to_fullness_of_target_cluster
      Remote replication of paired volumes between clusters stops, with a combination of one or more of the following alerts showing in the the Cluster UI (https://<MVIP>) and in ActiveIQ: The following vol...Remote replication of paired volumes between clusters stops, with a combination of one or more of the following alerts showing in the the Cluster UI (https://<MVIP>) and in ActiveIQ: The following volumes have paused remote replication of snapshots because the target cluster is too full: volume <volume_ID> cluster pair ID <cluster pair_ID> target cluster <target_cluster_name>. To resolve this fault, free up some space on the target storage cluster.
    • How to determine where snapmirror update is being executed from
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/How_to_determine_where_snapmirror_update_is_being_executed_from
      Applies to ONTAP 9 SnapMirror Description This article describes how to identify the source IP address using the audit logs when an unknown SnapMirror update is being executed.
    • CBS support for Cloud Manager offline version
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Backup_Service/CBS_support_for_Cloud_Manager_offline_version
      Applies to NetApp Cloud Manager offline version 3.9.15/x and earlier (Cloud Manager Dark Site) Cloud Backup Service (CBS) On-Prem Working Enviornment (WE) Issue After discovering On-Prem WE, the Backu...Applies to NetApp Cloud Manager offline version 3.9.15/x and earlier (Cloud Manager Dark Site) Cloud Backup Service (CBS) On-Prem Working Enviornment (WE) Issue After discovering On-Prem WE, the Backup & Restore page will not show any volumes available for backup
    • Blank Snapshot label leads to SCV secondary backup failure
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Blank_Snapshot_label_leads_to_SCV_secondary_backup_failure
      SnapCenter Plug-in for VMware vSphere (SCV) SCV secondary backup fails with errors: Job Details of SCV: Vault failed: SnapVault update failed for the relationship [<SRC_SVM> : <SRC_VOLUME> ==> <DST_SV...SnapCenter Plug-in for VMware vSphere (SCV) SCV secondary backup fails with errors: Job Details of SCV: Vault failed: SnapVault update failed for the relationship [<SRC_SVM> : <SRC_VOLUME> ==> <DST_SVM> : <DST_VOLUME>] with error: SnapVault relationship for source volume [<SRC_SVM> : <SRC_VOLUME>] and destination volume [<DST_SVM> : <DST_VOLUME>] is not healthy. Transfer failed. (Volume access error (No space left on device)) Backup is run with policy that has blank Snapshot label.
    • Snapshot-only replication pauses in Element due to target volumes exceeding snapshot limit
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Snapshot-only_replication_pauses_in_Element_due_to_target_volumes_exceeding_snapshot_limit
      The following volumes have paused remote replication of snapshots because the target cluster volume has exceeded its snapshot limit: [source volume ID <volume_ID> cluster pair ID <cluster_pair_ID> rem...The following volumes have paused remote replication of snapshots because the target cluster volume has exceeded its snapshot limit: [source volume ID <volume_ID> cluster pair ID <cluster_pair_ID> remote cluster <remote_cluster_name> target volume ID <target_volume_ID>, source volume ID <source_volume_ID> cluster pair ID <cluster_pair_ID> remote cluster <remote_cluster_name> target volume ID <target_volume_ID>, source volume ID <source_volume_ID> cluster pair ID <cluster_pair_ID> remote cluster…
    • AutoSupport Message: Replicating volume pairs have an Async Delay greater than 360 minutes
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/AutoSupport_Message__Replicating_volume_pairs_have_an_Async_Delay_greater_than_360_minutes
      The alert can be caused by different reasons: WAN connectivity between source and destination site is disrupted, Target volume does not exist, MTU between the replicating nodes mismatch, Alert can be ...The alert can be caused by different reasons: WAN connectivity between source and destination site is disrupted, Target volume does not exist, MTU between the replicating nodes mismatch, Alert can be triggered by failedSpaceTooFull alerts on the replication cluster, The source volume size is larger than the destination volume size, Replication is paused manually.
    • How to fix MTU inconsistency between replicating clusters with standard frame size interlink
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_fix_MTU_inconsistency_between_replicating_clusters_with_standard_frame_size_interlink
      Applies to NetApp Element Software Remote replication Link between clusters on standard MTU Storage clusters on jumbo MTU This article describes how to fix MTU inconsistency respecting the supported m...Applies to NetApp Element Software Remote replication Link between clusters on standard MTU Storage clusters on jumbo MTU This article describes how to fix MTU inconsistency respecting the supported models for remote replication as described in TR-4741 (page 12 and further). Please note on Element software MTU inconsistency is not supported by NetApp. While it is possible the replication may work/have worked under other circumstances, only the scenarios described in TR-4741 are supported.
    • Snapmirror Abort - Error: command failed: Job failed: No transfer to abort
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Snapmirror_Abort_Error__command_failed__Job_failed__No_transfer_to_abort
      Snapmirror abort will launch a job for the abort operation but will later fail if there is no active/current transfer *(or other active operation) in progress.
    • What are the restrictions on Snapshot label string that can be set from SCV?
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/What_are_the_restrictions_on_Snapshot_label_string_that_can_be_set_from_SCV
      Applies to SnapCenter Plug-in for VMware vSphere (SCV) Answer Snapshot label in backup policy has the following restrictions: Alphanumeric characters are allowed as the first character Alphanumeric ch...Applies to SnapCenter Plug-in for VMware vSphere (SCV) Answer Snapshot label in backup policy has the following restrictions: Alphanumeric characters are allowed as the first character Alphanumeric characters, dashes '-', underscores '_', and periods '.' are allowed from the second character Maximum character length is 31 Additional Information What are the restrictions on Snapshot label string that can be set from SnapCenter?
    • Snapshots are not transferring to destination automatically or manually
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Snapshots_are_not_transferring_to_destination_automatically_or_manually
      Source snapshot was being created with a _tmp extension and not replicated to destination. Snapshot was not being renamed snapshot_daily.x as other volume snapshots were. sourcecluster::> snapshot sho...Source snapshot was being created with a _tmp extension and not replicated to destination. Snapshot was not being renamed snapshot_daily.x as other volume snapshots were. sourcecluster::> snapshot show -vserver <vsname> -volume <volname> -fields create-time sourcecluster::> snapshot show -vserver <vsname2> -volume <volname2> -fields create-time <vsname2> <volname2> <snap>_daily.0 Thu Jun 02 21:32:05 2022 <vsname2> <volname2> <snap>_daily_tmp Mon Jun 06 21:32:11 2022