Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/How_to_resume_protection_in_a_fan-out_configuration_with_SMBC
      If you experience a failover on the SM-BC destination, the asynchronous SnapMirror destination will become unhealthy, and you must manually restore protection by deleting and recreating the relationsh...If you experience a failover on the SM-BC destination, the asynchronous SnapMirror destination will become unhealthy, and you must manually restore protection by deleting and recreating the relationship with the asynchronous SnapMirror endpoint. Note: Fan-out configurations are supported with the MirrorAllSnapshots policy, and, beginning with ONTAP9.11.1, the MirrorAndVault policy. Beginning in ONTAP 9.11.1, fan-out configurations in SMBC are not supported with XDPDefault policy.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Can_I_use__Fan-out_to_migrate_an_Identity_preserve_SVM_DR_to_a_new_Cluster
      Applies to In ONTAP 9.3 and earlier, only one identity-preserve true relationship is allowed per source-SVM Starting with ONTAP 9.4, SVM-DR allows fanout to two destinations, with considerations Use v...Applies to In ONTAP 9.3 and earlier, only one identity-preserve true relationship is allowed per source-SVM Starting with ONTAP 9.4, SVM-DR allows fanout to two destinations, with considerations Use volume SnapMirror to migrate the data to an SVM of the New Cluster Break and release the original SVM-DR Convert the new volume SnapMirror to SVM-DR Converting volume replication relationships to an SVM replication relationship SVM-DR cannot create the second destination relationship
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM_DR_can_not_create_the_second_destination_relationship
      SVM DR can not create the second FAN-out relationship following the errors: Reason: Source Vserver "SVM" is in an msid non preserving DR relationship, but the specified destination Vserver was created...SVM DR can not create the second FAN-out relationship following the errors: Reason: Source Vserver "SVM" is in an msid non preserving DR relationship, but the specified destination Vserver was created later than Data ONTAP 9.0, and so does not support an msid non preserving relationship. Delete the destination Vserver in the existing relationship. Recreate the destination Vserver, and then establish the SnapMirror relationship from both the destination Vservers
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Is_it_possible_to_create_more_than_8_Snapmirror_fan_out_relationships
      According to the document Snapmirror Limitation, it has mentioned "You can fan out a maximum of eight destination volumes from a single source volume". However, it has no hard limited in ONTAP to crea...According to the document Snapmirror Limitation, it has mentioned "You can fan out a maximum of eight destination volumes from a single source volume". However, it has no hard limited in ONTAP to create 8 fan-out Snapmirror relationships. You are able to create more than 8 fan-out Snapmirror relationships from a single source volume. The limitation is for performance concerns. To creating more than 8 fan-out Snapmirror relationships from a single source volume is an un-supported configuration.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Can_you_create_two_fan_out_SVM_DR_identity_preserve_true_relationships
      Applies to ONTAP 9 SVM-DR Answer Only one identity-preserve true relationship is allowed per source-SVM Data Protection Power Guide - Understanding SnapMirror SVM replication – Page 59 Understanding S...Applies to ONTAP 9 SVM-DR Answer Only one identity-preserve true relationship is allowed per source-SVM Data Protection Power Guide - Understanding SnapMirror SVM replication – Page 59 Understanding SnapMirror SVM replication Additional Information Add your text here.