SnapMirror SE Training

SnapMirror SE
Training
November 2011
Updated for Data ONTAP 8.1 7-Mode
Srinath Alapati & Neil Shah

Technical Marketing
Data Protection Solutions
NetApp Confidential Limited Use

Agenda
Causes of Downtime
NetApp High-Availability and
Disaster Recovery (DR) Solutions
SnapMirror Basics
SnapMirror Improvements in Data ONTAP 7.3
SnapMirror improvements in Data ONTAP 8.0.1 7-Mode
SnapMirror Improvements in Data ONTAP 8.1 7-Mode
SnapMirror Manageability
Securing SnapMirror
SnapMirror Advanced Topics
Competitive Information
Sizing Tools
Sample Deployment Scenarios
References
NetApp Confidential Limited Use 2
Causes of Downtime

Failures, Disasters, and Causes
More Likely, Lower Impact Less Likely, Higher Impact
NetApp Solutions
Failures and Disasters
Operational Application Component Site & Data Regional

Failures Failures Failures Center Failures Disasters
People and Bugs Controller Terrorist Attacks Electric Grid

Process Issues Performance Failure Cyber Threats Failures
Infrastructure Issues HBA/Port Failure HVAC Failures Natural
Changes Change Disk Failure Disasters:
Power Failures
Configuration Management Shelf Failure Floods
Building Fires Hurricanes
and Problem Process FC Loop Failure Plumbing Earthquakes
Management
Accidents
Architectural
Failures
Planned
Downtime
Logical Local Physical Physical
NetApp Confidential Limited Use

High Availability & Disaster Recovery Portfolio
More Likely, Lower Impact Less Likely, Higher Impact
NetApp Solutions
Failures and Disasters
Operational Application Component Site & Data Regional

Failures Failures Failures Center Failures Disasters
Fast Data Recovery Bugs Storage Resiliency
Controller Campus &
Terrorist Metro
Attacks Regional
Electric Grid
People and Area Protection Disaster
Snapshot
Process Issues
Performance Failure
RAID-DP
Cyber Threats Failures
Protection
Infrastructure Issues HBA/Port Failure MetroCluster
HVAC Failures Natural
SnapRestore MetroCluster
Changes Change Disk Failure SnapMirror
Disasters:
SnapVault Management Power
SnapMirror
Failures

Disk Maintenance SW Floods
Async
Configuration Shelf Failure SyncFires
Building
and Problem
SnapManager Process Redundant Hurricanes
FC LoopHW

Failure Plumbing Earthquakes
Management
Accidents
Architectural
Failures
NetApp Global Services
Backup & Recovery Services Planned
Downtime
Disaster Recovery Services
Logical AutoSupportLocal
& Storage Availability
Physical Audits
Physical

SnapMirror Basics

SnapMirror Basics
What Is SnapMirror; SnapMirror Modes
Volume SnapMirror (VSM) Fundamentals
Qtree SnapMirror (QSM) Fundamentals
VSM versus QSM
SnapMirror versus SnapVault
SnapMirror Sync Fundamentals
SnapMirror Sync versus MetroCluster
SnapMirror Setup
SnapMirror over Fibre Channel
SnapMirror Interoperability between different Data
ONTAP versions

What Is SnapMirror?
DR solution for NetApp storage
Maintain copies at multiple sites globally
Application testing using secondary storage
DR testing using secondary storage
Load balancing
Remote data access
Off-loading tape or D2D backups

SnapMirror Modes
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

Volume SnapMirror Fundamentals
Like volumes

FlexVol SnapMirror FlexVol

TradVol TradVol

FlexVol TradVol

Block-for-block replication
Older Data ONTAP release to same or newer
major Data ONTAP release
snapmirror update on the destination
Takes a Snapshot copy on the source system
Transfers all Snapshot copies created since the last
update
Deletes all Snapshot copies deleted on the source
since the last update
Transfers all changed blocks since the last update
Unchanged, unused, and deleted blocks are not
transferred

Destination volume is read-only

LUNS in the destination volume are read-only,
online, and unmapped

Source and destination systems can be of different
minor versions
Destination system can be of same or higher major
or minor version
Volume SnapMirror Volume SnapMirror Replication
Source Destination Possible?
Data ONTAP 7.2 Data ONTAP 7.3 Yes
Data ONTAP 7.3 Data ONTAP 7.2 No
Data ONTAP 7.3.x Data ONTAP 7.3.y Yes

Qtree SnapMirror Fundamentals
Qtree replication between like or different
volumes

FlexVol SnapMirror FlexVol

TradVol TradVol

FlexVol TradVol

Logical replication
Data ONTAP versions can be different
snapmirror update on the destination
Takes a Snapshot copy on the source unless the s
flag is used
Transfers only the latest Snapshot copy created since
the last update
Keeps only the latest copy on the destination
Transfers all changed blocks in the qtree of interest
Unchanged, unused, and deleted blocks are not
transferred

Destination volume is writable; qtree is read-
only
LUNS in the destination qtree are read-only,
online, and unmapped

VSM versus QSM
Volume SnapMirror Qtree SnapMirror
Replication between same type volumes Replication possible between qtrees in
traditional and flexible volumes
Destination system must have higher or Data ONTAP version independent
same Data ONTAP version
Destination volume must be same or larger Destination volume must have approx. 5% free
than the source volume space
Multihop cascading possible Only single-hop, however, QSM can be
cascaded with VSMfor example:
A [QSM] B -- [VSM] -- C
A [VSM] B [QSM] -- C
Can be initialized using tape device Can be initialized to an external disk using
(SnapMirror to tape) LREP
For traditional volumes only, performance is Not sensitive to disk geometry regardless of the
sensitive to disk geometry type of volume
Maintains same Snapshot copies at Different Snapshot copies can exist on source
source and destination and destination

VSM versus QSM
Source and destination volumes are replicas Destination volume can contain multiple
qtrees from different source systems
Source-deduplicated volumes that are Qtrees in source-deduplicated volumes that

replicated with volume SnapMirror remain are replicated with qtree SnapMirror are full
deduplicated at the destination size at the destination
Deduplication savings extend to the Even though the source volume is
bandwidth savings because volume deduplicated, qtree SnapMirror will expand
SnapMirror only transfers nondeduplicated the data and send the entire data to the
blocks destination
Destination volume is automatically Source and destination volumes can be
deduplicated and cannot be independently independently deduplicated
deduplicated
LUN clones cannot be created on the read- LUN clones can be created on the destination
only destination volume; clones can be volume, but not in the destination qtree
created in a FlexClone volume
FlexClone volume at the destination results in FlexClone volume at the destination has no
a lock on a Snapshot copy of the source impact on the source system
volume
Feature Volume Qtree SnapVault
SnapMirror SnapMirror
Replication type Physical Logical Logical
Replication network FC or IP FC or IP IP only
Multiple paths for Yes Yes No
replication
Data ONTAP version Yes No No
sensitive?
Network compression Yes Yes with NetApp No
approval
RPO (how much data 1 minute1 1 minute2 1 hour
can I afford to lose?)
RTO (how long does it Seconds to minutes Seconds to minutes Minutes to hours
take for data to be
writable?)
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

Feature Volume SnapMirror Qtree SnapVault
SnapMirror
Snapshot retention No Possible but Yes
for backup use tedious
Snapshot N/A No Yes
coalescing
Failback resync Yes Yes No
Deduplication Destination inherits Destination does Destination does not
source dedupe savings; not inherit source inherit source dedupe
network savings as well dedupe savings savings. Deduplication is
run on the destination
prior to the Snapshot
copy creation.

SnapMirror Sync Fundamentals
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

SnapMirror Sync Functional Diagram
NVLOG and CP forwarding
3
1
3
FC or IP
2
CP
Aggregate
Aggregate 4 5
Destination
Source volume
volume

SnapMirror Semi-Sync Fundamentals
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
SnapMirror Semi-Sync Functional Diagram
Only CP forwarding; no NVLOG

forwarding
2
1
FC or IP
3
CP
Aggregate
Aggregate 3 4
Destination
Source volume
volume

SnapMirror Sync & Semi-Sync Supported
Configurations
Same platforms for source and destination
Ex: FAS6070 to FAS6070
Systems with mixed disk types not supported
Even if replicating between similar disk types
Performance degradation with ATA drives
Obtain NetApp approval for these configs
Not supported between controllers belonging in
HA (cluster) pair
Not supported between volumes within the
same controller

SnapMirror Sync & Semi-Sync Supported
Configurations (contd)
Bidirectional on flexible volumes supported
since Data ONTAP 7.2.2
Recommended version is Data ONTAP 7.3 or higher
Distance (RTT) sensitive!
~< 2ms RTT recommended for Sync
~< 5ms RTT recommended for Semi-Sync

SnapMirror Sync or SnapMirror Semi-
Sync and Data ONTAP versions
Source and destination systems must be of same
version
SnapMirror Sync Source SnapMirror Sync Destination Replication

Possible?
Data ONTAP 7.x Data ONTAP 7.y No
Data ONTAP 7.3.x Data ONTAP 7.3.x Yes
Data ONTAP 7.3.x Data ONTAP 7.3.y No

SnapMirror Sync versus MetroCluster
Feature SnapMirror Sync MetroCluster
Replication network IP or FC FC only
Limit on concurrent Yes No limit

transfers
Distance limitation Up to 200 KM (latency 100 KM
driven)
Replication between HA Yes No
pairs
Manageability FilerView, CLI, Ops Mgr CLI
Multiuse replica Yes (FlexClone) Limited (app can read from
No (dump) both plexes)
Deduplication Dedupe volume and sync No restrictions
volume cannot be in the
same aggregate
Use of secondary node Yes Noasync replication has
for async mirroring to occur from primary node
Performance impact Yes. See Sizing section Minimal

SnapMirror Setup
Takes minutes to set up
Security / Access
On the source system, enter the following command:
source> options snapmirror.access host=destination
Configuration
Destination system contains the configuration
information (/etc/snapmirror.conf)
Examples:
fas1:vol1 fas2:vol2 0-55/5 * * *
fas1:/vol/vol1/qt1 fas2:/vol/vol2/qt2 0 23 * *

SnapMirror over Fibre Channel
SnapMirror works over both Ethernet and Fibre

Channel
Refer to the switch support matrix for
requirements on Fibre Channel
http://now.netapp.com/NOW/knowledge/docs/switches/sm_f
c_switch_support/

7-mode Volume SnapMirror
Interoperability Matrix
Destination Volume
Data ONTAP 7.3.x 8.0.x 8.1

Aggregate
32-bit 32-bit 64-bit 32-bit 64-bit
Type
7.3.x 32-bit Yes Yes 1 No Yes 1 Yes 1
32-bit No Yes No Yes 1 Yes 1

Source
8.0.x
Volume
64-bit No No Yes Yes 12 Yes 1
32-bit No No No Yes Yes

8.1
64-bit No No No Yes 2 Yes
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

7-mode Volume SnapMirror
Interoperability Matrix (contd)
NOTE: SnapMirror Sync and SnapMirror Semi-Sync
must have same Data ONTAP versions on both source
and destination systems.
This is also available in spreadsheet form here.

7-mode Qtree SnapMirror Interoperability
Matrix
Destination Volume
Data ONTAP 7.3.x 8.0.x 8.1

Aggregate
32-bit 32-bit 64-bit 32-bit 64-bit
Type
7.3.x 32-bit Yes Yes Yes Yes Yes
32-bit Yes Yes Yes Yes Yes

Source
8.0.x
Volume

8.1
Qtree SnapMirror and SnapVault have no restrictions replicating between 32-

bit and 64-bit volumes in 7-mode.

SnapMirror Improvements
in Data ONTAP 7.3

SnapMirror Improvements or Changes in
Data ONTAP 7.3
VSM and QSM Improvements
New VSM and QSM Options
SnapMirror Sync and SnapMirror Semi-Sync
changes
SnapMirror Destination Volume Guarantees
SnapMirror Network Compression
SnapMirror Window Size

Volume SnapMirror and Qtree SnapMirror
Changes in Data ONTAP 7.3
Max. number of supported concurrent transfers
on FlexVol volumes is increased for certain
platforms.
Limits due to ATA drives also removed
Throughput improvements
Optimized for multiprocessor systems
Alleviate or eliminate domain bottlenecks
Computational improvements
Improved algorithm to compute differences between
sets of Snapshot copies on the source

Concurrent Transfers
Refer to Data Protection Online Backup and
Recovery Guide for the appropriate Data ONTAP
version.
Transfers shown below are not cumulative, i.e.,
cannot simultaneously replicate 64 QSM, 50 VSM,
and 16 Sync transfers in case of FAS3040 system
shown below.

New Options for Volume SnapMirror in
Data ONTAP 7.3
Option to guarantee specified number of VSM
transfers will always start
replication.volume.reserved_transfers
Default: 0
Option to revert to pre-Data ONTAP 7.3
concurrent limits
replication.volume.transfer_limits
Default: current
Previous will revert to Data ONTAP 7.2 limits

New Options for Qtree SnapMirror in
Data ONTAP 7.3
Option to guarantee specified number of QSM
transfers will always start
replication.logical.reserved_transfers
Default: 0
Option to revert to pre-Data ONTAP 7.3
concurrent limits
replication.logical.transfer_limits
Default: current
Previous will revert to Data ONTAP 7.2 limits

SnapMirror Sync and Semi-Sync Changes
Data ONTAP 7.3
NetApp approval not required for supported
configurations
Outstanding option functionality removed
Replaced by: semi-sync (CP sync)
No NVLOG forwarding
If outstanding is currently defined, upon upgrade to
Data ONTAP 7.3:
outstanding < 10s is converted to sync
outstanding >= 10s is converted to semi-sync
outstanding >= 500ops converted to semi-sync
SnapMirror does not modify relationships in the
configuration file
SnapMirror Sync and Semi-Sync Changes
(contd)
No increase in concurrent transfers
Data ONTAP 7.2.2 + FlexVol
NVLOG writes to the aggregate, not the root volume
(SnapMirror Sync)
Requires some free space in the aggregate
Approx. (10 times source NVRAM size) per volume

Other Changes Impacting SnapMirror
Data ONTAP 7.3
SnapMirror destination volume guarantees:
Destination volumes can now have guarantees
independent of the source volume
This is to prevent SnapMirror failures when volumes run
out of space
Turned off by default
Dedupe metadata moved to aggregate
To unlock space savings of metadata
Rescan required on the DR volume to maximize space
savings
Data ONTAP 7.2.4
Improves deswizzling performance

Changes in Data ONTAP 7.3.2
Increased window size for volume SnapMirror
Beneficial for large WAN pipes with high network latencies
For details, see SnapMirror Advanced Topics
SnapMirror network compression is GA for volume
SnapMirror
Network compression for qtree SnapMirror continues to be
available via NetApp approval (PVR)
For details, see SnapMirror Advanced Topics

SnapMirror Improvements in
Data ONTAP 8.0.1 7-Mode

FlexClone Enhancements in
Data ONTAP 8.0.1 7-Mode
Space efficient replication of FlexClone volumes
using volume SnapMirror
Before Data ONTAP 8.0.1 7-Mode, space
efficiency is lost when a FlexClone volume is
replicated using VSM
Starting Data ONTAP 8.0.1 7-Mode, space
efficiency is maintained when a FlexClone
volume is replicated using VSM
See the SnapMirror and FlexClone section for
more details

Out Of Order Frame Delivery Support For
SMoFC in Data ONTAP 8.0.1 7-Mode
Starting Data ONTAP 8.0.1 7-Mode, out-of-order
frame delivery is supported for SnapMirror over
Fibre Channel on the source and destination
systems
Enabling support for out-of-order frame delivery
on source and destination systems
Changes the default system behavior to allow
processing of out of order frames
Ensures uninterrupted SnapMirror transfers
regardless of the order in which the frames are
delivered
SnapMirror Improvements
in Data ONTAP 8.1

SnapMirror Improvements or Changes in
Data ONTAP 8.1
Before Data ONTAP 8.1 7-Mode
SnapMirror Async (VSM), Sync and Semi-Sync
Not possible to create volume SnapMirror
relationships between volumes in 32-bit and 64-bit
aggregates
Starting Data ONTAP 8.1 7-Mode
SnapMirror Async (VSM), Sync and Semi-Sync
Possible to create volume SnapMirror relationships
between volumes in 32-bit and 64-bit aggregates
See the SnapMirror between 32-bit and 64-bit
Aggregates section for more details

Concurrent Transfers in Data ONTAP 8.1
7-Mode
Starting Data ONTAP 8.1 7-Mode, NearStore
personality license is enabled by default
Transfers shown below are not cumulative, i.e.,
cannot simultaneously replicate 160 QSM, 100
VSM, and 16 Sync transfers in case of FAS3040
system shown below.

SnapMirror Manageability

Ways to Manage SnapMirror
CLI OnCommand Protection
System Manager
Manager
Configuration & Setup * *
Configure Multipath
Configure Throttle *
Configure Compression
Failover * *
Failback * **
* Only Async
** Manual failback

Securing SnapMirror

Securing SnapMirror
No native encryption available for SnapMirror
Use DataFort appliance for encryption
Two checksum-based options available in Data
ONTAP
SnapMirror transfer checksums
Option snapmirror.checksum.enable is on by
default
cksum argument in snapmirror.conf file
Only works with multipath
cksum= {none | crc32c | crc32c_header_only}
crc32c_header_only is available from Data ONTAP
7.2.6 and is the default.
Only for VSM
SnapMirror Advanced
Topics

SnapMirror Advanced Topics
SnapMirror Window Size and Throughput
SnapMirror Checkpoints
Falling Out of Sync; Getting Back into Sync
Deswizzling
Storage Provisioning on SnapMirror Destination
SnapMirrorSnapVault Cascade
SnapMirror and FlexClone
SnapMirror and Deduplication
SnapMirror and Data Compression
SnapMirror between 32-bit and 64-bit Aggregates
SnapMirror and SnapLock Compliance
Sizing for SnapMirror
Enables compression over network to minimize network
bandwidth consumption
Configurable per SnapMirror relationship
Uses industry-standard gzip algorithm
Compression ratio depends on the data set type
Reported in the snapmirror status -l output and log
file
Read SnapMirror Async
Write
Compression
Decompression
Compressed data
across the wire

Compression and decompression processing occurs on
the storage systems
CPU overhead associated with compression
Compression ratios depend on the data set
Oracle DB: 3.5:1; Home Dir: 2.7:1; Exchange DB: 1.5:1
Lower bandwidth usage and/or improve transfer times
Available today by obtaining NetApp approval for both
volume and qtree SnapMirror
Generally available (GA) in Data ONTAP 7.3.2 for
volume SnapMirror
More information in SnapMirror Network Compression
tech report (TR-3790)

Compression Vs. WAN Optimization
If the customer already has WAN optimization devices
Use them
Dont enable both
If the customer doesnt have WAN optimization device
And is interested in reducing only SnapMirror traffic, try
SnapMirror compression
And is interested in reducing all enterprise traffic, consider
a WAN optimization device
If the network link is lossy
A WAN optimization device could be beneficial
SnapMirror compression will not help

Window Size and Throughput
Problem:
SnapMirror may not be able to fully utilize the network
pipe for high network latency and large network pipes
SnapMirror window size is limited to 2MB until Data
ONTAP 7.3.0 (single or multi-path)
Example: 1000 Mbps network link with 100 ms latency
Max. Throughput = Window Size / Round Trip Time
Max. theoretical throughput = 2MB/100 ms =~ 160 Mbps
Only 16% link utilization
Solution:
Require larger window sizes to increase link utilization

Window Size and Throughput
Solution (VSM only):
Increased window size
Throughput can be increased by increasing window size
Increased to 7MB/14MB in Data ONTAP 7.3 D5 patch fix
and in Data ONTAP 7.3.1.1P4
Same fix is available in Data ONTAP 7.3.2, 8.0
When using multipath, window size is doubled
QSM has 2MB window size limitation regardless of the Data
ONTAP version
Mode (Data ONTAP) RTT Window Size Max. Throughput
(ms) (MB)
Single-path (7.2) 100 2MB 20MB/s
Single-path (7.3.2) 100 7MB 70MB/s
Multi-path (7.3.2) 100 14MB 140MB/s

SnapMirror Checkpoints
Checkpoints occur every five minutes
Not configurable or tunable
Conditions that prevent SnapMirror from restarting from
a checkpoint
Hostname changes
Volume name changes
Volume size changes
Data ONTAP version upgrades and downgrades

SnapMirror Sync: Falling Out of Sync
NVLOG timeout of 25 seconds
CP timeout of 1 minute
The actual time taken to fall into async varies
Depending on whether there is a device that can
respond to ARP queries

SnapMirror Sync: Getting Back into Sync
Async update occurs
Destination performs a snaprestore to last common
Snapshot copy
Async update completes
CP forwarding begins
Second async update occurs
NVLOG forwarding begins
Do not change visibility_interval
See Visibility Interval section in TR-3326 for more
information

What Is Deswizzling?
Deswizzling establishes the PVBNVVBN relationship
Restores read performance on the destination to normal upon completion
Physical volume block numbers (PVBNs) do not remain the
same upon SnapMirror update
Affects only volume SnapMirror FlexVol destination
Does not affect:
qtree SnapMirror; traditional volumes; any source volume
Can result in higher disk and CPU utilization
Performance impact on first read:
FlexClone, tape backup, user access
Improvements in Data ONTAP 7.2.4
Does not impact failover, reading or writing data in any way
Just another background WAFL scanner process

Why Deswizzling?
Primary System Secondary System
Vol Info Vol Info
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
Flex Volume 1 Flex Volume 2 Flex Volume 1 Flex Volume 2

LUN 1 LUN 2 LUN 1 LUN 2
Disks Disks
The Deswizzling Process
Vol Info Vol Info
FS Info FS Info
Inode Inode
PVBN values replaced
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
Vol Info Vol Info
FS Info FS Info
Inode Inode
PVBN VVBN PVBN VVBN PVBN VVBN PVBN VVBN

1 1 2 2 -5 1 -5 2
Volume SnapMirror
Aggregate Aggregate

Disks Disks
Vol Info Vol Info Deswizzling

kicks off
FS Info FS Info
Inode Inode

1 1 2 2 -5 1 -5 2
Volume SnapMirror
Aggregate Aggregate

Disks Disks
Vol Info Vol Info
FS Info FS Info
Inode Inode PVBN data

updated

1 1 2 2 3 1 4 2
Volume SnapMirror
Aggregate Aggregate

Disks Disks
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

What Is the Deswizzling Impact During
Read Operations?
Disk and CPU utilization are higher
during deswizzling
During Deswizzling After Deswizzling

What Is the Deswizzling Impact During
Read Operations?
Read response times are higher during
deswizzling
Might encounter lower read IOPs during
deswizzling
During Deswizzling After Deswizzling

Storage Provisioning on SnapMirror
Destination
Best practice is to size the destination volume as large
as the max. size the source volume would ever grow to
This prevents update failures due to source vol size increases
as long as aggregate has enough space
Starting in Data ONTAP 7.3, it is possible to enable
guarantees on SnapMirror destination volumes to
prevent volumes running out of space
Source and destination volumes can have different guarantees
Guarantee is disabled by default (meaning none)
Guarantee property is not inherited from the source volume
A Data ONTAP 7.2 destination volume will have volume
(disabled) while in SnapMirror state
A Data ONTAP 7.3 destination volume will have none while in
SnapMirror state

Storage Provisioning on SnapMirror
Destination
If FlexClone volumes are created on a volume
SnapMirror destination
The Snapshotcopy used to create clone volume is locked
on the source system (soft lock)
This lock prevents SnapMirror update failures
If the clone volume on the destination lives for a long
period of time, space consumption will grow on the source
system because of the locked Snapshot copy
Take this into consideration when sizing for storage on
SnapMirror source system
Refer to session 4085 from Insight 2008 conference for
more information

Volume SnapMirrorSnapVault Cascade
SnapMirror SnapVault volA/qt

volA volA
This is a supported configuration

Mirror and then back up
Two things to keep in mind
SnapMirror and SnapVault cannot run concurrently
Stagger the schedules
Starting in Data ONTAP 7.3.2, SnapVault can back up a
specific Snapshot copy from SnapMirror destination
Before Data ONTAP 7.3.2, SnapVault can only back up the
latest SnapMirror Snapshot copy

Replicating FlexClone Volumes
Before Data ONTAP 8.0.1 7-Mode
Production Site DR Site
SnapMirror
Parent Inflated to full

volume used capacity
FlexClone
volumes
Destination volumes are inflated to full used

capacity of parent volume
Replicating FlexClone Volumes
Starting Data ONTAP 8.0.1 7-Mode
SnapMirror
Maintains
Parent storage
volume
efficiency
FlexClone
volumes FlexClone
volumes
Destination volumes maintain efficiency and

use base snapshot from parent volume
FlexClone on SnapMirror Destination
Replication
uninterrupted
FlexClone
volumes
SnapMirror
Nondisruptive testing of DR site applications

and data
FlexClone volumes can also be used for
development, testing, training, and reporting
Creating FlexClone Volumes on a Volume
SnapMirror Destination
OK to
Use user-created Snapshot copies
Do NOT
Use scheduled Snapshot copies (such as hourly)
Delete the Snapshot copies on the source if a
FlexClone volume exists on the destination
Beware of scripts that roll old Snapshot copies
Use SnapMirror Snapshot copy that was deleted on
the source
Caution
When using latest SnapMirror Snapshot copy
When using SnapDrive rolling Snapshot copies
Rename the rolling Snapshot copy before creating the
clone
Creating FlexClone Volumes on a Volume
SnapDrive rolling Snapshot copies
If SnapMirror updates fail, SnapDrive will still continue to
create rolling Snapshot copies
A failure of the source system may lead to data loss!
Important to monitor SnapMirror updates
snap auto delete behavior
Disabled by default
When enabled, can potentially delete a Snapshot copy that
has a corresponding clone volume on the destination
Refer to session 4085 from Insight 2008 conference for
more information

Creating FlexClone Volumes on a Qtree
Qtree SnapMirror can have different Snapshot
copies on source and destination
Therefore, Snapshot copies are not locked on the
source system due to clone volumes on the
destination system

Creating FlexClone Volumes on a
SnapMirror Sync Destination
FlexClone volumes can be created on SnapMirror
Sync destination volume
A soft lock is immediately propagated to the source
upon creation of the clone volume on the destination
OK to
Use user-created Snapshot copies
Do NOT
Use scheduled Snapshot copies (such as hourly)
Delete the Snapshot copies on the source if a
FlexClone volume exists on the destination
Beware of scripts that roll old Snapshot copies
Use SnapMirror Snapshot copy that was deleted on the
source
Source Be aware of dedupe Be aware of dedupe

volume size limits prior to volume size limits prior to
Data ONTAP 8.1. Starting Data ONTAP 8.1. Starting
Data ONTAP 8.1 Data ONTAP 8.1
deduplication does not deduplication does not
impose a limit on the impose a limit on the
maximum volume size maximum volume size
supported supported
Destination Destination cannot be Destination can be

deduped independently. deduped independently.
Destination automatically Destination does not inherit
inherits source dedupe source dedupe savings.
savings.
Network Yes. Data sent as No. Data sent as
Savings deduplicated over the undeduplicated over the
network network

Data ONTAP 7.3, 8.0.1
Fingerprint database moved out of the volume to
achieve additional space savings. Therefore fingerprint
DB is not available at the DR site
Fingerprint DB is not required to read/write data to
dedupe volume
New data at the DR site can still be deduped within itself
Rescan required at the DR if deduplication is desired
between the new data and the old data and this can
take a long time
Longer the failover duration and as more operations are
run at the DR site, dedupe savings recognized on the
primary at time of failback will decrease unless a full
dedupe scan was run
Data ONTAP 8.1
Primary fingerprint DB(working copy) for a volume will
continue to be located inside the aggregate to achieve
additional space savings
Backup copy of the Fingerprint DB stored in the volume
Change log entries appended to the backup copy in the
volume
In the event of a failover
Fingerprints for new writes created as written
On running deduplication on the destination,
aggregate copy of the fingerprint DB of the old data
will be constructed from the copy of the fingerprint DB
in the FlexVol on the destination. Faster process
rather than recreating all the fingerprints from scratch
In the event of a failover (contd)
Old fingerprints will be merged with new fingerprints
created and deduplication processing occurs.
Dedupe savings between new and the old data
In the event of a failback
New data written at primary enjoys space savings with the
old data that exists at the time of failover but not with data
written from DR volume
On running deduplication on the source, aggregate copy of
the fingerprint DB of data written at DR can be constructed
Fingerprints of data at source merged with fingerprints of
data written at destination and deduplication processing
occurs
Dedupe savings between data at source and data written
at DR volume
SnapMirror and Data Compression
Source Be aware of compression Be aware of compression volume

volume size limits prior to Data size limits prior to Data ONTAP
ONTAP 8.1. Starting Data 8.1. Starting Data ONTAP 8.1
ONTAP 8.1 compression does compression does not impose a
not impose a limit on the limit on the maximum volume
maximum volume size size supported
supported
Destination Destination cannot be Destination can be compressed
compressed independently. independently. Destination does
Destination automatically not inherit source compression
inherits source compression savings.
savings.
Network Savings Yes. Data sent as compressed No. Data sent as uncompressed
over the network over the network

Volume SnapMirror between 32-bit and
64-bit Aggregates
Before Data ONTAP 8.1 7-Mode
32-bit
32-bit or 64-bit or
64-bit Aggr 32-bit Aggr
32-bit or
64-bit
64-bit or
32-bit
Volume
SnapMirror Volume
System A running Data System B running Data

ONTAP 8.0 ONTAP 8.0
Volume SnapMirror between 32-bit and
64-bit Aggregates
Starting Data ONTAP 8.1 7-Mode
destination
32-bit
volume will
32-bit or 64-bit or inherit source
64-bit Aggr 32-bit Aggr volumes
format on a

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

SnapMirror and SnapLock Compliance
(SLC)
No restrictions for qtree SnapMirror and SLC
volumes
No resync support for volume SnapMirror and SLC
volumes in GA releases
Obtain NetApp approval if this feature is desired
No SnapMirror Sync and SnapMirror Semi-Sync
support for SLC volumes

System Sizing for SnapMirror Async
The larger the data change rate, the higher the
SnapMirror throughput and the higher the impact
Assuming there is no system bottleneck
SnapMirror in Data ONTAP 7.3 adaptively throttles
back when there are resource constraints
Impact can be further minimized by throttling
SnapMirror
Recommend using SnapMirror Sizer
For SnapMirror network compression impact on the
system, refer to the SnapMirror Network Compression
tech report (TR-3790)
Rule of thumb: 60 Mbps compression throughput per
processing core
Network Sizing for SnapMirror Async
Use the Synergy SnapCalc plug-in to estimate network
throughput and to find bandwidth requirements
Know the amount of data change, network latency,
network pipe (if already present)
Successful updates depend on the above parameters
An example
RPO = 1 hour, daily change = 500GB
Amount of data to be transferred ~ 21GB/hr (500GB / 24
hours) or 6MB/sec
This means you will need at least 6MB/sec throughput to
be able to perform successful updates
If you know the network pipe and latency, SnapCalc can
give you the estimated throughput

System Sizing for SnapMirror Sync and
SnapMirror Semi-Sync
The following guidelines assume there are no other
bottlenecks such as disk and network
SnapMirror Sync
If the CPU cost of a write is 1X on a standard volume:
Size for 2X CPU cost when using lower number of concurrent
streams
Size for 3X CPU cost when using max. concurrent streams
If the CPU cost of a write is 1X on a standard volume:
Size for 1.5X CPU cost when using lower number of
concurrent streams
Size for 2.2X CPU cost when using max. concurrent streams
Size for ~ 2X the write throughput for network bandwidth
for SnapMirror Sync
Network Sizing for SnapMirror Sync and
The following guidelines are applicable to size network
bandwidth
SnapMirror Sync
2X the write throughput
If write throughput is 20MB/s, size for 40MB/s network
throughput
1X the write throughput
If write throughput is 20MB/s, size for 20MB/s network
throughput

