Learn about performing a failback to Element
Contributors
Suggest changes
PDFs
When the issue on the primary side has been mitigated, you must resynchronize the original source volume and fail back to NetApp Element software. The steps you perform vary depending on whether the original source volume still exists or whether you need to failback to a newly created volume.
SnapMirror failback scenarios
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:
