Module 12

Data Protection: Snapshot and

SnapMirror Copies

NetApp Confidential 1

MODULE 12: DATA PROTECTION: SNAPSHOT AND SNAPMIRROR COPIES

12-1 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Module Objectives
After this module, you should be able to:
 Create a Snapshot copy of a volume and create
Snapshot policies
 Create load-sharing (LS) and data-protection (DP)
mirror copies
 Manually and automatically replicate mirror copies
 Promote an LS mirror copy to replace its read/write
volume
 Restore a Snapshot copy to be a read/write volume
 Configure Vserver and cluster peering for data
protection

NetApp Confidential 2

MODULE OBJECTIVES

12-2 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Data-Protection Methods
 Snapshot copies
 Mirror copies for data protection and load sharing
 SnapVault backup copies
 Tape backups through third-party software
 Restores:
– volume snapshot restore
– LS mirrors: snapmirror promote
– DP mirrors: snapmirror resync
– Vault backups: snapmirror restore
– NDMP restore

NetApp Confidential 3

DATA-PROTECTION METHODS
A customer’s data-protection plan is likely to use all of the methods of protecting data that are shown here.

12-3 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Disaster Recovery

 Clustered Data ONTAP uses NDMP with

third-party software for disaster recovery.
 A clustered Data ONTAP system can be an
ndmpcopy source or destination.
 Data-protection intracluster and intercluster
mirrors are built-in, disk-to-disk backups.

NetApp Confidential 4

DISASTER RECOVERY
No native tape backup or restore commands are currently available in clustered Data ONTAP. All tape
backups and restores are performed through third-party NDMP applications.

12-4 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Lesson 1

NetApp Confidential 5

LESSON 1

12-5 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Snapshot Technology
 A Snapshot copy is a read-only image of the active
file system at a point in time.
 The benefits of Snapshot technology are:
– Nearly instantaneous application data backups
– Fast recovery of data that is lost due to:
 Accidental data deletion
 Accidental data corruption
 Snapshot technology is the foundation for these
NetApp products:
– SnapRestore – SnapManager
– SnapDrive – SnapMirror
– FlexClone – SnapVault

NetApp Confidential 6

SNAPSHOT TECHNOLOGY
Snapshot technology is a key element in the implementation of the WAFL (Write Anywhere File Layout) file
system:
 A Snapshot copy is a read-only, space-efficient, point-in-time image of data in a volume or aggregate.
 A Snapshot copy is only a “picture” of the file system, and it does not contain any data file content.
 Snapshot copies are used for backup and error recovery.
The Data ONTAP operating system automatically creates and deletes Snapshot copies of data in volumes to
support commands that are related to Snapshot technology.

12-6 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Volume Snapshot Functionality
 Snapshot copies can be created:
– Manually
– Automatically based on a schedule defined by Snapshot
policies
 A user can restore files and directories through a client:
– UNIX: .snapshot directory (visibility set at the volume)
– Windows: ~snapshot directory (visibility set at the share)
 A cluster administrator can restore an entire volume with
SnapRestore:
– Restores an entire volume (or an individual file)
– Command: volume snapshot restore
– Requires the SnapRestore license

NetApp Confidential 7

VOLUME SNAPSHOT FUNCTIONALITY

Snapshot functionality is controlled by management, which provides the UI for manual Snapshot copies and
the Job Manager policies and schedules for automated Snapshot operations. Each volume can have a Snapshot
policy associated with it. A policy can include multiple schedules, so that Snapshot copies are created hourly,
daily, weekly, and so on. A policy also indicates how many of each type of Snapshot copy to retain before
deleting older copies. For example, you can keep four hourly Snapshot copies, and when the fifth one is
created, the oldest one is removed, such that a continuously updated group of the previous four hourly
Snapshot copies is retained.
Clients can see and use the .snapshot directories, so users can restore their own data without administrator
intervention. When an entire volume needs to be restored from a Snapshot copy, an administrator uses the
volume snapshot promote command, which is basically the same as restoring the volume using
SnapRestore technology. The entire Snapshot copy is promoted, replacing the entire volume. Individual files
can only be restored through a client.

12-7 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Data ONTAP Snapshot Copy
PROD SNAP 1 SNAP 2
Production: Active File System
A A A
Prod
B B B
C C C
WRITE WRITE D D D
A B C D E F F’ E’ E’E E E
F’F F F’
F

S1 S2

SNAP #1 SNAP #2

NetApp Confidential 8

DATA ONTAP SNAPSHOT COPY

Before a Snapshot copy is created, there must be a file system tree that points to data blocks, which contain
content. When the Snapshot copy is created, the file structure metadata is saved. The Snapshot copy points to
the same data blocks as the file structure metadata that existed when the Snapshot copy was created.
Creating a Snapshot copy has no significant impact on disk space. Because the file structure takes up little
space, and no data blocks must be copied to disk, a new Snapshot copy consumes almost no additional disk
space. In this case, the phrase “consumes no space” really means no appreciable space. The so-called “top-
level root inode,” which contains metadata that is necessary to define the Snapshot copy, is 4 KB.
Snapshot copies begin to use space when data is deleted or modified. The WAFL file system writes the new
data to a new block (F’) on the disk and changes the root structure for the active file system to point to the
new block.
Meanwhile, the Snapshot copy still references the original block F. Any time that a Snapshot copy references
a data block, that block remains unavailable for other uses, which means that Snapshot copies start to
consume disk space only when the file system data changes after a Snapshot copy is created.

12-8 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Restore from a Snapshot
PROD SNAP
PROD1 SNAP 2
Production: Active File System
A A A
Prod
B B B
C C C
D D D
A B C D E F F’ E’ E’
E E E
F’
F F F’
F

Prod
S1 S2
Production:
SNAP #1 SNAP #2
Active
File System

NetApp Confidential 9

RESTORE FROM A SNAPSHOT

12-9 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 CLI: Snapshot Copy Creation
 To manually create Snapshot copies:
cluster1::> volume snapshot create -vserver vs0
-volume vol3 -snapshot vol3_snapshot

 To rename Snapshot copies:

cluster1::> volume snapshot rename -vserver vs0
-volume vol3 -snapshot vol3_snap -new-name
vol3_snap_copy

NetApp Confidential 10

CLI: SNAPSHOT COPY CREATION

EXAMPLE RESULT
Creates a Snapshot copy called “test” in the
snap create engineering test
engineering volume.
Lists all available Snapshot copies in the
snap list engineering
engineering volume.
Deletes the Snapshot copy “test” in the
snap delete engineering test
engineering volume.
snap delete –a vol2 Deletes all Snapshot copies in vol2.
snap rename engineering Renames the Snapshot copy from nightly.0 to
nightly.0 firstnight.0 firstnight.0 in the engineering volume.
Changes the Snapshot copy reserve to 25% on
snap reserve vol2 25
vol2.
Sets the automatic schedule on vol2 to save these
snap sched vol2 0 2 6 @ 8,
weekly Snapshot copies: 0 weekly, 2 nightly, and
12, 16, 20
6 hourly at 8 a.m., 12 p.m., 4 p.m., and 8 p.m.

12-10 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Snapshot Disk Consumption
 Snapshot Reserve Aggregate Space

Default is 5% Active File

System 95%
 Deleting a snapshot
– snapshot delete Snap Reserve 5%

– volume snapshot autodelete WAFL Reserve 10%

 volume snapshot compute-reclaimable

– Calculates the volume space that can be reclaimed
if one or more specified Snapshot copies are deleted
– Available in advanced mode
– Can not use the “*” wildcard

NetApp Confidential 11

SNAPSHOT DISK CONSUMPTION

