Skip to main content
NetApp Knowledge Base

What are the best practices for designing SnapMirror to minimize user impact when using dedicated ports e0d/e0f ?

  1. Last updated
  2. Save as PDF
Views:
136
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

ONTAP 9

Answer

Best practices and design recommendations:
  • Separate SnapMirror and user traffic
    • Use dedicated physical ports (e0d/e0f) for SnapMirror intercluster traffic.
    • Prevents replication traffic from affecting user data access.
    • If possible, use separate VLANs or network segments for further isolation.
  • Create dedicated intercluster LIFs for SnapMirror
    • Create at least one intercluster LIF per node; two per node (e0d, e0f) recommended for redundancy.
    • Assign intercluster LIFs only to e0d/e0f, not to ports used by user traffic.
    • Do not include intercluster LIFs in the failover group for data (e0c/e0e).
    • Intercluster LIF failover is node-local; enable auto-revert so LIFs return to their home port after recovery.
  • SnapMirror policy and schedule
    • Asynchronous SnapMirror is suitable for disaster recovery if recovery point objective (RPO) is acceptable.
    • Schedule SnapMirror jobs outside business peak hours (e.g., early morning, evening).
  • Network bandwidth control (throttling)
  • Additional notes
    • Management ports are not supported for SnapMirror intercluster LIFs; use data ports (including e0d/e0f).
    • Intercluster LIFs can share physical ports with data LIFs, but dedicated ports are preferred for isolation.
    • For further details on networking requirements, see SnapMirror configuration and best practices guide for ONTAP 9 (see “Intercluster networking requirement”).
  • Cautions
    • Intercluster LIFs only fail over within the same node; plan redundancy accordingly.
    • Do not mix intercluster and data LIFs in the same failover group.
    • Confirm switch port availability and connectivity for e0d/e0f before deployment.

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.