Skip to main content
ONTAP tools for VMware vSphere 10

Fan out protection

Contributors netapp-jani
PDFs

In a fan out protection, the consistency group is double protected with synchronous relationship on the first destination ONTAP cluster and with asynchronous relationship on the second destination ONTAP cluster. The create, edit, and delete SnapMirror active sync protection workflows maintain the synchronous protection. SRM failover and reprotect workflows maintain the asynchronous protection.

In order to establish fan out protection you need to peer three site clusters and SVMs.

Example:

If

then

  • Source consistency group is on cluster c1 and SVM svm1

  • First destination consistency group is on cluster c2 and SVM svm2 and

  • Second destination consistency group is on cluster c3 and SVM svm3

  • The cluster peering on source ONTAP cluster will be (C1, C2) and (C1, C3).

  • The cluster peering on first destination ONTAP cluster will be (C2, C1) and (C2, C3) and

  • The cluster peering on second destination ONTAP cluster will be (C3, C1) and (C3, C2).

  • SVM peering on source SVM will be (svm1, svm2) and (svm1, svm3).

  • SVM peering on first destination SVM will be (svm2, svm1) and (svm2, svm3) and

  • SVM peering on second destination svm will be (svm3, svm1) and (svm3, svm2).

The following diagram shows the fan out protection configuration: Fan out protection configuration Fan out protection relationship

Steps

  1. Create a new place holder datastore. Refer Select a Placeholder Datastore

  2. Add datastore to host cluster protection Modify protected host cluster. You need to add both asynchronous and synchronous policy types.