12-11 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The volume snapshot show Command
netappu::> volume snap show -vserver vs7 -volume vs7_vol1
---Blocks---
Vserver Volume Snapshot Size Total% Used%
-------- ------- ---------------------------------- ------------ ------ -----
vs7 vs7_vol1
weekly.2011-09-22_0015 88KB 0% 37%
5min.2011-09-23_1120 76KB 0% 34%
5min.2011-09-23_1125 72KB 0% 33%
5min.2011-09-23_1130 92KB 0% 38%
weekly.2011-09-29_0015 56KB 0% 27%
daily.2011-10-02_0010 56KB 0% 27%
daily.2011-10-03_0010 52KB 0% 26%
hourly.2011-10-03_0605 52KB 0% 26%
hourly.2011-10-03_0705 52KB 0% 26%
hourly.2011-10-03_0805 52KB 0% 26%
hourly.2011-10-03_0905 52KB 0% 26%
hourly.2011-10-03_1005 52KB 0% 26%
hourly.2011-10-03_1105 52KB 0% 26%
13 entries were displayed.
NetApp Confidential 12

THE VOLUME SNAPSHOT SHOW COMMAND

The Snapshot copies shown here are scheduled Snapshot copies. The copies include two daily Snapshot
copies, six hourly Snapshot copies, and one weekly Snapshot copy.

12-12 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Snapshot Policies
 Created at the cluster level
 Assigned at the volume level
 Can be created with the CLI or OnCommand System manager
netappu::> volume snapshot policy show
Number Of Is
Name Schedules Enabled Comment
----------------- ---------- ------- ----------------------------------------
-
default 3 true Default policy with hourly, daily &
weekly schedules.
Schedule: hourly Count: 6 Prefix: hourly
daily 2 daily
weekly 2 weekly

none 0 false Policy for no automatic snapshots.

Schedule: - Count: - Prefix: -
2 entries were displayed.

NetApp Confidential 13

SNAPSHOT POLICIES
Two Snapshot policies are automatically created: default and none. If a volume uses none as its Snapshot
policy, no Snapshot copies of it will be created. If a volume uses the default policy, after two weeks, there
will be a total of ten Snapshot copies of it (six hourly copies, two daily copies, and two weekly copies).

12-13 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Snapshot Directory View
from a Windows Client

Snapshot copies are

visible to Windows
clients that have the
folder options
configured to display
“hidden files.”

NetApp Confidential 14

SNAPSHOT DIRECTORY VIEW FROM A WINDOWS CLIENT

Snapshot directories are hidden on Windows clients. To view them, you must first configure the folder
options to display hidden files, then navigate to the root of the CIFS share and find the directory folder.
The subdirectory for Snapshot copies appears to CIFS clients as ~snapshot. Files that are displayed here are
those files that are manually created Snapshot copies and those that are created automatically for specified
intervals.
Restoring a File
To restore a file from the ~snapshot directory, rename or move the original file, then copy the file from the
~snapshot directory to the original directory.

12-14 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Lesson 2

NetApp Confidential 15

LESSON 2

12-15 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The SnapMirror Engine
 Is used for the volume move, volume
copy, and snapmirror commands
 Uses SpinNP as the transport protocol
between the source and destination volumes
(intracluster only)
 Uses a Snapshot copy of the source,
determines the incremental differences, and
transfers only the differences
 Executes SnapVault backups

NetApp Confidential 16

THE SNAPMIRROR ENGINE

Internally, the incremental data transfer algorithm is used for moving, mirroring, and copying volumes. Data
is transferred over the network by using the proprietary SpinNP protocol. On the source side, Snapshot copies
of the volumes are used as the source of the data transfers so that the source volume itself can still be read
from and written to while the data transfer from the Snapshot copy occurs.

12-16 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 SnapMirror Considerations

 No qtree SnapMirror replication, but

replication by using volumes
 Asynchronous mirroring only
 DP and LS mirror copies
 Support for Vserver to Vserver replication
 Support for intercluster SnapMirror replication

NetApp Confidential 17

SNAPMIRROR CONSIDERATIONS

12-17 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LS and DP Mirror Copies
1 of 2
 Mirror copies are read-only copies of a volume.
 Mirror copies are volumes that have SnapMirror
relationships with source volumes.
 Mirror copies are updated from source volumes
manually, or automatically based on a scheduled.
 LS mirror relationships stay within the Vserver of the
source volume.
 DP mirror relationships can be within a Vserver,
between Vservers within the cluster, and between
Vservers of two different clusters.
 Mirrors cannot be cascaded.

NetApp Confidential 18

LS AND DP MIRROR COPIES: 1 OF 2

Mirror copies are read-only volumes. Each mirror copy has an association read/write volume and is labeled as
an LS or data-protection mirror copy. LS and data-protection mirror copies are similar conceptually, but the
type dictates how the mirror copy is used and maintained.
Mirror copies are copies of read/write volumes. Mirror copies are synchronized with the read/write source
volumes only to the extent that an administrator keeps them synchronized through manual replication or
scheduled (automated) replication. Generally, data-protection mirror copies do not need to be as up-to-date as
LS mirror copies do because of their different purposes.
Each mirror copy can have a replication schedule that is associated with it, which determines when (cron) or
how often (interval) replications are performed on the mirror copy. All LS mirror copies of a volume are
treated as a unified group and use the same schedule. The schedule is enforced by the UI, so if you choose a
different schedule for one LS mirror copy, the other LS mirror copies of that volume are automatically
changed to match. Each data-protection mirror copy is independent—it does not have to use the same
schedule as other data-protection mirror copies.
LS mirror relationships stay within the virtual storage server ( Vserver) of the source volume. Data-protection
mirrors can be within a Vserver, between Vservers within the cluster, and between Vservers of two different
clusters.

12-18 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LS and DP Mirror Copies
2 of 2
 A volume must be created before the volume can be
used as a mirror destination.
 A SnapMirror volume must be created as type DP, a
RW volume cannot be changed to a DP mirror.
 Creating a mirror relationship does not cause an initial
update to be performed.
 An LS mirror copy can be promoted to become the
source volume using the snapmirror promote
command.
 A DP mirror copy can be converted to a writable
volume using the snapmirror break command.
 A mirror copy can be “restored” to its source.

NetApp Confidential 19

LS AND DP MIRROR COPIES: 2 OF 2

All replication is performed directly from the read/write volume to the appropriate mirrors. This method is
different from the cascading that occurs within the Data ONTAP 7G operating system.
Creating a mirror copy, associating the mirror copy with a source volume, and replicating to it are separate
steps.
An LS or mirror copy can be promoted to replace its read/write volume. This is similar to using SnapRestore
technology to perform a restore.

12-19 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The snapmirror promote Command
For LS Mirrors Only
 The snapmirror promote command:
– Performs a failover to a destination volume
– Changes the destination volume to the new source
volume
 Read-only volume becomes read-write
 New source volume assumes the identity and SnapMirror
relationships of the original source volume
– Destroys the original source volume
 The destination volume must be an LS volume.
 Client accesses are redirected from the original
source volume to the promoted destination volume.

NetApp Confidential 20

THE SNAPMIRROR PROMOTE COMMAND: FOR LS MIRRORS ONLY

12-20 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Mirror Creation Steps
1. Create a (mirror) volume: volume create
2. Create a mirror relationship: snapmirror create
3. Perform baseline replication:
– Data protection: snapmirror initialize
– Load sharing: snapmirror initialize-ls-set
4. Perform incremental replication:
– Data protection: snapmirror update
– Load sharing: snapmirror update-ls-set

NOTE: The update commands work for the baseline

synchronization, too, so the initialize step can be skipped.

NetApp Confidential 21

MIRROR CREATION STEPS

12-21 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The snapmirror show Command
cluster1::> snapmirror show
Source Destination Mirror Relationship Total
Path Type Path State Status Progress Healthy
------------- ---- ------------ ------------- -------------- ---------- -------
cluster1://vs2/vs2root
DP cluster1://vs2/vs2root_dp1
Snapmirrored Idle - true
cluster1://vs2/vs2root_dp2
Snapmirrored Idle - true
LS cluster1://vs2/vs2root_ls2
Snapmirrored Idle - true
cluster1://vs2/vol227
XDP cluster2://vs7/xdp_vol227
Snapmirrored Idle - true
4 entries were displayed.

NetApp Confidential 22

THE SNAPMIRROR SHOW COMMAND

Notice that the volume that is called vs2root has three mirror copies: two data-protection mirror copies and
one LS mirror copy.

12-22 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The snapmirror show –instance
Command
cluster1::> snapmirror show -source-volume vs2root -type ls -instance

Source Path: cluster1://vs2/vs2root

Destination Path: cluster1://vs2/vs2root_ls2

Relationship Type: LS

Managing Vserver: vs2

SnapMirror Schedule: 5min

Tries Limit: 8

Throttle (KB/sec): unlimited

Mirror State: Snapmirrored

Relationship Status: Idle

Transfer Snapshot: -

Snapshot Progress: -

Total Progress: -

Snapshot Checkpoint: -

Newest Snapshot: snapmirror.79deda29-e8a6-11e0-b411-123478563412_4_2147484676.2011-10-05_023500

Newest Snapshot Timestamp: 10/05 02:35:00

Exported Snapshot: snapmirror.79deda29-e8a6-11e0-b411-123478563412_4_2147484676.2011-10-05_023500

Exported Snapshot Timestamp: 10/05 02:35:00

Healthy: true

NetApp Confidential 23

THE SNAPMIRROR SHOW –INSTANCE COMMAND

The instance view of the vs2root_ls2 mirror copy shows when the mirror copy was last replicated and other
information.

12-23 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LS Mirror Copies
 LS mirror copies are primarily used for load sharing
(balancing) when client read access is used.
 Read access requests for a volume are distributed to the
volume’s LS mirror copies, unless the special . admin path is
used.
 LS mirror copies are automatically available in the
namespace.
 LS mirror copies are implicitly accessed by clients (for read
access).
 Junctions are accessible in LS mirror copies.
 LS mirror copies are always replicated as a group.
 A source volume can have a maximum of one LS mirror copy
per node.

NetApp Confidential 24

LS MIRROR COPIES
The purpose of LS mirror copies is to offload volumes (and a single data module) of read activity. Therefore,
all mirror copies must be synchronized at the same data-version level. When a volume is replicated to its LS
mirror copies, all LS mirror copies of the volume are synchronized directly from the volume (without
cascading).
The way that NFS is mounted on a client, or which CIFS share is mapped to the client, changes which data is
accessed―either the read/write volume or one of its LS mirror copies. NFS is usually mounted at the root of a
Vserver by using a command such as mount <host>://myvserver. This command causes the LS
selection algorithm to be invoked. If, however, the NFS mount command is executed by using the . admin
path, such as mount <host>:/.admin /myvserver, this mount from the client always accesses the
read/write volumes when traversing the namespace, even if there are LS mirror copies for volumes.
For CIFS, the difference is not in how a share is accessed but in which share is accessed. If you create a share
for the . admin path and use that share, the client always has read/write access. If you create a share without
using . admin, the LS selection algorithm is used.
Unless the special .admin path is used, clients are transparently directed to an LS mirror copy for read
operations rather than to the read/write volume.

12-24 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LS Mirror Selection
The Data ONTAP operating system:
 If an LS mirror copy is on the same node as the network module
that fields the request, the network module uses that LS mirror
copy.
 If no LS mirror copy is on the same node as the network module
that fields the request, the network module uses an up-to-date
LS mirror copy on another node.
NFS and CIFS:
 NFS: A new LS mirror can be selected even if a file remains
open.
 CIFS: A new LS mirror is not selected while a file remains open.

NetApp Confidential 25

LS MIRROR SELECTION
When the / path is used (that is, the . admin path is not used) and a read or write request comes through that
path into the network module of a node, the network module first determines if there are any LS mirror copies
of the volume that it needs to access. If there aren’t any LS mirror copies of that volume, the read request is
routed to the read/write volume. If there are LS mirror copies of the volume, preference is given to an LS
mirror copy on the same node as the network module that fielded the request. If there isn’t an LS mirror copy
on that node, an up-to-date LS mirror copy from another node is chosen.
If a write request goes to an LS mirror copy, it returns an error to the client, which indicates that the file
system is read-only. To write to a volume that has LS mirror copies, you must use the . admin path.
For NFS clients, an LS mirror copy is used for a set period of time (minutes), after which a new LS mirror
copy is chosen. After a file is opened, different LS mirror copies can be used across different NFS operations.
The NFS protocol can manage the switch from one LS mirror copy to another.
For CIFS clients, the same LS mirror copy continues to be used for as long as a file is open. After the file is
closed, and the period of time expires, a new LS mirror copy is selected before the next time that a file is
opened. CIFS clients use this process because the CIFS protocol cannot manage the switch from one LS
mirror copy to another.

12-25 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Typical LS Mirror Issues
1 of 2
Client machines cannot see volumes that have
been created.
 The volume must be mounted (given a
junction path) to the namespace.
 Replicate the parent volume.

NOTE: You should schedule synchronization of

Vserver root volumes to run hourly.

NetApp Confidential 26

TYPICAL LS MIRROR ISSUES: 1 OF 2

12-26 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Typical LS Mirror Issues
2 of 2
 Client requests always go to the source volume rather than
to the LS mirror copy. This issue occurs when the client is
mounted by using the .admin path or share.
 Because the client is read-only, client write requests fail.
– This issue occurs when the client is not mounted by using the
.admin path or share.
– For read/write NFS access to a volume that has LS mirror
copies, clients must be mounted by using the .admin path.
– For read/write CIFS access to a volume that has LS mirror
copies, a specific volume .admin CIFS share must be created,
and the clients must connect to that share.

NetApp Confidential 27

TYPICAL LS MIRROR ISSUES: 2 OF 2

12-27 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 FlexCache Volumes and LS Mirror Volumes
1 of 2

A Origin volume

FlexCache volume
A’

B’ LS mirror volume

A’ A A’ A’

B’ B B’ B’ B’

NetApp Confidential 28

FLEXCACHE VOLUMES AND LS MIRROR VOLUMES: 1 OF 2

FlexCache volumes and LS mirror volumes can serve hosts from a local node in the cluster, instead of using
the cluster interconnect to access the node that stores the primary source of data. However, there are essential
differences between the two volume types and how they are used in a cluster.

12-28 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 FlexCache Volumes and LS Mirror Volumes
2 of 2

LS mirror volume FlexCache volume

 Complete copy of source  Only cached blocks

data  Not a disaster recovery
 Potential disaster option
recovery option  Read and write-through
 Read-only  Can simultaneously
 Created one at a time create on all nodes

NetApp Confidential 29

FLEXCACHE VOLUMES AND LS MIRROR VOLUMES: 2 OF 2

LS mirror volumes:
 Serve client requests by using a complete copy of the source data
 Can be promoted to a source volume and then used as a disaster-recovery solution
 Are read-only volumes, with the exception of admin privileges for write access or bypass of the LS mirror
 Are created by users one volume at a time
FlexCache volumes:
 Serve client requests by using a cached copy of the source data that contains only data blocks that are
accessed by clients
 Cannot be used for disaster recovery because they do not contain a complete copy of the source data
 Are read and write-through cache volumes
 Can be created by users one volume at a time, or can be simultaneously created on all the nodes that are
spanned by the Vserver that contains the origin volume

12-29 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 DP Mirror Copies
1 of 2
 DP mirror copies are not implicitly accessed by
clients.
 DP mirror copies can be mounted (through a junction)
into the namespace by the administrator.
 In DP mirror copies, junctions are not accessible.
 Each DP mirror copy replication is independent of the
LS mirror copies and of other DP mirror copies of the
same source volume.

NetApp Confidential 30

DP MIRROR COPIES: 1 OF 2
Data-protection mirror copies are not meant for client access, although they can be mounted into the
namespace by an administrator. Junctions cannot be followed in a data-protection mirror copy, so access is
given to only the data that is contained in that data-protection mirror copy, not to any other volumes that are
mounted to the source read/write volume.
Data-protection mirror copies are primarily meant for disk-based online backups. Data-protection mirror
copies are simpler, faster, more reliable, and easier to restore than tape backups are, although data-protection
mirror copies are not portable for storing offsite. A typical use of data-protection mirror copies is to put them
on aggregates of SATA disks that use RAID-DP technology and then mirror data to them daily during the
least active time in the cluster. One data-protection mirror copy per volume is generally sufficient.

12-30 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 DP Mirror Copies
2 of 2
 Consider using inexpensive, high-capacity (and slower)
