ONTAP 9.3 Fan-out and cascade data protection deployments

Fan-out and cascade data protection deployments:

You can use a fan-out deployment to extend data protection to multiple secondary systems. You can use a cascade deployment to extend data protection to tertiary systems. Both deployments support any combination of SnapMirror DR, SnapVault, or unified replication.

How fan-out deployments work

A mirror-vault fan-out deployment consists of a source volume that has a mirror relationship to a secondary volume and a SnapVault relationship to a different secondary volume.

A multiple-mirrors fan-out deployment consists of a source volume that has a mirror relationship to multiple secondary volumes.

How cascade deployments work :

A mirror-mirror cascade deployment consists of a chain of relationships in which a source volume is mirrored to a secondary volume, and the secondary volume is mirrored to a tertiary volume. If the secondary volume becomes unavailable, you can synchronize the relationship between the primary and tertiary volumes without performing a new baseline transfer.

A mirror-vault cascade deployment consists of a chain of relationships in which a source volume is mirrored to a secondary volume, and the secondary volume is vaulted to a tertiary volume.

Vault-vault and vault-mirror cascade deployments are also supported:

• A vault-vault cascade deployment consists of a chain of relationships in which a source volume is vaulted to a secondary volume, and the secondary volume is vaulted to a tertiary volume.
• A vault-mirror cascade deployment consists of a chain of relationships in which a source volume is vaulted to a secondary volume, and the secondary volume is mirrored to a tertiary volume.

Steps to configure the Cascading Protection Deployment:

List the Vserver information. 

This example I am using the single cluster and 3 vservers 

=> vsnew  --- Source Vserver

=> vsdest  ---- Destination Vserver

=> vstertiary  --- Tertiary Vserver

Create a Cluster and SVM level peer relationship (Source -- Destination --- Tertiary)

Create a RW source volume in vsnew vserver and create a DP volume to destination and Tertiary vservers.

Create some files in source volume.

Now create a snapmirror relationship to destination vserver (vsnew ---- vsdest)

Now initialize the replication process using the following command.

Check the destination volume, which contains source volume files.

Now create a snapmirror relationship from Destination to Tertiary (vsdest  ----- vstertiary)

Initialize it now.

Now Cascade mirror - Mirror relationship got created and initialized.

Check the protection relationship from System Manager.

Now you append some text to an existing files in source volume.

This update will replicate as per your schedule.

After your schedule time, you will be able to see the files.

You can use the wildcard characters also to query the snapmirror details.

You can use the cluster wide options to set the throttle also.