Competitive Information

NetApp SnapMirror vs. Oracle Data Guard
NetApp SnapMirror Oracle Data Guard
Array-based Host-based; possible server
performance impact
Application agnostic Works only with Oracle DB
With FlexClone on DR site, In Snapshot standby mode, redo
replication is continuous logs are not appliedincreased RPO
IP or FC Works only over IP
Failback resync involved only new Failback speed an issuerequires full
changed blocks synchronization; increased exposure
when running at DR site
Throttling and compression available No throttling for replication

No charge for passive DR License cost at DR site
NetApp Confidential Limited

97Use
NetApp SnapMirror vs. Microsoft SCR
NetApp SnapMirror Microsoft SCR
Single replication solution for all applications Replication solution only for Exchange
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
Maximizes resource utilization of DR site with Active-passive configuration means idle

space-efficient cloned copies for active resources on passive node
business use such as dev/test, QA, and DR
testing
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

98Use
NetApp SnapMirror vs. EMC SRDF
NetApp SnapMirror EMC SRDF
Flexible; single replication solution Only for Symmetrix platforms
for all tiersFAS, N series, and V-
Series
Ease of use; set up and run in Complex; requires PS to install;
minutes; single interface different mgmt. interfaces for
different replication products
SnapMirror relies on our already When used with Time Finder, BCV
efficient Snapshot technology requires an entire set of disks
Synchronous replication not highly Robust synchronous replication
scalable
SnapMirror cannot replicate CG Consistency group support
Snapshot copies as a group
Integration with SnapSuite and Centralized management with
centralized management with Control Center; Replication Manager
Protection Manager is difficult to install, set up, and
configure

99Use
Sizing Tools

Tools Agenda
Concurrent Streams Calculator
Synergy Sizers for SnapMirror
Synergy SnapCalc
Replication Advisor
SnapMirror Progress Monitor

Concurrent Stream Calculator
Available on the Field Portal
The DPG Online Backup and Recovery Guide gives the
total number of available concurrent streams for a given
type of replication
What if I am using two or more types of replication?
Ex: SnapMirror Sync, SnapVault, QSM
The calculator gives the available number of concurrent
streams for different replication roles for a given storage
system

Concurrent Stream Calculator

SnapMirror Sizer
Available with CustomSizer, DBSizer, and
ExchangeSizer
Previous sizing for SnapMirror accounted for 20% flat
overhead
SnapMirror Async only (volume and qtree)
No bidirectional support in the first release
Available for Data ONTAP 7.3.x
SnapMirror throughput averaged over the entire window
Minimum of 15 minutes update window
Bandwidth can be defined

Synergy Sizers: CustomSizer

Synergy Quick Bandwidth Wizard
Available as a plug-in in Synergy tool suite
Estimates SnapMirror and SnapVault throughput
given: network bandwidth, latency, and packet loss
(optional)
Ability to choose increased window size in Data
ONTAP 7.3 for VSM
SnapMirror network compression not incorporated
On road map

Synergy Quick Bandwidth Wizard Results

Replication Advisor
Available on the Field Portal
Interactive learning tool to help differentiate various
NetApp replication products
Advises on best-fit replication products based on given
criteria, such as RPO, RTO, failover, etc.
Autofills the criteria for a selected replication product
User can further enhance his/her knowledge by
reviewing the listed references for each product in the
tool

Replication Advisor

Available on the NOW ToolChest
Provides progress on completion times and percentages for volume
SnapMirror updates
Does not work for qtree SnapMirror
V1.0 uses RSH protocol
V2.1 uses ZAPI + HTTP[S] protocols
V3.0 improvements
Ability to monitor multiple storage systems at the same time
Ability to connect to either source or destination storage systems
Ability to monitor data transfers of large amount of data
Ability to estimate data to be transferred without transferring
data
Link to the tool available in the References


Sample Deployments

Multipurpose Data Replication
Production Site DR Site DR Testing
Replication
Uninterrupted
FlexClone Tape
Volumes Library
SnapMirror
Flexible, easy, and efficient data replication with SnapMirror

Put the DR site to use by creating space-efficient copies for DR
testing, dev/test, and business intelligence
Production operations uninterrupted
Replication uninterrupted

Campus and Regional DR + Backup
Production Site Standby DR Site
SnapVault
Tape
Library
MetroCluster
SnapMirror
Campus HA and DR SnapVault can provide

Protection from long-term retention
regional disasters SnapMirror can extend
Off-site
Off-loading tape DR protection over Storage
backups long distance

DR with Volume SnapMirror and
SnapVault
Production Site Standby DR Site
FlexClone Volumes
Volume
SnapMirror SnapVault
Async
Multiple systems at primary data center

Disaster recovery for many systems
Protection from regional disasters
FlexClone volumes for multiple purposes
Stagger VSM and SV schedules
Exchange DR with SnapMirror
Production Site 1 Production Site 2
Utilize both sites
and infrastructure
SnapManager for

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

Data Distribution / Remote Access FlexClone volumes
can be made
Replicas can be instantly writable
used for read
access Primary Site
R/O R/W
R/O R/W R/W
Remote Site 1
Remote Site 2
One-to-many or many-to-one flexible configuration for async mode

Remote read-only replicas can be used for data distribution
Read-only replicas can be instantly made writable and used for
test, dev, and stage purposes

Flexible RPO
Primary Site
Remote Site
VolA VolA VolA
SnapMirror Sync SnapMirror Async
VolB
VolB
SnapMirror Async
SnapMirror offers flexible RPO in a single product

SnapMirror Sync and SnapMirror Async (VSM) can be cascaded in
the above configuration to achieve local and regional DR
Different volumes can be replicated at different intervals providing
wide-ranging RPO
References

References
On NOW (NetApp on the Web):
Data Protection Online Backup and Recovery Guide
Select the Data ONTAP version and the document
On the Field Portal (type SnapMirror in the search field):

SnapMirror Technical FAQ
SnapMirror Sales FAQ
SnapMirror Concurrent Streams Calculator
Synergy SnapCalc
Various NetApp Application Sizers
NetApp Replication Advisor Tool (Scotch)
TR-3561v2 SnapMirror Performance on Flexible Volumes
TR-3790 SnapMirror Network Compression
Data ONTAP SnapMirror Compatibility Matrix
Session 4085 from Insight 2008 Conference
SnapMirror Binder
SnapMirror Marketing Collateral
References
On www.netapp.com/us/library/technical-reports/
TR-3446 SnapMirror Async Overview and Best Practices Guide
TR-3326 SnapMirror Sync Overview and Design Considerations Guide
TR-3784 Data Protection Handbook
TR-3787 Oracle Data Protection Handbook
TR-3487 SnapVault Best Practices Guide
TR-3483 Thin Provisioning in a NetApp SAN Environment
TR-3505 Deduplication Best Practices Guide
TR-3548 MetroCluster Design and Implementation Guide
TR-3606 HA and DR for VMware Using SnapMirror and MetroCluster
TR-3958 NetApp Data Compression and Deduplication Deployment and
Implementation Guide: Data ONTAP 8.1 Operating in 7-Mode
TR-3978 In-Place Expansion of 32-Bit Aggregates to 64-Bit Overview
and Best Practices
Copyright 2009 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc.
Specifications are subject to change without notice. NetApp, the NetApp logo, Go further, faster, Data ONTAP, FilerView, FlexClone, FlexVol, NOW, RAID-DP,
SnapDrive, SnapManager, SnapMirror, SnapRestore, Snapshot, SnapSuite, SnapVault, SyncMirror, and WAFL are trademarks or registered trademarks of
NetApp, Inc. in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. Microsoft is a registered trademark of
Microsoft Corporation. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.

SnapMirror SE Training

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SnapMirror SE Training

Transféré par

Droits d'auteur :

Formats disponibles

SnapMirror SE

Srinath Alapati & Neil Shah

NetApp Confidential Limited Use

NetApp Confidential Limited Use 3

More Likely, Lower Impact Less Likely, Higher Impact

Operational Application Component Site & Data Regional

People and Bugs Controller Terrorist Attacks Electric Grid

Logical Local Physical Physical

NetApp Confidential Limited Use

More Likely, Lower Impact Less Likely, Higher Impact

Operational Application Component Site & Data Regional

NetApp Confidential Limited Use 5

NetApp Confidential Limited Use 6

NetApp Confidential Limited Use 7

NetApp Confidential Limited Use 8

NetApp Confidential Limited Use 9

NetApp Confidential Limited Use 10

NetApp Confidential Limited Use 11

Destination volume is read-only

NetApp Confidential Limited Use 12

Data ONTAP 7.2 Data ONTAP 7.3 Yes

Data ONTAP 7.3 Data ONTAP 7.2 No

Data ONTAP 7.3.x Data ONTAP 7.3.y Yes

NetApp Confidential Limited Use 13

NetApp Confidential Limited Use 14

NetApp Confidential Limited Use 15

NetApp Confidential Limited Use 16

NetApp Confidential Limited Use 17

Source-deduplicated volumes that are Qtrees in source-deduplicated volumes that

NetApp Confidential Limited Use 19

NetApp Confidential Limited Use 20

NetApp Confidential Limited Use 21

NVLOG and CP forwarding

NetApp Confidential Limited Use 22

Only CP forwarding; no NVLOG

NetApp Confidential Limited Use 24

NetApp Confidential Limited Use 25

NetApp Confidential Limited Use 26

SnapMirror Sync Source SnapMirror Sync Destination Replication

Data ONTAP 7.3.x Data ONTAP 7.3.x Yes

Data ONTAP 7.3.x Data ONTAP 7.3.y No

NetApp Confidential Limited Use 27

Limit on concurrent Yes No limit

NetApp Confidential Limited Use 28

NetApp Confidential Limited Use 29

SnapMirror works over both Ethernet and Fibre

NetApp Confidential Limited Use 30

Data ONTAP 7.3.x 8.0.x 8.1

7.3.x 32-bit Yes Yes 1 No Yes 1 Yes 1

32-bit No Yes No Yes 1 Yes 1

32-bit No No No Yes Yes

NetApp Confidential Limited Use 31

NetApp Confidential Limited Use 32

Data ONTAP 7.3.x 8.0.x 8.1

7.3.x 32-bit Yes Yes Yes Yes Yes

32-bit Yes Yes Yes Yes Yes

32-bit Yes Yes Yes Yes Yes

Qtree SnapMirror and SnapVault have no restrictions replicating between 32-

NetApp Confidential Limited Use 33

NetApp Confidential Limited Use 34

NetApp Confidential Limited Use 35

NetApp Confidential Limited Use 36

NetApp Confidential Limited Use 37