1
my
NetApp ONTAP FAN-
a
us
th
OUT and CASCADE
Mu
SnapMirror
r
ma
ku
Configuration
l
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 1
2
Three Site Data Center Data Protection
In today’s constantly connected global business environment,
companies expect rapid recovery of critical application data with zero
data loss. Organizations devise effective disaster recovery plans by
keeping the below requirements in mind:
• Data should be recoverable in the event of catastrophic failure at
one or more data centers (disaster recovery).
my
• Data should be replicated and distributed in an optimal way, taking
a
into consideration major business criteria such as cost of storage,
us
protection level against site failures, and so on.
th
• What needs to be protected and for how long should be driven by:
Shrinking recovery point objective (RPO), to achieve zero data
Mu
loss
Near-zero recovery time objective (RTO), for faster recovery of
r
business-critical applications in case of disaster
ma
Three-Site Data Center Topology
ku
The three-site data center configuration can be done in either fan-
l
out or cascade topology.
hi
nt
Fan-out Topology
Fan-out topology consists of primary and near disaster recovery data
Se
centers within region sites (with replication network having <10ms
round trip time), will synchronously replicate data between
themselves to achieve zero RPO. And the primary asynchronously
replicates data on a regular basis depending on the quantity of new
data being generated to the remote or far disaster recovery out-of-
region data center.
If disaster strikes the primary site, the application can be started with
zero data loss from the near disaster recovery data center, which
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 2
3
would also take over asynchronous replication to the far disaster
recovery data center.
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 fan-out and cascade deployments support any combination of
my
SnapMirror DR, SnapVault, or unified replication; however,
SnapMirror Synchronous relationships (supported beginning with
a
ONTAP 9.5) support only fan-out deployments with one or more
us
asynchronous SnapMirror relationships and do not support cascade
deployments. th
Mu
Only one relationship in the fan-out configuration can be a SnapMirror
Synchronous relationship, all the other relationships from the source
r
volume must be asynchronous SnapMirror relationships. SnapMirror
ma
Business Continuity (supported beginning with ONTAP 9.8) also
ku
supports fan-out configurations.
l
hi
How fan-out deployments work
nt
SnapMirror supports multiple-mirrors and mirror-vault fan-out
Se
deployments.
A multiple-mirrors fan-out deployment consists of a source volume
that has a mirror relationship to multiple secondary volumes.
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.
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 3
4
amy
us
th
Mu
r
ma
ku
Configuring FAN-OUT Data Protection:
l
hi
Check or add a snapmirror_sync license.
nt
In this document, I have used 3 ontap 9.7 clusters (cluster1,
cluster2 and cluster3)
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 4
5
In cluster1, create a cluster peer to cluster2 and cluster3.
List the cluster peer status.
Cluster1 peered to cluster2 and cluster3
In cluster1, create and list the SVM peer.
my
svm_src1 vserver peered to cluster2’s svm_dst1 and
a
cluster3’s svm_dst2
us
th
Mu
r
ma
l ku
In cluster2, repeat the same steps.
hi
Create and list the cluster peer status.
nt
Cluster2 is peered with cluster1 and cluster3.
Create and list the svm peer relationship.
Se
Cluster2 svm_dst1 is peered with cluster1’s svm_src1 and
cluster3’s svm_dst2.
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 5
6
my
In cluster3, repeat the same steps.
a
us
Create and list the cluster peer status.
Cluster3 is peered with cluster1 and cluster2.
th
Create and list the svm peer relationship.
Mu
Cluster3 svm_dst2 is peered with cluster1’s svm_src1 and
cluster2’s svm_dst1.
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 6
7
In a source cluster (cluster1), create data flexvolume and create
files.
ex: cluster1 ---- svm_src1 ----- volnew
Volume is R/W type.
amy
us
th
Mu
In a cluster2, create a DP volume.
r
ma
cluster2 svm_dst1volnew_dr (DP type Volume)
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 7
8
Create Synchronous snapmirror relationship from cluster2.
Source cluster – cluster1
Destination Cluster – cluster2
Source svm – svm_src1
Destnation svm – svm_dst1
Source Volume – volnew
Destination Volume – volnew_dr
Mode – Synchronous
amy
us
th
Mu
r
ma
ku
Then initialize the snapmirror relationship from cluster2.
l
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 8
9
Check and list the snapmirror status.
completed and InSync status
my
a
us
th
Mu
r
ma
Mount the DP volume and check the file contents.
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 9
10
Create a new file in source volume(ex: volnew --- file name:f1)
my
a
us
Step2: Async snapmirror replication between cluster1 volume and
cluster3 DP type volume.
Create a new DP type volume in cluster3.
th
Mu
r
ma
l ku
hi
nt
Create Asynchronous snapmirror relationship.
Se
Source cluster – cluster1
Destination Cluster – cluster3
Source svm – svm_src1
Destination svm – svm_dst2
Source Volume – volnew
Destination Volume – volnew_dr2
Mode – Asynchronous
Schedule – 5min
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 10
11
amy
Then initialize the snapmirror relationship from cluster3.
us
th
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 11
12
Check and list the snapmirror status.
status - snapmirrored
my
a
Mount the DP volume and check the file contents.
us
th
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 12
13
Fan-Out Configuration:
Source volume – volnew (cluster 1)
Destination volume – volnew_dr (cluster2) –synchronous
Destination volume – volnew_dr2 (cluster3) -
Asynchronous
my
a
us
th
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 13
14
To test the replication, create a new file in source volume
(volnew – cluster1)
my
a
us
Check and list the contents from cluster3 (volnew_dr2)
th
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 14
15
Cascade Topology
Cascade topology is where the primary would synchronously replicate
to the near disaster recovery site, and the near disaster recovery site
would asynchronously replicate data to the far disaster recovery site.
In case the near disaster recovery site goes down, you can configure
an asynchronous replication directly to the far disaster recovery site
over longer distance to ensure all the delta updates are being updated
my
or replicated.
a
us
How cascade deployments work
SnapMirror th
supports mirror-mirror, mirror-vault, vault-mirror,
and vault-vault cascade deployments.
Mu
A mirror-mirror cascade deployment consists of a chain of
r
relationships in which a source volume is mirrored to a secondary
ma
volume, and the secondary volume is mirrored to a tertiary volume. If
ku
the secondary volume becomes unavailable, you can synchronize the
relationship between the primary and tertiary volumes without
l
hi
performing a new baseline transfer.
nt
Beginning with ONTAP 9.6, SnapMirror Synchronous relationships are
supported in a mirror-mirror cascade deployment. Only the primary
Se
and secondary volumes can be in a SnapMirror Synchronous
relationship. The relationship between the secondary volumes and
tertiary volumes must be asynchronous.
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 15
16
ONTAP Cascade Topology Configuration:
my
Cluster2 Cluster3
Source Cluster: Cluster1
svm_dst1 svm_dst2
a
Source vServer: svm_src1
us
vol_cascade_dr1 vol_cascade_dr2
Source Volume: vol_cascade
Sync
th Async
Mu
Create a RW volume (vol_cascade) in cluster1. (Source cluster)
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 16
17
Mount this volume in linux server and create files.
my
a
us
th
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 17
18
Create Synchronous snapmirror relationship.
Source cluster – cluster1
my
Destination Cluster – cluster2
a
Source svm – svm_src1
us
Destination svm – svm_dst1
Source Volume – vol_cascade
Destination Volume – vol_cascade_dr1
th
Mu
Mode – synchronous
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 18
19
Initialize the snapmirror relationship and test the status.
Successfully initialized and it is InSync status.
a my
us
Mount the DP volume in linux server and list the file contents.
th
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 19
20
Create a new DP volume (vol_cascade_dr2) in cluster3.
my
a
us
th
Mu
r
ma
ku
Create Synchronous snapmirror relationship.
l
Source cluster – cluster2
hi
Destination Cluster – cluster3
nt
Source svm – svm_dst1
Se
Destination svm – svm_dst2
Source Volume – vol_cascade_dr1
Destination Volume – vol_cascade_dr2
Mode – Asynchronous
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 20
21
my
a
us
th
Initialize the Async snapmirror relationship.
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 21
22
Mount the DP volume in linux server and list the file contents.
amy
us
th
Mu
r
ma
l ku
hi
nt
Se
SENTHILKUMAR MUTHUSAMY | SAN MASTERS 22
