Release notes
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
SnapMirror failback scenarios
Contributors
Suggest changes
-
PDF of this doc site
-
Manage storage with Element software
-
Protect your data
-
Replication between NetApp Element software and ONTAP (ONTAP CLI)
-
-
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
The SnapMirror disaster recovery functionality is illustrated in two failback scenarios. These assume the original relationship has been failed over (broken).
The steps from the corresponding procedures are added for reference.
|
In the examples here, R1 = the original relationship in which the cluster running NetApp Element software is the original source volume (Element) and ONTAP is the original destination volume (ONTAP). R2 and R3 represent the inverse relationships created through the reverse resync operation. |
The following image shows the failback scenario when the source volume still exists:
The following image shows the failback scenario when the source volume no longer exists:
