Training
November 2011
Updated for Data ONTAP 8.1 7-Mode
NetApp Solutions
Failures and Disasters
NetApp Solutions
Failures and Disasters
Asynchronous mode
Provides regional disaster protection
Volumes or qtrees
Manual or scheduled replication
Synchronous and semi-synchronous modes
Provides metro distance disaster protection
Zero or near-zero RPO
Only volumes
FlexVol SnapMirror FlexVol
TradVol TradVol
FlexVol TradVol
FlexVol SnapMirror FlexVol
TradVol TradVol
FlexVol TradVol
Maintains same Snapshot copies at Different Snapshot copies can exist on source
source and destination and destination
Source and destination volumes are replicas Destination volume can contain multiple
qtrees from different source systems
1
Although 1-min updates are possible, they are not recommended; use SnapMirror Semi-Sync for low
RPO (<3 minutes)
2
Although 1-min updates are possible, they are not recommended; SnapMirror Semi-Sync cannot be used
on stand-alone qtrees
Only volumes
Initial baseline transfer
SnapMirror transitions into synchronous mode
with the help of consistency point (CP)
forwarding and NVLOG forwarding
When SnapMirror is in synchronous mode:
Writes are acknowledged to the client only after
destination system receives the data
Example:
fas1:vol1 fas2:vol2 sync
3
1
3
FC or IP
2
CP
Aggregate
Aggregate 4 5
Destination
Source volume
volume
Only volumes
Initial baseline transfer
SnapMirror transitions into semi-synchronous
mode with the help of consistency point (CP)
forwarding
When SnapMirror is in semi-synchronous
mode:
Writes are acknowledged to the client soon after
they are written to the source system
Example:
fas1:vol1 fas2:vol2 semi-sync
NetApp Confidential Limited Use 23
SnapMirror Semi-Sync Functional Diagram
2
1
FC or IP
3
CP
Aggregate
Aggregate 3 4
Destination
Source volume
volume
Configuration
Destination system contains the configuration
information (/etc/snapmirror.conf)
Examples:
fas1:vol1 fas2:vol2 0-55/5 * * *
fas1:vol1 fas2:vol2 semi-sync
fas1:/vol/vol1/qt1 fas2:/vol/vol2/qt2 0 23 * *
1
Reverse resync (which is resync after a failover) will not work until source Data
ONTAP version is upgraded to match the destination Data ONTAP version.
2
Do not grow source volume beyond 16TB until 64-bit expansion is complete
on the destination aggregate and the destination volume is grown beyond 16TB
* Only Async
** Manual failback
Compression
Decompression
Compressed data
across the wire
FS Info FS Info
Inode Inode
PVBNVVBN PVBN VVBN PVBN VVBN PVBN VVBN PVBNVVBN PVBN VVBN PVBN VVBN PVBN VVBN
1 1 2 2 3 3 4 4 2 1 1 2 4 3 3 4
Aggregate Aggregate
Disks Disks
NetApp Confidential Limited Use 65
The Deswizzling Process
Primary System Secondary System
FS Info FS Info
Inode Inode
PVBN VVBN PVBN VVBN PVBN VVBN PVBN VVBN PVBN VVBN PVBN VVBN
1 1 2 2 -5 1 -5 2 2 1 1 2
Volume SnapMirror
Aggregate Aggregate
Disks Disks
NetApp Confidential Limited Use 66
The Deswizzling Process
Primary System Secondary System
FS Info FS Info
Inode Inode
Volume SnapMirror
Aggregate Aggregate
Disks Disks
NetApp Confidential Limited Use 67
The Deswizzling Process
Primary System Secondary System
Inode Inode
Volume SnapMirror
Aggregate Aggregate
Disks Disks
NetApp Confidential Limited Use 68
The Deswizzling Process
Primary System Secondary System
FS Info FS Info
Volume SnapMirror
Aggregate Aggregate
Disks Disks
NetApp Confidential Limited Use 69
How Long Does Deswizzling Take?
It depends on:
Age of the data set
Size of the data set
100GB delta change took approx. 20 minutes
500GB delta change took approx. 3 hours
System utilization
Frequency of SnapMirror updates
Whether a Snapshot copy is deleted before
deswizzling for that Snapshot copy is
completed
SnapMirror
FlexClone
volumes
SnapMirror
Maintains
Parent storage
volume
efficiency
FlexClone
volumes FlexClone
volumes
FlexClone
volumes
SnapMirror
Network Savings Yes. Data sent as compressed No. Data sent as uncompressed
over the network over the network
32-bit or
64-bit
64-bit or
32-bit
Volume
SnapMirror Volume
SnapMirror
initialize or an
update
32-bit or
64-bit or
64-bit
32-bit
Volume
SnapMirror Volume
32-bit or
System A running Data 64-bit
System B running Data
ONTAP 8.1 Volume
ONTAP 8.1
Volume SnapMirror between 32-bit to 64-
bit Aggregates
For more information on Volume SnapMirror between
32-bit and 64-bit Aggregates please refer to the
following slides on the field portal
Replication Between 32-bit and 64-bit A
ggregates using Volume SnapMirror
Eliminates performance impact to the host Replication at the host level consumes CPU
with replication handled at the storage level cycles and network bandwidth
Provides zero data loss with synchronous Dependency on hub transport server and
mirroring, but flexible enough to stretch across mailbox server leaves room for potential data
WAN distances and replicate asynchronously loss
Provides fast failover and failback through Failover to DR site involves manual process to
integration with SnapManager for Exchange bring target DB online, plus no failback
Business Continuity Module mechanism with expected RTO of 12 hrs.
No reseeding unless complete loss of data at May require reseeding of database if too many
the primary site logs cannot be replayed on target server
Replication
Uninterrupted
FlexClone Tape
Volumes Library
SnapMirror
SnapVault
Tape
Library
MetroCluster
SnapMirror
FlexClone Volumes
Volume
SnapMirror SnapVault
Async
Exchange offers
consistent
backups
Bidirectional Volume
SnapMirror Async Local archival and
Supporting Exchange
off-load tape
Supporting Exchange
with 15,000 mailboxes with 15,000 mailboxes backups
SnapManager
Local Archive using products are
SnapVault & Tape
integrated with
SnapMirror
R/O R/W
R/O R/W R/W
Remote Site 1
Remote Site 2
VolB
VolB
SnapMirror Async