SATA disks for DP mirror copies.
 DP mirror copies can be restored or resynchronized:
– To restore a mirror copy is to re-create a broken SnapMirror
relationship such that destination changes overwrite the
source data.
– To resynchronize a mirror copy is to re-create a broken
SnapMirror relationship such that source changes overwrite
the destination data.
– You can restore and resynchronize to a new volume.

NetApp Confidential 31

DP MIRROR COPIES: 2 OF 2
A feature that is available only for data-protection mirror copies is the ability to perform a SnapMirror restore.
This action can restore a broken mirror relationship between a source and destination and perform an
incremental overwrite of the source volume with the current contents of the mirror destination. If the restore is
performed between a source and destination that didn’t formerly have a SnapMirror relationship, a baseline
copy of the destination contents are performed to the source volume.
Resynchronizing a source and destination is similar to restoring a source and destination, except that the
source content overwrites the destination content.

12-31 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Intercluster Logical Interfaces and Ports
 Intercluster LIFs Ports Cluster LIFs
– New in Data
ONTAP 8.1
– Share data ports ifgrp1
with data LIFs or
e0a e0b e0c e0d
use dedicated
intercluster ports
– Node scoped!
failover only to
other intercluster
capable ports on Data LIFs
Intercluster LIFs
same node (IP Addresses)

NetApp Confidential 32

INTERCLUSTER LOGICAL INTERFACES AND PORTS

12-32 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Intercluster SnapMirror Replication
 Replication between clusters for DR
 Data transfers on intercluster network
RW Source volume

Intercluster LIF Intercluster

connection WAN network

DP Destination volume

NetApp Confidential 33

INTERCLUSTER SNAPMIRROR REPLICATION

Intercluster SnapMirror replication, as opposed to traditional intracluster mirroring, gives you the flexibility
to create an asynchronous SnapMirror volume on a cluster other than the source volume’s cluster for data
protection. The replication is carried out across the WAN by using intercluster logical interfaces (LIFs). You
can use intercluster SnapMirror replication to store online copies of your data off-site for disaster recovery.
To use intercluster SnapMirror replication, you must license the feature on both participating clusters.
You need a full mesh intercluster network to support node failover and volume moves of the source or
destination volumes. For the network to be full mesh, every intercluster LIF on every node in the cluster must
be able to connect to every intercluster LIF on every node in the peer cluster.

12-33 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Intercluster Networking for SnapMirror

 Requires the clusters to be peered together

 Requires full mesh connectivity of intercluster
LIFs

Every intercluster LIF on every

node in the cluster
WAN
should be able
to connect to every intercluster LIF
on every node in the other cluster.

NetApp Confidential 34

INTERCLUSTER NETWORKING FOR SNAPMIRROR

12-34 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Cluster and Vserver Peering
Supported relationships include:
 Intercluster (Cluster and Vserver peers required)
 Intracluster (Vserver peer required)

Source Destination Destination Destination

Vserver Peering is Required

Cluster and Vserver Peering is Required

NetApp Confidential 35

CLUSTER AND VSERVER PEERING

Supported configurations include intracluster and intercluster mirror and vault relationships. In intracluster
relationships, source and destination volumes can be on the same Vserver or different Vservers. In intercluster
relationships, source and destination volumes can be in different clusters.
Vserver peering is an infrastructure that enables you to manage the relationship between two Vservers and
provides authorization for applications to function between two Vservers. Cluster peering provides similar
intercluster management and authorization.
Establishing cluster peering is a one-time operation that must be performed by the cluster administrators. A
peer relationship can be created in two ways. In one method, a peer relationship is created by a cluster
administrator who has security credentials (a cluster admin login and password) for the other cluster. The
other method allows two administrators who do not want to exchange cluster admin passwords to peer their
clusters. In this method, each administrator enters the “cluster peer create” command specifying
intercluster IP addresses of the other cluster.
Vserver peer requirements include the following:
 A cluster peering relationship must exist before any Vserver peer relationships involving two clusters can
be created. This is not required if the Vservers reside in the same cluster.
 If Vservers are on different clusters, then execute “vserver peer create” and “vserver peer accept”. If
Vservers are on the same cluster, then execute ONLY “vserver peer create”.
 Vserver names involved in Vserver peering relationships must be unique.
 The languages of the two Vservers must be the same.
 Use the “vserver peer create” command.

12-35 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
Starting in clustered Data ONTAP 8.2, more granularity in SnapMirror security is provided. Replication
permission must be defined by peering Storage Virtual Machines together. Before creating any SnapMirror
relationships between a pair of Storage Virtual Machines, you must have a Storage Virtual Machine peer
relationship between the pair of Storage Virtual Machines. These Storage Virtual Machines can be local
(intracluster) or remote (intercluster). Storage Virtual Machine peering is a permission-based mechanism and
is a one-time operation that must be performed by the cluster administrators.

12-36 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 SnapMirror Snapshot Copies
1 of 2
bcluster1::> vol snap show -vserver vs2 -volume vs2root
(volume snapshot show)
---Blocks---
Vserver Volume Snapshot Size Total% Used%
-------- ------- ---------------------------------- ------------ ------ -----
vs2 vs2root
weekly.2011-10-02_0015 84KB 0% 1%
daily.2011-10-04_0010 80KB 0% 1%
snapmirror.79deda29-e8a6-11e0-b411-
123478563412_4_2147484684.2011-10-04_052359
0% 1%
92KB
hourly.2011-10-04_2105 72KB 0% 1%
hourly.2011-10-04_2205 72KB 0% 1%
hourly.2011-10-04_2305 72KB 0% 1%
hourly.2011-10-05_0005 72KB 0% 1%
daily.2011-10-05_0010 72KB 0% 1%
hourly.2011-10-05_0105 72KB 0% 1%

NetApp Confidential 36

SNAPMIRROR SNAPSHOT COPIES: 1 OF 2

The Snapshot copies that are shown on this slide are (mostly) scheduled Snapshot copies; three of them are
SnapMirror Snapshot copies. A separate reference Snapshot copy of a read/write volume (vs2root in this
example) is needed for every mirror copy that exists and that has a data version other than the read/write
volume. Because the replication process uses the SnapMirror Snapshot copy for a given mirror copy to
determine what has changed since the previous replication was performed, incremental mirroring is achieved
in this way. Because LS mirrors are synchronized, there should be only one SnapMirror Snapshot copy for all
of the LS mirrors. In this example, the other two SnapMirror Snapshot copies are for data-protection mirror
copies. If all LS and data-protection mirror copies are synchronized, there is one SnapMirror Snapshot copy,
and if there are no mirror copies, there are no SnapMirror Snapshot copies.

12-37 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 SnapMirror Snapshot Copies
2 of 2
---Blocks---
Vserver Volume Snapshot Size Total% Used%
-------- ------- ---------------------------------- ------------ ------ -----
snapmirror.79deda29-e8a6-11e0-b411-
123478563412_4_2147484683.2011-10-05_020500
0% 1%
60KB
hourly.2011-10-05_0205 72KB 0% 1%
snapmirror.79deda29-e8a6-11e0-b411-
123478563412_4_2147484676.2011-10-05_023500
0% 1%
72KB
12 entries were displayed.

NetApp Confidential 37

SNAPMIRROR SNAPSHOT COPIES: 2 OF 2

12-38 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Module Summary
Now that you have completed this module, you should
be able to:
 Create a Snapshot copy of a volume and create
Snapshot policies
 Create load-sharing (LS) and data-protection (DP)
mirror copies
 Manually and automatically replicate mirror copies
 Promote an LS mirror copy to replace its read/write
volume
 Restore a Snapshot copy to be a read/write volume
 Configure Vserver and cluster peering for data
protection
NetApp Confidential 38

MODULE SUMMARY

12-39 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Exercise
Module 12: Data Protection:
Snapshot and SnapMirror Copies
Time Estimate: 60 minutes

NetApp Confidential 39

EXERCISE
Please refer to your exercise guide.

12-40 Clustered Data ONTAP Administration: Data Protection: Snapshot and SnapMirror Copies

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.