STRSW Ilt Dataprot Rev6 Studentguide

Data ONTAP Data
Protection Administration
Student Guide
Content Version 2.0
NETAPP UNIVERSITY
Data ONTAP Data Protection Administration
Student Guide
Course ID: STRSW-ILT-DATAPROT-REV6
Catalog Number: STRSW-ILT-DATAPROT-REV6-SG
NetApp University - Do Not Distribute

ATTENTION
The information contained in this course is intended only for training. This course contains information and activities that,
while beneficial for the purposes of training in a closed, non-production environment, can result in downtime or other
severe consequences in a production environment. This course material is not a technical reference and should not,
under any circumstances, be used in production environments. To obtain reference materials, refer to the NetApp product
documentation that is located at http://now.netapp.com/.
COPYRIGHT
2015 NetApp, Inc. All rights reserved. Printed in the U.S.A. Specifications subject to change without notice.
No part of this document covered by copyright may be reproduced in any form or by any meansgraphic, electronic, or
mechanical, including photocopying, recording, taping, or storage in an electronic retrieval systemwithout prior written
permission of NetApp, Inc.
U.S. GOVERNMENT RIGHTS

Commercial Computer Software. Government users are subject to the NetApp, Inc. standard license agreement and
applicable provisions of the FAR and its supplements.
TRADEMARK INFORMATION
NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Clustered Data ONTAP,
Customer Fitness, CyberSnap, Data ONTAP, DataFort, FilerView, Fitness, Flash Accel, Flash Cache, Flash Pool,
FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, GetSuccessful, LockVault, Manage
ONTAP, Mars, MetroCluster, MultiStore, OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity,
Simulate ONTAP, SnapCenter, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager,
SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap,
Unbound Cloud, and WAFL are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other
countries.
Other product and service names might be trademarks of NetApp or other companies. A current list of NetApp trademarks
is available on the Web at http://www.netapp.com/us/legal/netapptmlist.aspx.
2 Data ONTAP Data Protection Administration: Welcome
2015 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.

TABLE OF CONTENTS
WELCOME........................................................................................................................................................... 1
MODULE 1: OVERVIEW OF NETAPP DATA PROTECTION TECHNOLOGIES ......................................... 1-1
MODULE 2: DATA PROTECTION WITH NETAPP SNAPSHOT COPIES .................................................... 2-1
MODULE 3: SYNCHRONOUS DATA PROTECTION .................................................................................... 3-1
MODULE 4: USING NDMP FOR DATA PROTECTION ................................................................................. 4-1
MODULE 5: IMPLEMENTING AND MANAGING SNAPMIRROR TECHNOLOGY ...................................... 5-1
MODULE 6: SNAPVAULT BACKUP AND RECOVERY ................................................................................ 6-1
MODULE 7: USING DATA PROTECTION MANAGEMENT SOLUTIONS .................................................... 7-1

Data ONTAP
Data Protection
Administration
Course ID: STRSW-ILT-DATAPROT-REV6
1 2015 NetApp, Inc. All rights reserved. NetApp Proprietary Limited Use Only
DATA ONTAP DATA PROTECTION ADMINISTRATION

Classroom Logistics
Getting Started Classroom Facilities Virtual Classroom

Schedule (start, Refreshments Collaboration
stop, breaks, tools
breakout Phones
sessions) Ground rules
Alarm signal
Activities and Phones and
Evacuation headsets
participation procedure
Materials Equipment check
Electrical safety
Support Be sure to sign in!
CLASSROOM LOGISTICS

Course Objectives
By the end of this course, you should be able to:

Describe Data ONTAP data protection technologies and data
protection management solutions
Create and manage Snapshot copies
Describe SyncMirror and MetroCluster configuration
Create and manage SnapMirror relationships
Create and manage SnapVault relationships
Configure NDMP for backing up to tape
Describe Data ONTAP and third-party management solutions
COURSE OBJECTIVES

Course Agenda
Session 1 (Day 1, Morning)

Module 0: Welcome (quick quiz and equipment check)
Module 1: Overview of NetApp Data Protection Technologies
Session 2 (Day 1, Afternoon)

Module 2: Data Protection with NetApp Snapshot Copies
Module 3: Synchronous Data Protection
Module 4: Using NDMP for Data Protection
Session 3 (Day 2, Morning)

Module 5: Implementing and Managing SnapMirror Technology
Module 6: SnapVault Backup and Recovery
Session 4 (Day 2, Afternoon)

Module 6: SnapVault Backup and Recovery
Module 7: Using Data Protection Management Solutions
COURSE AGENDA

Introductions
Name, Job Title, Goals for This Class
Virtual setting Classroom setting
I am Marc. I am a NetApp partner selling

to Enterprise customers in the medical
field
INTRODUCTIONS: NAME, JOB TITLE, GOALS FOR THIS CLASS

Take time to briefly get to know one another. If you are participating in a NetApp Virtual Live class, use the
chat window or the conference connection to speak with everyone. When called on, unmute your line, briefly
share your name, job title, and experience with the course topic. Mute your line again when you are finished
speaking.

Where Do You Live?
Click the whiteboard arrow. Your name appears on the arrow.

Place your arrow onto your location on the map.
WHERE DO YOU LIVE?

If you are participating in a NetApp Virtual Live class, you can practice using the classroom tools by clicking
the arrow key and pointing to where you are or where you are from. You can also point to where you would
like to be!

Ken, Your Guide to This Course
Ken is a professional who does the following:

Maintains and provisions storage
Responds to requests and issues
Follows best practices
Ken is a thoughtful person who asks
not only how, but also why. Ken is a
troubleshooter who solves storage problems.
KEN, YOUR GUIDE TO THIS COURSE

The final participant of this class is Ken, a representative IT professional with whom you might identify. Ken
asks key questions, helps to introduce concepts, and helps to summarize lessons learned.

Data ONTAP Learning Path
Fundamental Courses Intermediate Courses Advanced Categories
Clustered Data ONTAP Data ONTAP

Performance
Administration NFS Administration
Data ONTAP
Clustered Data ONTAP
SMB (CIFS) Troubleshooting
Installation Workshop
Administration
Data ONTAP Management

SAN Implementation Software
Data ONTAP Data Enterprise

Protection Administration Applications
You are here
DATA ONTAP LEARNING PATH

Following Clustered Data ONTAP Administration (and Installation Workshop, if necessary), intermediate
courses can be taken to further understand and support protocols, data protection, performance,
troubleshooting, management software, and enterprise applications.
Intermediate courses can be taken to match a particular role as needed.
Advanced categories should be taken only after taking all the intermediate courses. The advanced
categories typically contain one or more courses. See the NetApp University learning maps for more
details.

Ken Takes the Data Protection Assessment
I wonder how much I already

know about Data ONTAP
data protection.
KEN TAKES THE DATA PROTECTION ASSESSMENT

Like Ken, you also might already know a few things about Data ONTAP data protection technology. You can
take this quick 20-question quiz before the course to set your own personal baseline. The results of this quiz
are not reported to anyone and remain confidential. You have another opportunity to take this assessment after
the course to see how much you have learned.

ACTION: Pre-Class Assessment
20-Question Quiz
Instructor provides Duration: 20 minutes

exam link.
Open the Submit your

assessment in a answers.
browser.
Read and answer Click Submit after
each question. Observe your
each question. baseline score.
After the final

question, your
personal baseline
score is displayed
only to you.
Write down your
score.
ACTION: PRE-CLASS ASSESSMENT: 20-QUESTION QUIZ

To measure your current knowledge of data protection, take this pre-class assessment. At the completion of
the course, you can take the post-class assessment to measure how much you have learned.
All scores remain private.
Your instructor will provide the link to the assessment.

Class Equipment: Basic Architecture
Windows 2012 Server
Domain Controller
Laptop or
Classroom
Desktop Remote
Desktop
W2K12 CentOS 6.5
Data ONTAP 8.3

cluster1 cluster2
cluster1-01 cluster1-02 cluster2-01

(node1) (node2) (node1)
CLASS EQUIPMENT: BASIC ARCHITECTURE

Launch your exercise equipment kit from your laptop or from the classroom desktop. To connect to your
exercise equipment, use Remote Desktop Connection or the NetApp University portal.
The Windows 2012 Server is your windows domain controller for the LEARN windows domain. The
Windows Server hosts the domain DNS server.
Your exercise equipment consists of several servers:
A two-node NetApp Data ONTAP cluster
A one-node Data ONTAP cluster
A CentOS Linux server

ACTION: Exercise
Access your Duration: 15 minutes

exercise
equipment.
Open your
Use the login Exercise Guide.
credentials
provided Turn to Complete
by your Exercise 0. Exercise 0.
instructor.
Start with Participate in
Task 1. review session.
Stop at the
end of Q&A
Exercise 0.
ACTION: EXERCISE
See your Exercise Guide.

Share Your Experiences
Roundtable Questions for the Equipment-Based Exercise
Do you have any questions about your

equipment kit?
Do you have any issues to report?
SHARE YOUR EXPERIENCES: ROUNDTABLE QUESTIONS FOR THE EQUIPMENT-

BASED EXERCISE
If you encounter an issue, promptly notify your instructor so that the issue can be resolved before you begin
the exercise for Module 1.

Your Learning Journey
Bookmark These Links
NetApp University NetApp

NetApp University Overview New to NetApp Support Webcast
Find the training you need Ensure a successful support experience
Explore certification NetApp Support
Follow your learning map Access downloads, tools, documentation
NetApp University Community Customer Success Community

Join the discussion Engage with experts
NetApp University Support Welcome to Knowledgebase

Contact the support team Access a wealth of knowledge
YOUR LEARNING JOURNEY: BOOKMARK THESE LINKS

The NetApp University Overview page is your front door to learning. Find training that fits your learning map
and your learning style, learn how to become certified, link to blogs and discussions, and subscribe to the
NetApp newsletter Tech OnTap. http://www.netapp.com/us/services-support/university/index.aspx
The NetApp University Community page is a public forum for NetApp employees, partners, and customers.
NetApp University welcomes your questions and comments.
https://communities.netapp.com/community/netapp_university
The NetApp University Support page is a self-help tool that enables you to search for answers and to contact
the NetApp University support team. http://netappusupport.custhelp.com
Are you new to NetApp? If so, register for the New to NetApp Support Webcast to acquaint yourself with the
facts and tips that ensure that you have a successful support experience.
http://www.netapp.com/us/forms/supportwebcastseries.aspx?REF_SOURCE=new2ntapwl-netappu
The NetApp Support page is your introduction to all products and solutions support:
http://mysupport.netapp.com. To establish your support account and hear from the NetApp CEO, use the
Getting Started link (http://mysupport.netapp.com/info/web/ECMP1150550.html). Search for products,
downloads, tools, and documentation, or link to the NetApp Support Community
(http://community.netapp.com/t5/Products-and-Solutions/ct-p/products-and-solutions).
Join the Customer Success Community to ask support-related questions, share tips, and engage with other
users and experts. https://forums.netapp.com/
Search the NetApp Knowledgebase to learn from the accumulated knowledge of NetApp users and product
experts.
https://kb.netapp.com/support/index?page=home

Module 1
Overview of NetApp Data Protection
Technologies
MODULE 1: OVERVIEW OF NETAPP DATA PROTECTION TECHNOLOGIES
1-1 Data ONTAP Data Protection Administration: Overview of NetApp Data Protection Technologies

Module Objectives
After this module, you should be able to:

Recall Data ONTAP data protection technologies in the
context of the gamut of risks to data
Align Data ONTAP data protection technology to specific risks
Recall NetApp and third-party data protection management
solutions
Configure prerequisites for deploying Data ONTAP data
protection
MODULE OBJECTIVES

Lesson 1
Putting Data Protection
into Context
LESSON 1: PUTTING DATA PROTECTION INTO CONTEXT

Data Protection Requirements
Fast Backups and Restores
Quickly create mirror replicas and data archives
Quickly recover after file deletions, application
interruptions, data inconsistency, and viruses
Cost Efficiency and Simplicity

$$$$ Avoid purchasing multiple specialized devices
$$$$ Manage storage efficiently
$$$$
Avoid time-consuming deployments
Multiple specialized systems Avoid multiple silos of management, multiple
and the people to manage them
vendors, and multiple support contracts
Flexibility
Use systems for multiple purposes, including
virtual servers
Use systems for on-demand, multi-tenancy, IT as
a Service (ITaaS), and the cloud
DATA PROTECTION REQUIREMENTS

To provide data protection from the spectrum of risks, businesses design data protection plans. Data
protection plans encompass all backup and recovery processes that detail how to create copies of the data so
that it can be restored, even if the original data is not available.
Data protection plans require several abilities, including the ability to provide data protection that is fast, cost
efficient, simple, and flexible.
Fast Backups and Restores
Quickly create mirror replicas and data archives so that backups can be completed within a minimized
window of time
Quickly recover files that are lost due to accidental deletion, application interruptions, data inconsistency,
and viruses
Quickly recover data that is stored in private, public, and hybrid data centers that are in an IT as a service
(ITaaS) environment
Meet the recovery time objective (RTO) and recovery point objective (RPO) as promised in the
organizations SLA
Recovery Time Objective: The RTO is the amount of time within which the service, data, or process must be
made available again to avoid undesirable outcomes.
Recovery Point Objective: The RPO is a point to which data must be restored or recovered to comply with
the organizations acceptable data loss policy.
Clustered Data ONTAP data protection technology and management solutions offer features and methods that
protect data from accidental, malicious, and disaster-induced loss.

Data Protection Technologies and Management
NetApp Data ONTAP Data ONTAP Data Protection

Protection Technology Management Solutions
Third-Party Data Protection Management Solutions
DATA PROTECTION TECHNOLOGIES AND MANAGEMENT

NetApp data protection for FAS systems is based on the Data ONTAP built-in replication technologies, Data
ONTAP data protection management tools, and third-party data protection management solutions.


Snapshot copies
SnapRestore
SnapMirror
MetroCluster
SnapVault
FlexClone
NDMP protocol

The Data ONTAP built-in replication technologies include these products:
Snapshot copies are foundational to all Data ONTAP replication technologies.
SnapRestore software reverts files or volumes back to a point-in-time Snapshot copy.
MetroCluster high-availability disaster recovery software provides continuous access to data.
SnapMirror replication technology creates a read-only remote copy of primary data that is updated on a
schedule.
SnapVault software archives multiple point-in-time, read-only copies of data.
FlexClone software creates writable copies of volumes or LUNs.
NDMP is built into the Data ONTAP operating system for tape backups.


Snapshot copies Data ONTAP CLI
SnapRestore NetApp OnCommand System Manager
SnapMirror NetApp OnCommand Unified Manager
MetroCluster NetApp SnapManager Suite
SnapVault NetApp SnapProtect
FlexClone
NDMP

NetApp data protection management tools and solutions include the Data ONTAP CLI, OnCommand System
Manager, OnCommand Unified Manager, SnapManager products, and SnapProtect software.


FlexClone
NDMP

Symantec Plug-in for Data ONTAP
NDMP-compatible backup solutions
Scripted solutions system:\

Third-party data protection management solutions include Symantec NetBackup, any backup software that is
compatible with NDMP, and scripts that are written to work with the Data ONTAP API.

Lesson 2
Aligning Data ONTAP Data
Protection Technologies to the
Risk Spectrum
LESSON 2: ALIGNING DATA ONTAP DATA PROTECTION TECHNOLOGIES TO THE

RISK SPECTRUM

Data Loss Risk Spectrum
Degree of Severity and Scope Increasing Downtime
Failures and Disasters
Operational Site, Data

Failures Application Component Center, and Regional
(Accidental Failures Failures Power Disasters
Deletion) Failures
DATA LOSS RISK SPECTRUM

This slide illustrates the range of severity and scope of each type of risk. In terms of scope and severity, risk
can be confined to a local storage system or can extend to a regional disaster. On the low end, risk can entail
operational failures, such as the accidental deletion of a file. On the high end, risk can be an earthquake that
destroys the data center.
Operational failures: Pertains to data that is lost due to accidental deletion, data inconsistency, or viral
infection
Application failures: Pertains to data that is lost due to issues with an application
Component failures: Pertains to data becoming unavailable due to disk, network, or application host
failure
Site, Data Center, or Power Failures: Pertains to data becoming unavailable due to site failure, data
center failure, or power loss
Regional Disasters: Pertains to data becoming unavailable because of earthquakes or other regional
disasters
The data-loss spectrum also ranges from high to low probability incidents. A high-probability incident would
be the accidental deletion of a file. A low probability incident would be a regional disaster that destroys a data
center.

NetApp Protection Replication Technologies
Snapshot copies
SnapRestore data recovery software
SyncMirror software
MetroCluster configuration
SnapMirror replication
SnapVault archival backups
FlexClone volume clones
NDMP for tape backups
NETAPP PROTECTION REPLICATION TECHNOLOGIES

Functionalities of Data ONTAP provide you with continual access to or recovery of your data.
Snapshot copy functions: Create, schedule, and maintain multiple backups of data on the primary storage
volume to quickly restore data that is accidentally modified or deleted
SnapRestore functions: Revert a volume or a file to a previous Snapshot copy
SyncMirror functions: Synchronously write data to two different sets of disks in the same aggregate to
create a synchronous mirror of the aggregate
MetroCluster configuration functions: Fail over to a local high-availability partner or switch over to a
remote MetroCluster site
SnapMirror functions: Copy data from one FlexVol volume to another node within the same cluster or in a
different cluster
SnapVault functions: Create, schedule, and maintain multiple archive copes of a volume on a remote storage
system or cluster
FlexClone volume clone functions: Create point-in-time, space-efficient, writable copies of a volume by
using the Data ONTAP FlexClone license
NDMP functions: Use Data ONTAP and backup solutions to stream data to tape

NetApp Data Protection Across the Risk
Spectrum
Application Component Site, Data Center,

Failures Failures and Power Failures
Operational or Archive and

Regional Archive and
Accidental Retrieve
Disasters Retrieve Data
Data Loss Historical Data
Snapshot SnapRestore SnapMirror SnapVault NDMP

copies (revert to point- (disaster (disk-to-disk (disk-to-tape
(local backups) in-time copy) recovery short-term long-term
failover that is archival) archival)
not limited by
distance)
Snapshot Copy Foundational Technology
NETAPP DATA PROTECTION ACROSS THE RISK SPECTRUM

The Data ONTAP technologies provide protection across a spectrum of degree of risk. Local Snapshot copies
and SnapRestore recovery software provide for recovery from operational failures, accidental deletions,
application failures, or any data loss that does not involve hardware failure of primary storage.
SnapMirror software provides protection across the whole spectrum of risk. SnapMirror software provides
failover capabilities for the same types of risks as Snapshot copies; also, SnapMirror software can provide
failover for regional disasters.
SnapVault software provides a disk-to-disk archive for the fast retrieval of aged data. For long-term archival
of data, Data ONTAP NDMP enables you to offload data to tape libraries and retrieve historical data when the
need arises.

Snapshot Copy and SnapRestore Technologies
Foundational Replication Technology
Snapshot copies SnapRestore software

Provide a point-in-time, read- Reverts a volume back to a
only copy of the file system point-in-time Snapshot copy
Do not consume disk space Restores aggregates, volumes,
LUNs, or files from Snapshot
Consist of blocks that cannot copies
be overwritten
Active Data Snapshot Copy Active Data

File or LUN X File or LUN X File or LUN X
Disk A B C Disk A B C
Blocks Blocks
SNAPSHOT COPY AND SNAPRESTORE TECHNOLOGIES: FOUNDATIONAL

REPLICATION TECHNOLOGY
Snapshot copy technology is the foundation for SnapRestore, MetroCluster, SnapMirror, and SnapVault
software, and for NDMP backup operations. Snapshot copy technology is a key element of the Data ONTAP
WAFL (Write Anywhere File Layout) file system. A Snapshot copy is a read-only, space-efficient copy of a
traditional volume, a FlexVol volume, or an aggregate that captures the state of the file system at a point in
time. A Snapshot copy is only a picture of the file system. A Snapshot copy is not a duplication of the data
blocks that the volume or aggregate contain. Snapshot copies are your first line of defense to back up and
restore data.
SnapRestore software is the foundational technology for reverting a volume back to a point-in-time Snapshot
copy. To restore aggregates, volumes, LUNs, or files from Snapshot copies, use the SnapRestore feature.

MetroCluster Technology
Continuous Availability for Mission-Critical Applications
MetroCluster provides:
Near zero data loss
Near zero application downtime
Set-it-once simplicity Up to 200 km
Near zero change management
MetroCluster
Seamless integration with storage
efficiency, backup, disaster
recovery, nondisruptive operations
(NDO), non-FAS storage Multiple recovery points
with Snapshot copies
METROCLUSTER TECHNOLOGY: CONTINUOUS AVAILABILITY FOR MISSION-

CRITICAL APPLICATIONS
MetroCluster software addresses the need to provide continuous data availability beyond the data center (or
beyond the cluster), and it does so natively in Data ONTAP.
MetroCluster is an active-active solution, meaning that all nodes in each cluster actively serve data to
applications. Data can be read from the primary and secondary clusters, a feature that can also improve read
performance. MetroCluster technology is foundational for creating an active-active data center, like Ciscos
Virtualized Multi-Tenant Data Center concept.

SnapMirror Technology
Provides a Remote Disaster Recovery Site
Snapshot
SnapMirror copies SnapMirror
source destination
SnapMirror
Intracluster SnapMirror
relationships require storage
virtual machine (SVM) peering.
WAN
SnapMirror
Intercluster SnapMirror
Long-term
relationships require cluster archived data
peering and SVM peering.
SnapMirror Tape
FlexClone destination
volumes
SNAPMIRROR TECHNOLOGY: PROVIDES A REMOTE DISASTER RECOVERY SITE

SnapMirror Uses and Benefits
SnapMirror technology in clustered Data ONTAP provides asynchronous volume-level replication based on a
configured replication update interval. SnapMirror technology uses NetApp Snapshot copy technology as part
of the replication process.
SnapMirror relationships consist of source and destination volumes. The SnapMirror source and destination
volumes can be in the same cluster (intracluster) or in different clusters (intercluster). Intracluster SnapMirror
relationships require that the storage virtual machines (SVMs) be configured as SVM peers (also called
Vserver peers). Intercluster SnapMirror relationships require cluster peering and SVM peering.
Instead of leaving the mirrored volume unused in the colocation, SnapMirror technology enables you to use
the destination volume to create Data ONTAP FlexClone volume clones. You can create a clone of the
destination volume without affecting performance on the source volume. You can also use the destination
volume to offload to tape.

SnapVault Technology
Provides Secondary Archive Storage
Snapshot SnapVault
Primary copies secondary
volume volume
SnapVault
Archived data
Intracluster SnapVault
relationships require
SVM peering.
WAN
SnapVault
Intercluster SnapVault
Long-term
relationships require cluster archived data
peering and SVM peering.
SnapVault Tape
FlexClone
secondary
volumes
volume
SNAPVAULT TECHNOLOGY: PROVIDES SECONDARY ARCHIVE STORAGE

SnapVault technology is a NetApp disk-to-disk backup solution that is built into the Data ONTAP operating
system. A SnapVault backup is a collection of Snapshot copies on a FlexVol volume, from which you can
restore data if the primary data is not usable.
The difference between SnapMirror and SnapVault technology is that SnapMirror technology provides an up-
to-date failover mirror of the data on the primary volume, whereas SnapVault provides long-term, storage-
efficient retention of backups. SnapVault relationships enable you to back up selected Snapshot copies of
volumes to a destination volume and to retain the backups.

NDMP Technology
Protocol to Communicate with Disk-to-Tape Backup Applications
NDMP is an industry-standard protocol that can control

backup, recovery, and data transfer between primary and
secondary storage devices.
All communications occur over TCP/IP or TCP/IPv6.
NDMP provides low-level control of tape and media changers.
NDMP TECHNOLOGY: PROTOCOL TO COMMUNICATE WITH DISK-TO-TAPE

BACKUP APPLICATIONS
NDMP is an industry-standard protocol for controlling backup, recovery, and data transfer between primary
and secondary storage devices, including storage systems and tape libraries.
Enabling NDMP on a NetApp storage system enables that storage system to communicate with NDMP-
enabled backup applications.

ACTION: Take a Poll
Check Your Understanding
Instructor begins Duration: 5 minutes

polling session.
Questions Instructor ends

appear in the polling session.
polling panel.
Answer each Correct
question. Instructor leads
answers have debrief discussion.
When finished, a green check
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.
ACTION: TAKE A POLL: CHECK YOUR UNDERSTANDING

This poll has two quick questions about risk and the appropriate data protection technology. When the
instructor begins the polling session, you see the polling questions that you are to answer. After all answers
are submitted, the instructor closes the poll.
After the polling session ends, the instructor briefly answers questions for you.

Poll Questions
1. Which Data ONTAP technology provides remote archive to

disk that can be offloaded to tape?
a. Snapshot
b. SnapVault
c. NDMP
d. SnapRestore
2. Which Data ONTAP technology protects against disasters

that affect a region greater than 200 km?
a. MetroCluster
b. Snapshot
c. SnapMirror
d. SnapRestore
POLL QUESTIONS: CHECK YOUR UNDERSTANDING

Lesson 3
Data Protection Management
Interfaces and Solutions
LESSON 3: DATA PROTECTION MANAGEMENT INTERFACES AND SOLUTIONS

Using the Data ONTAP CLI
You can manage data protection for Data ONTAP clusters by

connecting to the command line.
USING THE DATA ONTAP CLI

NetApp management interfaces begin with the Data ONTAP CLI. To connect to the storage system or the
cluster CLI, use a Telnet or Secure Shell (SSH) client. If the storage system is not online, use a terminal
server to connect to the command line through the console. You can automate or schedule data protection or
use scripts to automate data protection.

Using NetApp OnCommand System Manager
NetApp Data ONTAP UI
OnCommand System Manager is built into Data ONTAP and

can be used for most administration tasks.
To access a
cluster, use a
browser.
Manage at the
cluster, SVM,
and node levels.
USING NETAPP ONCOMMAND SYSTEM MANAGER: NETAPP DATA ONTAP UI

The basic UI that you can use to manage aggregates, SVMs, volumes, shares, exports, network settings, and
other configurations is NetApp OnCommand System Manager. Set up and manage NetApp storage systems
from this management interface that is built into the Data ONTAP 8.3 operating system.
You cannot use versions 1.0 or 1.1 of NetApp System Manager to configure SnapMirror, SnapVault, or Open
Systems SnapVault software. To manage data protection operations with OnCommand System Manager, you
must use System Manager 2.0 or later.
If you are working with Data ONTAP 8.3, access the OnCommand System Manager UI by opening a browser
and entering the cluster management logical interface (LIF) IP address.

Using NetApp OnCommand Unified Manager
NetApp Data ONTAP Management Application
The OnCommand Unified Manager enables you to manage

data protection tasks with policies:
Create policy-based SnapVault and SnapMirror relationships.
Manage data protection globally.
Unprotected data
USING NETAPP ONCOMMAND UNIFIED MANAGER: NETAPP DATA ONTAP

MANAGEMENT APPLICATION
With OnCommand Unified Manager, you can manage Data ONTAP storage worldwide from a central
console. OnCommand Unified Manager has several features for monitoring and configuring storage systems
and clusters, such as error messages, reports, performance metrics, and configuration tools. With
OnCommand Unified Manager, you can simplify data protection tasks and apply user-defined policies to
select resources for each provisioning activity.

Ken Asks
A few of my customers do have

NetApp management software.
But what do I do about the

customers who use other types
of backup applications?
KEN ASKS

NetApp Plug-In for Symantec NetBackup
Symantec NetBackup Replication Director
This NetApp plug-in combines Symantec NetBackup software

with NetApp SnapVault and SnapMirror replication
technologies.
NETAPP PLUG-IN FOR SYMANTEC NETBACKUP: SYMANTEC NETBACKUP

REPLICATION DIRECTOR
The combination of Symantec NetBackup software with NetApp SnapVault and SnapMirror replication
technologies provides an integrated and scalable disk-based data-protection and recovery solution.
To integrate Symantec and Data ONTAP replication, use the following procedure:
Install the NetApp Plug-in for Symantec and the NetApp OnCommand Core Package on the same host.
Configure the plug-in and the OnCommand Unified Manager server to the same storage system.
The OnCommand Unified Manager server creates primary Snapshot copies on the primary NetApp storage
system.
The copies are replicated to the secondary storage system by using a SnapMirror, SnapVault, or tape
replication process.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick quiz on the overview of NetApp data protection management interfaces and solutions.
When the instructor begins the polling session, you see the polling questions that you are to answer. After all
answers are submitted, the instructor closes the poll.
After the polling session ends, the instructor briefly answers questions for you.

Poll Questions
1. Which management solution is built into the Data ONTAP

operating system?
a. OnCommand System Manager
b. OnCommand Unified Manager
c. SnapManager for Exchange
d. NetApp SnapProtect
2. Which third-party solution can interoperate with Data

ONTAP through a plug-in?
a. Syncsort MFX
b. Symantec NetBackup
c. Mondo Rescue
d. Redo Backup and Recovery

Lesson 4
Configuring Data Protection
Required Prerequisites
LESSON 4: CONFIGURING DATA PROTECTION REQUIRED PREREQUISITES

Prerequisite Data Protection Configurations
To implement Data ONTAP data protection, several prerequisite

configurations are required:
Intercluster failover groups
Cluster peering
SVM peering
PREREQUISITE DATA PROTECTION CONFIGURATIONS

To implement Data ONTAP data protection, you replicate data between SVMs within and between Data
ONTAP clusters. You first need to configure intracluster and intercluster secure communications by
establishing the following configurations on the primary and secondary clusters and SVMs:
Intercluster subnet and interface group
Cluster peering
SVM peering
Details of each CLI command follow in this section of the module. In the exercise that follows this lecture,
you use the OnCommand System Manager UI to practice these configurations.

Configure an Intercluster Failover Group
Failover Groups Used for Intercluster Networking
This command creates the failover group and assigns port e0c to it.
cluster1::> network interface failover-groups create

-vserver cluster1 -failover-group failover_cluster1
-targets cluster1-01:e0c
cluster1::> network interface failover-groups
add-targets -vserver cluster1
-failover-group failover_cluster1
-targets cluster1-01:e0d
This command adds port e0d to the failover group.

You use the administration SVM (cluster1) in these commands.
CONFIGURE AN INTERCLUSTER FAILOVER GROUP: FAILOVER GROUPS USED

FOR INTERCLUSTER NETWORKING
The network interface failover-groups create command used to configure the intercluster
failover group on node 1 of the primary cluster has three main options:
The vserver option identifies the SVM that will use the failover group.
The failover-group option names the failover group.
The targets option lists the nodes and ports to be included in the failover group. You can list two
targets separated by a comma. (Example: -targets cluster1-01:e0c,e1c)
The target nodes for intercluster failover groups must be ports that all reside on the same node. Although
other types of LIFs allow failover groups to fail over to a different node, intercluster failover groups must fail
over to ports on the same node.
Use the network interface failover-groups add-targets command to add failover targets
to a failover group. In the following example, failover group failover_cluster1 is being
extended to include additional failover targets:
cluster1::> network interface failover-group add-targets -vserver vs1 -
failover-group failover_cluster1 -targets cluster1-01:e0c, cluster1-
01:e0d-100, cluster1-02:a0a

Configure Node 2 of the Cluster
Perform the Same Steps on node2 of the Cluster
You must create a failover group with a unique name:

-vserver cluster1 -failover-group failover_cluster1-2
-targets cluster1-02:e0c,e0d
CONFIGURE NODE 2 OF THE CLUSTER: PERFORM THE SAME STEPS ON NODE2

OF THE CLUSTER
You must create a failover group for each node of the cluster. This slide shows an example of creating a
failover group on node 2 of cluster1. In this example, rather than use the failover-group add-
targets command, two ports are specified as failover targets in the failover-group create
command. The two ports are cluster1-02, e0c, and e0d.

Configure an Intercluster LIF on Node 1
Create an Intercluster LIF on Node 1 of the Cluster
cluster1::> network interface create

-vserver cluster1
-lif failover_cluster1 -role intercluster
-home-node cluster1-01 -home-port e0c
address 192.168.1.50 -netmask 255.255.255.0
-failover-policy local-only
-firewall-policy intercluster
This command creates the intercluster LIF

on node cluster1-01.
CONFIGURE AN INTERCLUSTER LIF ON NODE 1: CREATE AN INTERCLUSTER LIF

ON NODE 1 OF THE CLUSTER

Configure an Intercluster LIF on Node 2
Create an Intercluster LIF on Node 2 of the Cluster
This command creates the intercluster LIF on node

cluster1-02:
cluster1::> network interface create vserver cluster1
-lif failover_cluster1-2 role intercluster
-address 192.168.1.60 -netmask 255.255.255.0
The intercluster failover policy must be configured for

local-only. Failover to a different node is not supported for
intercluster LIFs.
CONFIGURE AN INTERCLUSTER LIF ON NODE 2: CREATE AN INTERCLUSTER LIF

ON NODE 2 OF THE CLUSTER

Verify Network Interface Configurations
Verify that the intercluster LIFs were created properly:

cluster1::> network interface show -role intercluster
Verify that the intercluster LIFs are configured to be

redundant:
cluster1::> network interface show
role intercluster -failover
VERIFY NETWORK INTERFACE CONFIGURATIONS

Check your work. Verify that the intercluster LIFs were created properly.
Logical Status Network Current
Current Is
SVM Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ----------------- -------------
------- ----
cluster1
failover_cluster1 up/up 192.168.1.50/24 cluster1-0 e0c
true
failover_cluster1-2 up/up 192.168.1.60/24 cluster1-02 e0c
true
2 entries were displayed.

Verify that the intercluster LIFs are configured to be redundant:
cluster1::> network interface show -role intercluster -failover
Logical Home Failover
Failover
Vserver Interface Node:Port Policy
Group
-------- --------------- --------------------- ---------------
---------------
cluster1
failover_cluster1 cluster1-01:e0c local-only failover_cluster1
Failover Targets: cluster1-01:e0c, cluster1-01:e0d
failover_cluster1-2 cluster1-02:e0c local-only failover_cluster1
Failover Targets: cluster1-02:e0c

ACTION: Try This
View Configurations of the Network Interfaces
In your exercise kit, log in to cluster 1 and enter the following

commands to view network configurations.
Are there intercluster LIFs?
If so, are intercluster LIFs configured to fail over?

role intercluster -failover
ACTION: TRY THIS: VIEW CONFIGURATIONS OF THE NETWORK INTERFACES

In your exercise kit, try to determine if cluster1 has intercluster LIFs. If so, are the intercluster LIFs
configured to fail over?
Log in to the cluster1 CLI and enter the following commands:

View and Configure Intercluster Routes
Configure Intercluster Routes on Primary and Secondary (Peer) Clusters
Display the routes in the cluster:

cluster1::> network route show
Create an intercluster route:

cluster1::> network route create -vserver cluster1
-destination 0.0.0.0/0 -gateway 192.168.1.1
-metric 40
Important:
The destination cluster must be configured with intercluster LIFs.
VIEW AND CONFIGURE INTERCLUSTER ROUTES: CONFIGURE INTERCLUSTER

ROUTES ON PRIMARY AND SECONDARY (PEER) CLUSTERS
Display the routes in the cluster:
Vserver Destination Gateway Metric
------------------- --------------- --------------- ------
Cluster1 0.0.0.0/0 192.168.0.1 20
Create an intercluster route:
cluster1::> network route create -vserver svm1 -destination 0.0.0.0/0 -
gateway 192.168.1.1 -metric 40
------------------- --------------- --------------- ------
cluster1
0.0.0.0/0 192.168.0.1 20
svm1
0.0.0.0/0 192.168.1.1 40
Important: These steps must be performed on the peer cluster.

Configure the Secondary Cluster (Cluster 2)
Configure a Failover Group on the Secondary Cluster
In this example, the second cluster is a single-node cluster.

Check the cluster2 network ports:
cluster2::> network port show
Create a failover group on cluster2:

-vserver cluster2 -failover-group failover_cluster2
-targets cluster2-01:e0c,e1c
CONFIGURE THE SECONDARY CLUSTER (CLUSTER 2): CONFIGURE A FAILOVER

GROUP ON THE SECONDARY CLUSTER
Now that the two nodes of the primary cluster have been configured, you configure the secondary cluster for
intercluster networking. Cluster2 is a single-node cluster. Similar to the configuration of the primary cluster,
you must configure intercluster failover groups and intercluster LIFs on the secondary cluster, cluster2. Use
the following command to configure an intercluster failover group for the single node of cluster2:
cluster2::> network port show
Speed (Mbps)
Node Port IPspace Broadcast Domain Link MTU Admin/Oper
------ --------- ------------ ---------------- ----- ------- ------------
cluster2-01
e0a Default Default up 1500 auto/1000
e0b Default Default up 1500 auto/1000
e0c Default Default up 1500 auto/1000
e0d Default Default up 1500 auto/1000
e0e Default Default up 1500 auto/1000
e0f Default Default down 1500 auto/10
Create a failover group on cluster2:
cluster2::> network interface failover-groups create -vserver cluster2 -
failover-group failover_cluster2 -targets cluster2-01:e0c,e0d

Create the Intercluster LIF on Cluster 2
cluster2::> network interface create -vserver cluster2

-lif failover_cluster2 -role intercluster
-address 192.168.1.51 -netmask 255.255.255.0
-role intercluster
-role intercluster-failover
CREATE THE INTERCLUSTER LIF ON CLUSTER 2

Similar to the configuration of the primary cluster, you must configure intercluster LIFs on the secondary
cluster, cluster2. An example of the CLI command follows:
cluster2::> network interface create -vserver cluster2 -lif failover_cluster2 -
role intercluster -home-node cluster2-01 -home-port e0c -address 192.168.1.51 -
netmask 255.255.255.0 -failover-group failover_cluster2 -failover-policy local-
only -firewall-policy intercluster
Use the following command to verify network configurations:
Logical Status Network Current Current
Is
Vserver Interface Admin/Oper Address/Mask Node Port
Home
----------- ---------- ---------- ------------------ ------------- -------
----
cluster2
failover_cluster2
up/up 192.168.1.51/24 cluster2-01 e0c
true

Logical Home Failover Failover
Vserver Interface Node:Port Policy Group
-------- ------------ --------------------- --------------- ---------------
cluster2
cluster2

Create an Intercluster Route on Cluster 2
Create the network route on cluster2 for the intercluster

subnet.
cluster2::> network route create -vserver cluster2
-destination 0.0.0.0/0 -gateway 192.168.1.1
-metric 40
Verify that the network route was created correctly:

CREATE AN INTERCLUSTER ROUTE ON CLUSTER 2

Similar to the configuration of the primary cluster, you must configure an intercluster network route on
cluster2 for the intercluster subnet.
cluster2::> network route create -vserver cluster2 -destination 0.0.0.0/0
-gateway 192.168.1.1 -metric 40
Verify your configuration:

------------------- --------------- --------------- ------
cluster2
0.0.0.0/0 192.168.0.1 20
0.0.0.0/0 192.168.1.1 40

Configure Cluster and SVM Peer Relationships
Are there peer relationships between clusters and SVMs?
cluster1::> cluster peer show

This table is currently empty.
cluster1::> vserver peer show
There are no SVM peer relationships.
CONFIGURE CLUSTER AND SVM PEER RELATIONSHIPS

Configure Cluster Peering on Cluster 1
Create the Peer Relationship on Cluster1
Create the peer relationship between the two clusters:

cluster1::> cluster peer create
-peer-addrs 192.168.1.51
The IP address points to the IP address that

is configured on the destination cluster.
When you are prompted for a passphrase, enter the cluster

administrators password.
CONFIGURE CLUSTER PEERING ON CLUSTER 1: CREATE THE PEER

RELATIONSHIP ON CLUSTER1
Use the following CLI commands to create a peer relationship between the two clusters.
cluster1::> cluster peer create -peer-addrs 192.168.1.51
Notice: Choose a passphrase of 8 or more characters. To ensure the
authenticity of the peering relationship, use a phrase or sequence of
characters that would be hard to guess.
Enter the passphrase:
Confirm the passphrase:
Notice that the IP address in the previous command points to the IP address that was created on the
destination cluster.

Configure Cluster Peering on Cluster 2
Create the Peer Relationship on Cluster2
Repeat the same CLI command on the peer cluster:

cluster2::> cluster peer create
-peer-addrs 192.168.1.50,192.168.1.60
The two IP addresses point to the two IP

addresses that are configured on the peer cluster.
Verify that cluster peering was created correctly:

cluster2::> cluster peer show -instance
CONFIGURE CLUSTER PEERING ON CLUSTER 2: CREATE THE PEER

RELATIONSHIP ON CLUSTER2
The cluster peering relationship must be created on both clusters. Repeat the same configuration on the cluster
peer partner, cluster2:
cluster2::> cluster peer create -peer-addrs 192.168.1.50,192.168.1.60
Notice: Choose a passphrase of 8 or more characters. To ensure the
authenticity of the peering relationship, use a phrase or sequence of
characters that would be hard to guess.
Enter the passphrase:
Confirm the passphrase:
Verify that the cluster peer relationship is reported as Available and authentication is reported as ok:
Peer Cluster Name Cluster Serial Number Availability Authentication
------------------------- --------------------- -------------- --------------
cluster1 1-80-000099 Available ok
Peer Cluster Name Cluster Serial Number Availability Authentication
------------------------- --------------------- -------------- --------------
cluster2 1-80-000099 Available ok

Verify all details of the cluster peer relationship with the cluster peer show instance
command. The output shows the following details and many more that are not shown on this
page:
cluster1::> cluster peer show -instance
Peer Cluster Name: cluster2
Remote Intercluster Addresses: 192.168.1.51
Availability of the Remote Cluster: Available
Remote Cluster Name: cluster2
Active IP Addresses: 192.168.1.51

Configure SVM Peer Relationships
Peer Relationships Between Storage Virtual Machines
Set up a peer relationship between SVMs:

cluster1::> vserver peer create -vserver svm1
-peer-vserver svm1_2 -peer-cluster cluster2
-applications snapmirror
Verify that the peer state is peered:

cluster1::> vserver peer show-all
The peer SVM must accept the peer request:

cluster2::> vserver peer accept -vserver svm1_2 -
peer-vserver svm1
CONFIGURE SVM PEER RELATIONSHIPS: PEER RELATIONSHIPS BETWEEN

STORAGE VIRTUAL MACHINES
Set up a peer relationship between the SVMs.
cluster1::> vserver peer create -vserver svm1 -peer-vserver svm1_2 -peer-cluster cluster2
-applications snapmirror
Peer Peer Peering
Vserver Vserver State Peer Cluster Applications
----------- ----------- ------------ -------------------------- ---------------
svm1 svm1_2 initiated cluster2 snapmirror
Check the state of the peering request from cluster2.

Peer Peer Peering
----------- ----------- ------------ -------------------------- ---------------
svm1_2 svm1 pending cluster1 snapmirror

The peer SVM must accept the peer request:
cluster2::> vserver peer accept -vserver svm1_2 -peer-vserver svm1
Verify that the peer state is initiated:
Peer Peer Peering
----------- ----------- ------------ -------------------------- ---------------
svm1 svm1_2 peered cluster2 snapmirror
Peer Peer Peering
----------- ----------- ------------ -------------------------- ---------------
svm1_2 svm1 peered cluster1 snapmirror

ACTION: Exercise

exercise
equipment.
Open your
credentials
provided Turn to Complete the
by your Exercise 1. specified tasks.
instructor.
Stop at the
end of Q&A
Exercise 1.
ACTION: EXERCISE

What network interface configurations

were required for intercluster data
protection?
Which peered relationship must be
configured first, cluster or SVM?
What tasks did you complete to prepare
the secondary storage environment?

BASED EXERCISE

References
NetApp University courses:

Clustered Data ONTAP Administration
NetApp OnCommand Unified Manager Administration
Community:
http://communities.netapp.com/community/products_and_solutions/
netapp_integrated_data_protection
REFERENCES

Module 2
Data Protection with NetApp Snapshot Copies
MODULE 2: DATA PROTECTION WITH NETAPP SNAPSHOT COPIES
2-1 Data ONTAP Data Protection Administration: Data Protection with NetApp Snapshot Copies

Module Objectives

Describe Data ONTAP Snapshot copy technology
Recover data from Snapshot copies
Manage Snapshot copies
Create and manage Snapshot copy policies
MODULE OBJECTIVES

Lesson 1
Data ONTAP Snapshot Copy
Technology
LESSON 1: DATA ONTAP SNAPSHOT COPY TECHNOLOGY

Snapshot Copy Technology Is Foundational
Snapshot SnapRestore SnapMirror SnapVault NDMP

copies (revert to point- (disaster (disk-to-disk (disk-to-tape
(local backups) in-time copy) recovery short-term long-term
failover that is archival) archival)
not limited by
distance)
Snapshot Copy Foundational Technology
SNAPSHOT COPY TECHNOLOGY IS FOUNDATIONAL

Snapshot copy technology is foundational to Data ONTAP data protection replication.
The Data ONTAP data protection technologies provide various types of data protection, and local Snapshot
copies are the foundation for MetroCluster, SnapMirror, SnapVault, and NDMP replication technologies.

The NetApp Data ONTAP Snapshot Copy
A Snapshot copy is a read-only, space-efficient, point-in-time

image of data in a volume or an 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.
Active File Snapshot

System Copy
File or LUN X File or LUN X
Disk
A B C
Blocks
THE NETAPP DATA ONTAP SNAPSHOT COPY

Snapshot copy technology is a key element of the Data ONTAP 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 an aggregate.
Snapshot copies are used for backup and error recovery.
To create a Snapshot copy of a volume or an aggregate, Data ONTAP copies the inode map file. This text file
lists all of the file names and block locations for each file in the volume or aggregate. The data blocks are not
copied.
A Snapshot copy is only a picture of the file system, and it does not contain any data file content. When
Data ONTAP begins a Snapshot copy, the blocks in the file system that have data written in them are locked
so that data that is preserved in a Snapshot copy cannot be overwritten. You can use the SnapRestore feature
to revert back to the file system as it was preserved in the Snapshot copy.

Ken Asks
What do I need to know to

design a Snapshot solution
for my company?
KEN ASKS

Snapshot Copy Design Guidelines
Understand that a Snapshot copy is a local image of a

volume that is created to retrieve accidentally deleted data.
If the primary volume becomes unavailable, the Snapshot
copy also becomes unavailable.
To control storage consumption, create only as many
Snapshot copies as are necessary, and configure Snapshot
copy automatic deletion and volume automatic increase.
Check and adjust the aggregate and volume Snapshot copy
reserve defaults.
NOTE: 32-bit Snapshot copies are not supported in Data ONTAP 8.3.
SNAPSHOT COPY DESIGN GUIDELINES

Snapshot copies are the first line of defense against accidental data loss or inconsistency. Before you
implement a Snapshot copy solution, you should thoroughly understand the customers needs and
environment. Also, remember that a Snapshot copy is a local image that has not yet been transferred to a
remote storage location. If the primary volume becomes unavailable because of disk failure, controller failure,
or network failure, the Snapshot copies of that volume also become unavailable.
To provide efficient use of disk space, deploy only the required number of Snapshot copies on each volume.
If you deploy more Snapshot copies than are required, the copies consume more disk space than necessary.
You can also configure a policy to automatically delete Snapshot copies under specified conditions. If you
have also deployed SnapMirror or SnapVault, you should be mindful that your automatic deletion policy does
not delete needed SnapMirror or SnapVault Snapshot copies.
Another way to use disk space efficiently is to check and adjust the default settings for Snapshot copy reserve
for volumes and aggregates. Snapshot copy reserve guarantees that you can create Snapshot copies until that
space is filled. When Snapshot copies fill the reserved space, Snapshot blocks compete for space with the
active file system.
NOTE that 32-bit Snapshot copies are not supported on Data ONTAP 8.3; therefore, if you are upgrading to
Data ONTAP 8.3, you must delete all of your 32-bit Snapshot copies.

Maximum Number of Snapshot Copies
The Number of Snapshot Copies per Volume Can Vary
The maximum number of Snapshot copies per FlexVol

volume is 255.
If the FlexVol volume is in a data protection mirror
relationship, the maximum number of Snapshot copies is 254.
If the FlexVol volume is in a disk-to-disk backup relationship,
the maximum number of Snapshot copies is 251.
MAXIMUM NUMBER OF SNAPSHOT COPIES: THE NUMBER OF SNAPSHOT COPIES

PER VOLUME CAN VARY
It is important to know how many Snapshot copies you can accumulate. If you monitor the number of
Snapshot copies in a volume, you can prevent Snapshot copy failure due to volume limitations.
Remember the following conditions about the maximum number of Snapshot copies:
You can accumulate a maximum of 255 Snapshot copies per FlexVol volume.
If the FlexVol volume is in a data protection mirror relationship, the maximum number of Snapshot
copies is 254 because one Snapshot copy is reserved for use by the relationship during recovery
operations.
If the FlexVol volume is in a disk-to-disk backup relationshipfor example, a SnapVault relationship of
a mirror SnapVault cascadethe maximum number of Snapshot copies is 251.

Manage Snapshot Copies
Snapshot Copy Management Commands
cluster1::> volume snapshot ?
autodelete> Manage snapshot autodelete settings

modify Modify autodelete settings
show Display autodelete settings
create Create a snapshot
delete Delete a snapshot
modify Modify snapshot attributes
partial-restore-file Restore part of a file from a snapshot
policy> Manage snapshot policies
rename Rename a snapshot
restore-file Restore a file from a snapshot
show Display a list of Snapshot copies
MANAGE SNAPSHOT COPIES: SNAPSHOT COPY MANAGEMENT COMMANDS

The volume snapshot command directory contains commands for managing Snapshot copies. The
commands that you might use most often include the show, modify, rename, and autodelete
commands.

Obtain Information About Snapshot Copies
Obtain general information about all Snapshot copies:

cluster1::> volume snapshot show
Obtain granular information about a particular Snapshot

copy:
-volume svm1_vol1 -snapshot hourly.2014-10-01_0605
-instance
Displays detailed information about all fields
OBTAIN INFORMATION ABOUT SNAPSHOT COPIES

The volume snapshot show command displays information about Snapshot copies. The command
output depends on the parameters that are specified with the command. If no parameters are specified, you
can obtain verbose information by adding the instance parameter. The instance parameter with the
volume snapshot show command displays a table that includes the verbose information about all the
available Snapshot copies, for example:
Storage virtual machine (SVM) name
Volume name
Snapshot copy name
Creation time
Size
And many other fields of information

Manually Create a Snapshot Copy
Manually create a Snapshot copy:

cluster1::> volume snapshot create -vserver svm1
-volume svm1_vol1 -snapshot MySnapshot1
-comment Manually created Snapshot Copy
Obtain size and space utilization information:

Obtain verbose information about the Snapshot copy:

-instance
MANUALLY CREATE A SNAPSHOT COPY

The volume snapshot create command creates a Snapshot copy of a specified volume.
cluster1::> volume snapshot create
Usage:
[ -vserver <vserver name> ] Vserver (default: svm1)
[-volume] <volume name> Volume
[-snapshot] <snapshot name> Snapshot
[[-comment] <text (size 0..255)>] Comment
[ -foreground {true|false} ] Foreground Process (default: true)
[ -snapmirror-label <text (size 0..31)> ] Label for SnapMirror Operations
Example:
cluster1::> volume snapshot create -vserver svm1 -volume svm1_vol1 -snapshot
MySnapshot1 -comment "Manually created Snapshot Copy"
cluster1::> volume snapshot show -volume svm1_vol1

Modify a Snapshot Copy
Modify an existing Snapshot copy comment or SnapMirror

label:
cluster1::> volume snapshot modify vserver svm1
volume svm1_vol1 -snapshot MySnapshot1 comment
This is a new comment
Rename the Snapshot copy:

cluster1::> volume snapshot rename -vserver svm1
-new-name MySnapshot_Renamed
MODIFY A SNAPSHOT COPY

The volume snapshot modify command enables you to change the text comment that is associated
with a Snapshot copy.
cluster1::> volume snapshot modify
Usage:
[ -vserver <vserver name> ] Vserver (default: svm1)
[-volume] <volume name> Volume
[-snapshot] <snapshot name> Snapshot
[ -comment <text (size 0..255)> ] Comment
[ -snapmirror-label <text (size 0..31)> ] Label for SnapMirror Operations
Examples:
cluster1::> volume snapshot modify vserver svm1 -volume svm1_vol1
comment This is a new comment
cluster1::> volume snapshot rename -vserver svm1 -volume svm1_vol1 -
snapshot MySnapshot1 -new-name MySnapshot_Renamed
cluster1::> volume snapshot show -vserver svm1 -volume svm1_vol1

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll has two quick questions about Snapshot technology. When the instructor begins the polling session,
you see the polling questions that you are to answer. After all answers are submitted, the instructor closes the
poll.
After the polling session ends, the instructor briefly answers the questions for you.

Poll Questions
1. Which two statements are true about Snapshot copy

technology? (Choose two.)
a. A Snapshot copy can be used to recover from a shelf failure.
b. A Snapshot copy requires the same amount of space as the volume.
c. A Snapshot copy is a copy of the inode map file.
d. A Snapshot copy is a read-only image of a volume or an aggregate.
2. What command displays Snapshot size and space

utilization for a specific volume?
a. volume snapshot create -vserver svm1
b. volume snapshot modify vserver svm1
c. volume snapshot show
d. volume snapshot show -volume vol1

Lesson 2
Restoring Data from Snapshot
Copies
LESSON 2: RESTORING DATA FROM SNAPSHOT COPIES

The SnapRestore Feature
SnapRestore software reverts aggregates, volumes,

LUNs, or files back to a point in time when the Snapshot
copy was created.
Active File
System
File or LUN X
Disk
Blocks A B C
THE SNAPRESTORE FEATURE

To restore aggregates, volumes, LUNs, or files from Snapshot copies, use the SnapRestore feature.
SnapRestore software is the foundational technology for reverting a volume back to a point-in-time Snapshot
copy.

Considerations Before Restoring Data
SnapRestore
Privilege
license
requirements
requirement
Volume I/O
activity
SnapMirror
relationships Use of an entire
volume, entire file,
or partial file
Use of the root

volume
CONSIDERATIONS BEFORE RESTORING DATA

For smooth restore operations, consider the following factors before you decide to restore data from a
Snapshot copy:
SnapRestore license requirement: A SnapRestore license is required to be able to perform the Snapshot
copy restore operation.
Privilege requirements: You must have the advanced privilege level or higher to restore the contents of
a volume from a Snapshot copy. Snapshot files carry the same permissions as the original files, which
keeps the integrity of the security system intact.
Volume I/O activity: To restore the contents of a volume from a Snapshot copy, there must be no I/O
activity on the volume.
Use of an entire volume, entire file, or partial file: You can restore the entire volume from a Snapshot
copy, restore an entire file, or restore part of a file.
Use of the root volume: If you are required to restore the root volume from a Snapshot copy, the node is
rebooted. Nonroot volumes do not require a reboot.
SnapMirror relationships: You should manually update all the SnapMirror relationships of a volume
immediately after you restore its Snapshot copy. If you do not do so, the result might be unusable
SnapMirror relationships that must be deleted and re-created.

Volume Snapshot Restore Workflow
The steps for performing a volume Snapshot copy restore

include:
Review the existing Snapshot copies in the volume and
carefully select the Snapshot copy to restore.
Notify users that data might be lost with snapshot restore.
Run the volume snapshot restore command.
Review your results.
If you have implemented SnapMirror relationships, you must
manually update the SnapMirror relationships of a
volume immediately after you restore its Snapshot copy.
VOLUME SNAPSHOT RESTORE WORKFLOW

Follow these steps to restore a volume with the volume snapshot restore command.
1. Review the existing Snapshot copies in the volume and decide which Snapshot copy is best to revert to.
2. Run the volume snapshot restore command.
3. If you have implemented any SnapMirror or SnapVault relationships, you must manually update the
relationships of a volume immediately after you restore its Snapshot copy. Not doing so can result in
unusable SnapMirror relationships that must be deleted and re-created.

Restore Data with Data ONTAP Commands
To restore data from Snapshot copies, use these Data

ONTAP commands:
volume snapshot restore
volume snapshot restore-file
The volume snapshot restore command restores a

Snapshot copy to be the read/write parent volume.
The volume snapshot restore-file command enables
you to restore a single file to a version saved in a Snapshot copy.
RESTORE DATA WITH DATA ONTAP COMMANDS

The volume snapshot restore command restores a Snapshot copy to be the read/write parent
volume. This volume replaces the current working copy of the volume with the Snapshot copy and results in a
loss of all changes made since the Snapshot copy was created.
The volume snapshot restore-file command enables you to restore a single file to a version that
is saved in the Snapshot copy. You can restore a file over an existing copy of the file in the parent read/write
volume or to a different location within the same parent read/write volume. If the destination file for the
restore operation does not exist, a new file is created with the same version as the one saved in the Snapshot
copy. If the destination file for the restore operation exists, then it is overwritten by the version from the
Snapshot copy. This operation is used to restore normal user-level files and LUNs. The command fails if you
try to restore directories (and their contents) and files with NT streams. During the restore operation, the
parent read/write volume should remain online. The command fails if the destination path for the restore
operation is in a different volume than the source volume.

Performing a Volume SnapRestore Operation
Review the existing Snapshot copies in the volume:

cluster1::> volume snapshot show -vserver svm1
-volume svm1_vol1
Run the snapshot restore command for the desired

Snapshot copy:
cluster1::> volume snapshot restore -vserver svm1
-volume svm1_vol1 snapshot hourly.2014-10-07_0205
PERFORMING A VOLUME SNAPRESTORE OPERATION

In the example, the volume snapshot show command displays eight Snapshot copies. After reviewing
the date stamp on each of the Snapshot copies, you select the one that is best.
Next, you run the snapshot restore command and respond to the prompts.
cluster1::> volume snapshot restore -vserver svm1 -volume svm1_vol1 -snapshot
hourly.2014-10-07_0205
Warning: Snapshot copy "hourly.2014-10-07_0205" is not the most recent copy.
Promoting this Snapshot copy will delete all copies made after it.
Do you want to continue? {y|n}: y
Warning: Quota rules currently enforced on volume svm1_vol1 may change during
this operation. If the currently enforced quota rules are different
from those in Snapshot copy hourly.2014-10-07_0205, you may have to
resize or reinitialize quotas on this volume after this operation.
Warning: Export policies currently enforced on the qtrees of volume "svm1_vol1"
will not change during this operation. If the currently enforced
export policies are different from those in Snapshot copy
"hourly.2014-10-07_0205", reassign the export policies of the qtrees
on this volume after this operation.

Verifying a Volume SnapRestore Operation
Check the Snapshot copies on the volume:

-vserver svm1 -volume svm1_vol1
Snapshot copies newer than the restored Snapshot copy

have been removed.
VERIFYING A VOLUME SNAPRESTORE OPERATION

Enter the volume snapshot show command to see the remaining list of Snapshot copies for the volume.
Notice that Snapshot copies that are newer than the restored Snapshot copy have been removed. Your volume
has returned to a point in time when the newer Snapshot copies, and new data for that matter, did not exist.

Single File SnapRestore
Check the volume Snapshot copies:

Restore the file (MyFile.txt) from a Snapshot copy:

cluster1::> volume snapshot restore-file
-snapshot 2HourSnapshot.2014-09-22_1405
-path /vol/svm1_vol2/MyFile.txt
SINGLE FILE SNAPRESTORE

You begin the restore file workflow by examining the existing Snapshot copies with the volume
snapshot show command.
Run the volume snapshot restore-file command and specify the Snapshot copy that you want to
restore the file from.
cluster1::> volume snapshot restore-file -vserver svm1 -volume svm1_vol2
-snapshot ManualSnapshot2 -path /vol/svm1_vol2/MyFile.txt
Because you restored a single file, all the Snapshot copies and all of the data written since the most recent
Snapshot copy was created still exist on the volume.

Using Copy and Paste to Restore Data
Recovering Data from the Clients Computer
Clients can be enabled to access the Snapshot copy

directories on each volume or on any volume.
Make the Snapshot copy directories visible to NFS and CIFS
clients:
cluster1::> volume modify -volume svm1_vol1
-snapdir-access true
Volume modify successful on volume svm1_vol1 of
Vserver svm1.
Copy the files in the Snapshot copy directories back to the

local file systems with copy and paste.
USING COPY AND PASTE TO RESTORE DATA: RECOVERING DATA FROM THE
CLIENTS COMPUTER
Customers can use native client tools to access the Snapshot directories on each volume or any volume. The
CIFS or NFS client must have access to the root directory of the volume. In Data ONTAP, for CIFS clients,
you must modify the settings of CIFS shares to make Snapshot copies visible. For CIFS clients, Snapshot
copies are not visible by default. In Data ONTAP for NFS clients, Snapshot copies are visible by default.
After you configure the Snapshot copy directories to be visible to both CIFS and NFS clients, clients can see
the Snapshot directories on the volume and use the copy and paste tools to recover data from Snapshot copies.

Restoring Previous Versions
Use Snapshot Copies to Restore Previous Versions from the Windows Client
Right-click any file that

is stored on a Data
ONTAP SVM.
Select Restore
previous versions.
RESTORING PREVIOUS VERSIONS: USE SNAPSHOT COPIES TO RESTORE

PREVIOUS VERSIONS FROM THE WINDOWS CLIENT
Another way to recover data is with Windows Restore previous versions. On the Windows client, select any
file that is stored on a Data ONTAP SVM, right-click that file, and select Restore previous versions. The
previous versions are offered by the Snapshot copies of that shared volume.

Restore a File to a Previous Version
Data ONTAP Snapshot Copies Provide Previous Versions
Select one of the

previous versions.
You can Open, Copy, or

Restore the version.
RESTORE A FILE TO A PREVIOUS VERSION: DATA ONTAP SNAPSHOT COPIES

PROVIDE PREVIOUS VERSIONS
In the Windows Previous Versions tab, you see choices to open, copy, or restore any previous version of the
file. You can select a version and open, copy, or restore the file. If no previous versions are listed, the file has
not changed.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

Poll Questions
1. How can you use a Snapshot copy to recover data?

(Choose three.)
a. by promoting a Snapshot copy to be the active file system
b. by using SnapRestore to revert a file or volume to a point in time
c. by copying a file from the Snapshot directory to the active file system
d. by undoing a reversion and choosing a more recent Snapshot copy
2. Before you recover data from a Snapshot copy, which

factors should you consider? (Choose all that apply.)
a. Install the SnapRestore license, meet privilege requirements, and update
SnapMirror relationships.
b. Ensure that there is no I/O activity.
c. If the root volume being restored, prepare users for a node reboot.
d. Decide whether to restore entire volume, entire file, or partial file.

ACTION: Exercise

exercise
equipment.
Open your
credentials
instructor.
Stop after
Task 3. Q&A
ACTION: EXERCISE

Topic for Discussion
If a user tries to recover a file in a

Snapshot copy that the user has no
permissions for, what happens?
TOPIC FOR DISCUSSION

Lesson 3
Managing Snapshot Copies
LESSON 3: MANAGING SNAPSHOT COPIES

Snapshot Copy Management Tasks
To manage Snapshot copies, perform the following types

of tasks:
Monitor storage space allocated to Snapshot copies
over time.
To recover storage space, delete Snapshot copies.
Manage busy Snapshot copies.
Create an automatic Snapshot copy deletion policy for
volumes with a high rate of change.
SNAPSHOT COPY MANAGEMENT TASKS

In this section of the module, you learn the basics of managing Snapshot copies:
You learn how to manage busy Snapshot copies.
You can create an automatic Snapshot copy delete policy; however, you should know about the option to
preserve SnapVault Snapshot copies.
Although the overall plan for managing Snapshot copies is to use Snapshot copy policies, the tips in this
section should help you.

Guidelines for Snapshot Copy Disk Space
Know how much disk space is consumed by all Snapshot

copies and each Snapshot copy.
Predict Snapshot copy disk space consumption.
Delete Snapshot copies automatically.
Find out how much disk space is recovered if a Snapshot
copy is deleted.
GUIDELINES FOR SNAPSHOT COPY DISK SPACE

Although Snapshot copies consume almost no disk space when they are first created, there is still a need to
manage the storage space that is consumed by Snapshot copies. Over time, as Snapshot copies continue to
protect data that has changed, Snapshot copies consume an increasing amount of storage space.
If the rate of change of a volume is high, Snapshot copies might need to be manually deleted. The next slides
show you how to determine how much space is being consumed by a Snapshot copy, how to delete a
Snapshot copy, and how to implement automatic Snapshot copy deletion.

Managing Snapshot Copy Disk Space
Snapshot Copy Disk Space Consumption
Monitor the Snapshot copy disk space consumption:

Find out how much Snapshot copy space is being used:

cluster1::> volume show -vserver svm1 -volume
svm1_vol2 -fields snapshot-space-used
MANAGING SNAPSHOT COPY DISK SPACE: SNAPSHOT COPY DISK SPACE

CONSUMPTION
The design of the Snapshot copy feature prevents the data that is referenced by a Snapshot copy from being
deleted accidentally. Therefore, as the active file system changes, files protected by a Snapshot copy are
owned by the Snapshot copy and consume storage space that is owned by the Snapshot copy.
You can monitor Snapshot copy storage consumption by using the volume show command, which displays
the amount of free space on a disk.
You can also find out how much Snapshot copy space is being used.
cluster1::> volume show -vserver svm1 -volume svm1_vol2 -fields snapshot-

space-used

Snapshot Copy Disk Space Management
Find out the amount of disk space can be reclaimed by

deleting a specific Snapshot copy:
cluster1::> volume snapshot compute-reclaimable

-snapshots hourly.2014-10-13_1405
A total of 77824 bytes can be reclaimed.
SNAPSHOT COPY DISK SPACE MANAGEMENT

If a volume is running low on available space, you can use the volume snapshot computer-
reclaimable command to determine which Snapshot copies are consuming the most space and can be
deleted. Use this command to check the oldest Snapshot copies first.

Deleting Snapshot Copies
Manually delete a Snapshot copy:

cluster1::> volume snapshot delete -vserver svm1
-volume svm1_vol1 -snapshot MySnapshot_Renamed
Warning: Deleting a Snapshot copy permanently
removes any data that is stored only in that
Snapshot copy. Are you sure you want to delete
Snapshot copy "MySnapshot_Renamed" for volume
"svm1_vol1" in Vserver "svm1" ?
{y|n}: y
Delete all Snapshot copies in a volume:

cluster1::> volume snapshot delete -vserver svm1
-volume svm1_vol1 -snapshot *
DELETING SNAPSHOT COPIES

If you locate a Snapshot copy that is not needed but is consuming a significant amount of space, you can
manually delete the Snapshot copy with the volume snapshot delete command.
The examples show how to delete a specific Snapshot copy or all of the Snapshot copies in a volume. If you
have SnapMirror and SnapVault Snapshot copies, do not delete all Snapshot copies.

Managing Busy Snapshot Copies
Finding Busy Snapshot Copies
If there are any applications that are based on a Snapshot

copy, then that Snapshot copy is in a busy state and cannot
be deleted. (Example: a FlexClone clone of a volume.)
Create a FlexClone of a volume:
cluster1::> volume clone create -vserver svm1
-flexclone svm1_vol1_Clone -type RW
-parent-volume svm1_vol1
Check to see any busy Snapshot copies appear in the

volume:
cluster1::> volume snapshot show -vserver svm1 volume
svm1_vol1 -busy true
MANAGING BUSY SNAPSHOT COPIES: FINDING BUSY SNAPSHOT COPIES

If a Snapshot copy is locked by a FlexClone volume clone, for example, that Snapshot copy is marked as
busy, and busy Snapshot copies cannot be deleted.
To see what a busy Snapshot copy looks like, create a FlexClone clone of a volume.
cluster1::> volume clone create -vserver svm1 -flexclone svm1_vol1_Clone
-type RW -parent-volume svm1_vol1
Use the busy true command option to see if there are any busy Snapshot copies in the volume.
cluster1::> volume snapshot show -vserver svm1 -volume svm1_vol1 -busy
true
The output of the busy true command option shows only the busy Snapshot copies.

Managing Busy Snapshot Copies
Finding the Owner of a Busy Snapshot Copy
Check the owner of a busy Snapshot copy:

cluster1::> volume snapshot show -vserver svm1
-volume svm1_vol1 -fields owners
vserver volume snapshot owners
------- --------- ---------------------- ------
svm1 svm1_vol1 clone_svm1_vol1_clone.0 "volume
clone"
MANAGING BUSY SNAPSHOT COPIES: FINDING THE OWNER OF A BUSY

SNAPSHOT COPY
If you have a busy Snapshot copy, you need to determine the owner so that you know which FlexClone
volume clone or other function is locking the Snapshot copy as busy. To determine the owner of the busy
Snapshot copy, use the volume snapshot show command.
For example:
cluster1::> volume snapshot show -vserver svm1 -volume svm1_vol1 -fields
owners
vserver volume snapshot owners
------- --------- ---------------------- ------
svm1 svm1_vol1 clone_svm1_vol1_clone.0 "volume clone"
After you determine the owner of the Snapshot copy, you can determine whether you can stop the application
that is holding the Snapshot copy busy. For example, you might be able to delete the FlexClone volume clone.
After you can delete the clone, the Snapshot copy is no longer busy and can be deleted.

The Snapshot Copy autodelete Command
Define a Policy for Automatically Deleting Snapshot Copies
snap autodelete vol_name on option value
Options Option Functions
commitment Specifies whether Snapshot copies that are locked by data

protection utilities can be deleted. To protect SnapMirror or
SnapVault Snapshot copies, set this option to try.
trigger Specifies when to begin automatically deleting Snapshot
copies (volume size or space reserve threshold)
target_free_space Determines when to stop deleting Snapshot copies
defer_delete Deletes the specified type of Snapshot copies last
prefix Used with the defer_delete option; deletes Snapshot

copies with a specific prefix last
THE SNAPSHOT COPY AUTODELETE COMMAND: DEFINE A POLICY FOR

AUTOMATICALLY DELETING SNAPSHOT COPIES
You can better manage space usage if you automatically delete Snapshot copies.
You can define and enable a policy for automatically deleting Snapshot copies by using the snap autodelete
command.
You use the snap autodelete command with several options to define your Snapshot copy autodelete
policy.
The following guidelines apply:
You can modify a policy to automatically delete Snapshot copies by using the volume snapshot
autodelete modify command.
If you enable automatic Snapshot copy deletion and you have also implemented SnapMirror or
SnapVault, use the commitment option with the try value to protect needed SnapMirror or
SnapVault Snapshot copies from being automatically deleted.

Monitoring and Managing Automatic Deletion
Snapshot Copy Automatic Deletion
View the volume automatic deletion policy settings that are

currently in effect:
cluster1::> volume snapshot autodelete show
Enable the automatic deletion of Snapshot copies and set the

trigger to volume for the svm1_vol2 volume, which is
affiliated with the svm1 SVM:
cluster1::> volume snapshot autodelete modify
vserver svm1 -volume svm1_vol2 -enabled true
-trigger volume
NOTE: For SAN solutions, see the Clustered Data ONTAP 8.3 SAN Administration Guide.
MONITORING AND MANAGING AUTOMATIC DELETION: SNAPSHOT COPY

AUTOMATIC DELETION
View the volume autodelete policy settings that are currently in effect.
cluster1::> volume snapshot autodelete show -vserver svm1 -volume
svm1_vol2
Vserver Name: svm1
Volume Name: svm1_vol2
Enabled: false The autodelete policy is not turned on.
Commitment: try
Defer Delete: user_created
Delete Order: oldest_first
Defer Delete Prefix: (not specified)
Target Free Space: 20%
Trigger: volume
Destroy List: none
Is Constituent Volume: false
This policy triggers when the free space in the volume falls below 20%.
Modify the Snapshot automatic deletion options with the volume snapshot autodelete modify
command.
cluster1::> volume snapshot autodelete modify ?

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll has two questions about managing Snapshot copies. When the instructor begins the polling session,
you see the polling questions that you are to answer. After all answers are submitted, the instructor closes the
poll.

Poll Questions
1. Which three tasks might you perform regularly to manage

Snapshot copies? (Choose three.)
a. Monitor Snapshot copy space consumption
b. Configure automatic Snapshot copy deletion policies for volumes
c. Manually delete Snapshot copies that have exceeded the retention
period
d. Create manual Snapshot copies hourly to protect data
e. Manually delete Snapshot copies that were created manually to preserve
disk space
2. True or False: If you notice a busy Snapshot copy, you can

delete the busy Snapshot copy in one simple step.
a. True
b. False

Lesson 4
Creating Snapshot Copy
Policies
LESSON 4: CREATING SNAPSHOT COPY POLICIES

The Snapshot Copy Policy
Automatically Manage Snapshot Copy Schedules and Retention Rules
Snapshot
Job
Copy Policy SnapMirror
Schedule
Label
daily
To specify the number To specify frequency, If the SnapMirror Label

of Snapshot copies to assign one or more parameter is specified,
retain, use a Snapshot job schedules. it is used in with
copy policy. SnapMirror policies.
You can use the default Snapshot copy policy or create

Snapshot copy policies with job schedules when necessary.
THE SNAPSHOT COPY POLICY: AUTOMATICALLY MANAGE SNAPSHOT COPY

SCHEDULES AND RETENTION RULES
Use Snapshot copy policies to automate Snapshot copies. A Snapshot copy policy enables you to specify the
frequency and maximum number of Snapshot copies that are created automatically.
You can use the default Snapshot copy policies or create customized Snapshot copy polices as necessary.
You can use default job schedules or create customized job schedules as necessary.
You can apply one or more job schedules to a Snapshot copy policy.
The Snapshot copy policy can also have no schedules.
The SnapMirror label is discussed in the SnapVault module.

Assigning Snapshot Copy Policies
Assign a Snapshot Copy Policy to the Cluster, SVM, or Volume
Snapshot Copy Policy

Job
SnapMirror
Schedule
Label
daily
cluster1 svm1 vol1
ASSIGNING SNAPSHOT COPY POLICIES: ASSIGN A SNAPSHOT COPY POLICY TO

THE CLUSTER, SVM, OR VOLUME
When you create an SVM, you can specify a Snapshot copy policy. That policy becomes the default for all
FlexVol volumes that are created for that SVM.
When you create a FlexVol volume, you can specify which Snapshot copy policy you want to use, or you can
allow the FlexVol volume to inherit the SVM Snapshot copy policy.

Default Snapshot Copy Policies
Three preconfigured Snapshot copy policies exist. These

policies are affiliated with the cluster.
Policy Name Schedule Count

Default Hourly 6
Daily 2
Weekly 2
Default-1 weekly Hourly 6
Daily 2
Weekly 1
None n/a n/a
DEFAULT SNAPSHOT COPY POLICIES

The three preconfigured Snapshot copy policies cover various schedules and Snapshot copy retention rules.
You can create customized job schedules and Snapshot copy policies to meet your requirements.

Creating a Snapshot Copy Policy Workflow
1. Create a Job Schedule
Data ONTAP job schedules are created at

the cluster level.
Job schedules can be applied to the cluster, Job
to an SVM, or to a volume. Schedule
You can apply one or more schedules to a

cluster, an SVM, or a volume.
You can use one of the default job
schedules or create schedules.
You cannot modify a default schedule.
CREATING A SNAPSHOT COPY POLICY WORKFLOW: 1. CREATE A JOB

SCHEDULE
A Snapshot copy policy automatically manages Snapshot copy schedules and retention on FlexVol volumes.
You can apply the Snapshot copy policy to the cluster or to an SVM.
To implement a Snapshot copy solution, first, decide on a job schedule.
Use a default or pre-existing schedule or create a schedule, as required.
You can use multiple schedules that create and delete Snapshot copies.

Creating a Snapshot Copy Policy Workflow
2. Create Snapshot Copy Policies
Snapshot copy policies manage retention on FlexVol volumes

automatically.
To manage the schedule automatically, assign a job schedule
to a Snapshot copy policy.
If SnapMirror is implemented, assign a SnapMirror label to a
Snapshot copy policy.
Snapshot
Job
Copy Policy SnapMirror
Schedule
Label
daily
CREATING A SNAPSHOT COPY POLICY WORKFLOW: 2. CREATE SNAPSHOT COPY

POLICIES
Next, you create the Snapshot copy policy and assign a schedule.
The volume snapshot policy command directory contains commands that you use to create and
manage Snapshot copy policies.
cluster1::> volume snapshot policy ?
add-schedule Add a schedule to snapshot policy
create Create a new snapshot policy
delete Delete a snapshot policy
modify Modify a snapshot policy
modify-schedule Modify a schedule within snapshot policy
remove-schedule Remove a schedule from snapshot policy
show Show snapshot policies

Managing Policies and Schedules
Cron job schedules are schedules that run at a specific time.

Display the list of schedules with the following command:
job schedule cron show
5min @:00,:05,:10,:15,:20,:25,:30,:35,:40,:45,:50,:55
8hour @2:15,10:15,18:15
Daily @0:10
Hourly @:05
Weekly Sun@0:15
Each Snapshot copy policy contains at least one schedule.
MANAGING POLICIES AND SCHEDULES

The job schedule cron command directory contains commands that you use to manage schedules that
can be used for Snapshot copy policies.
cluster1::> job schedule cron show
Name Description
---------------- ---------------------------------------------------
5min @:00,:05,:10,:15,:20,:25,:30,:35,:40,:45,:50,:55
8hour @2:15,10:15,18:15
daily @0:10
hourly @:05
weekly Sun@0:15

Create a Job Schedule
Check to see if an existing job schedule fits your needs:

cluster1::> job schedule show
Create a job schedule:

cluster1::> job schedule cron create -name
2HourSnapshot -month all -dayofweek all -day all
-hour 0,2,4,6,8,10,12,14,16,18,20,22 -minute 5
Verify that the job schedule was created:

CREATE A JOB SCHEDULE

Find out which job schedules exist. If a job schedule meets your needs, use it. If not, create a job schedule.
cluster1::> job schedule show
If you need to create a job schedule, run the job schedule cron create command:
cluster1::> job schedule cron create
Usage:
[-name] <text> Name
[ -month <cron_month>, ... ] Month
[ -dayofweek <cron_dayofweek>, ... ] Day of Week
[ -day <cron_dayofmonth>, ... ] Day
[ -hour <cron_hour>, ... ] Hour
[-minute] <cron_minute>, ... Minute
Example: Create a job that runs every month, every day of the week, every two hours, at five minutes past the
hour:
cluster1::> job schedule cron create -name 2HourSnapshot -month all -
dayofweek all -day all -hour 0,2,4,6,8,10,12,14,16,18,20,22 -minute 5
You can use the 2HourSnapshot job to create a Snapshot copy policy.

Create a Snapshot Copy Policy
View the current volume Snapshot copy policies:

cluster1::> volume snapshot policy show
Create a volume Snapshot copy policy:

cluster1::> volume snapshot policy create -vserver
svm1 -policy 2Hour_Policy -enabled true -comment
"Takes a Snapshot Copy Every 2 Hours" -schedule
2HourSnapshot -count 84
Keep 84 Snapshot copies.
Verify that the policy was created:
cluster1::> volume snapshot policy show -policy
2Hour_Policy
CREATE A SNAPSHOT COPY POLICY

View the current Snapshot copy policies with the command volume snapshot policy show.
Vserver: cluster1
In the following example, you create a volume Snapshot copy policy for SVM svm1 that uses the
2HourSnapshot job that you created in the previous step. You keep one week of Snapshot copies, for a total of
84 copies:
cluster1::> volume snapshot policy create -vserver svm1 -policy
2Hour_Policy -enabled true -comment "Takes a Snapshot Copy Every 2 Hours"
-schedule 2HourSnapshot -count 84
Use one of two commands to verify the new Snapshot copy policy:
cluster1::> volume snapshot policy show -policy 2Hour_Policy

Assign the Snapshot Copy Policy to an SVM
For an existing SVM, check to see which policy is already

assigned:
cluster1::> vserver show -vserver svm1
Modify an SVM to use an existing Snapshot copy policy:

cluster1::> vserver modify -vserver svm1
-snapshot-policy 2Hour_Policy
Verify that the SVM configuration is using a new Snapshot

copy policy:
ASSIGN THE SNAPSHOT COPY POLICY TO AN SVM

Assign the new Snapshot copy policy to the SVM so that all of the volumes in the SVM inherit the new
Snapshot copy policy.
First, view the current Snapshot copy policy for SVM svm1 and notice that svm1 has been assigned the
default Snapshot copy policy.
Vserver: svm1
Vserver Type: data
Vserver Subtype: default
. . .
Snapshot Policy: default The current Snapshot copy policy
Change the current Snapshot copy policy so that the SVM uses the new
Snapshot policy:
cluster1::> vserver modify -vserver svm1 -snapshot-policy 2Hour_Policy
Use the vserver show -vserver svm1 command to verify that the new Snapshot copy policy has been
assigned.
Vserver: svm1
Snapshot Policy: 2Hour_Policy New Snapshot copy policy

Volumes Inherit the Snapshot Copy Policy
Create a FlexVol volume that inherits the Snapshot copy

policy from the SVM:
cluster1::> volume create -vserver svm1 -volume
svm1_vol2 -aggregate n1_aggr1 -size 200M
[Job 79] Job succeeded: Successful
Verify that the Snapshot copy policy exists:
cluster1::> volume show -vserver svm1 -volume
svm1_vol2 -fields Snapshot-Policy
vserver volume snapshot-policy The policy is
inherited from the
------- --------- --------------- SVM.
svm1 svm1_vol2 2Hour_Policy
VOLUMES INHERIT THE SNAPSHOT COPY POLICY

New volumes inherit the Snapshot copy policy that is assigned to the SVM.
Create a FlexVol volume without specifying the Snapshot copy policy. The new volume inherits the Snapshot
copy policy from the current setting on the SVM. Here is an example of the command to create a FlexVol
volume without assigning a Snapshot copy policy:
cluster1::> volume create -vserver svm1 -volume svm1_vol2 -aggregate
n1_aggr1 -size 20M
Confirm the Snapshot copy policy on the new volume:
cluster1::> volume show -vserver svm1 -volume svm1_vol2 -fields Snapshot-
Policy
vserver volume snapshot-policy
------- -------------- ---------------
svm1 svm1_vol2 2Hour_Policy

ACTION: Exercise

exercise
equipment.
Open your
credentials
instructor.
Stop at the
end of Q&A
Exercise 2.
ACTION: EXERCISE

Why did you create the job schedule

before the Snapshot copy policy?
What part of the Snapshot copy policy
works with SnapVault?

BASED EXERCISE

What Ken Has Learned in This Module
I learned how to design and deploy

an effective Snapshot copy solution.
I can now manage my Snapshot
copies effectively. I feel confident in
restoring data from Snapshot copies,
and I understand how to give my
users access to recover their own
data from Snapshot copies.
WHAT KEN HAS LEARNED IN THIS MODULE

References
NetApp University course:

NetApp documentation
Clustered Data ONTAP 8.3 Data Protection Guide
Clustered Data ONTAP 8.3 Data Protection Tape Guide
REFERENCES

Module 3
Synchronous Data Protection
MODULE 3: SYNCHRONOUS DATA PROTECTION
3-1 Data ONTAP Data Protection Administration: Synchronous Data Protection

Module Objectives

Explain how the Data ONTAP SyncMirror feature works
Explain how to set up and manage the SyncMirror feature
Explain MetroCluster architecture and components
Recall MetroCluster high-availability (HA) capabilities
Recall SyncMirror and MetroCluster deployment options and
use cases
MODULE OBJECTIVES

Lesson 1
Using the SyncMirror Feature
for Data Protection
LESSON 1: USING THE SYNCMIRROR FEATURE FOR DATA PROTECTION

Overview of the SyncMirror Feature
The SyncMirror feature provides synchronous data protection.
OVERVIEW OF THE SYNCMIRROR FEATURE

The SyncMirror feature is an optional feature of Data ONTAP that enables real-time mirroring of data within
a single aggregate. The SyncMirror feature provides for synchronous mirroring of data, implemented at the
RAID level. You can use the SyncMirror feature to create aggregates that consist of two copies of the same
WAFL (Write Anywhere File Layout) file system. The two copies, known as plexes, are simultaneously
updated. Therefore, the copies are always identical. The two plexes exist within a single aggregate.
Use the SyncMirror feature to provide increased data resiliency. The SyncMirror feature removes single
points of failure in connecting to disks or array LUNs. Application servers that are stored on Data ONTAP
with the SyncMirror feature can prevent data loss due to disk, shelf, or controller failures.
With the SyncMirror feature, you can configure two physically separated sites, such as a Site A and a Site B.
Data written to an aggregate in Site A is synchronously replicated in a set of disks that are on the remote Site
B.

SyncMirror Guidelines
Remember these guidelines about the SyncMirror feature:

The SyncMirror feature can be used to mirror aggregates.
A SyncMirror aggregate has two plexes.
This setup provides a high level of data availability because the
two plexes are physically separated.
The SyncMirror feature cannot be used to mirror FlexVol
volumes.
FlexVol volumes can be mirrored as part of an aggregate.
You cannot set up the SyncMirror feature with disks in one plex
and array LUNs in the other plex.
SYNCMIRROR GUIDELINES
A SyncMirror aggregate has two physically separated plexes, plex0 and plex1. For a system that uses disks,
the two plexes are on different shelves connected to the system with separate cables and adapters. Each plex
has its own collection of spare disks. For a system that uses array LUNs, the plexes are on separate sets of
array LUNs, either on one storage array or on separate storage arrays.
You cannot set up the SyncMirror feature with disks in one plex and array LUNs in the other plex.
Physical separation of the plexes protects against data loss if one of the shelves or the storage array becomes
unavailable. The unaffected plex continues to serve data while you fix the cause of the failure. After it is
fixed, the two plexes can be resynchronized.
Rebuild time with SyncMirror plexes is faster than recovering from other disk or tape secondary volumes.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick quiz on data protection using the SyncMirror feature.

Poll Questions
1. Which three statements about the SyncMirror feature are

true? (Choose three.)
a. SyncMirror provides synchronous mirroring at the RAID level.
b. SyncMirror creates and maintains two identical copies of a WAFL file
system within a single aggregate.
c. The two copies, known as plexes, are updated every 10 minutes.
d. Plexes contain disks from different shelves that are connected to the
system with separate adapters.
e. You can configure SyncMirror with disks that are located on the same
shelf.
2. True or False: You can use SyncMirror to mirror a single

volume within an aggregate without mirroring the aggregate.
a. True
b. False

Lesson 2
MetroCluster Architecture,
Components, and Capabilities
LESSON 2: METROCLUSTER ARCHITECTURE, COMPONENTS, AND CAPABILITIES

MetroCluster for Clustered Data ONTAP 8.3.0
MetroCluster Configuration Provides Continuous Availability
Active-active mirroring solution

Near zero data loss or application
downtime
Set-it-once simplicity
Near zero change management Up to 200 km
Seamless integration with storage MetroCluster

efficiency, data protection,
nondisruptive operations (NDO),
and non-FAS storage
Unified architecture: supports SAN Multiple Recovery Points
with Snapshot Copies
and NAS
METROCLUSTER FOR CLUSTERED DATA ONTAP 8.3.0: METROCLUSTER

CONFIGURATION PROVIDES CONTINUOUS AVAILABILITY
MetroCluster mirroring technology, which is built into the Data ONTAP operating system, provides
continuous data availability through a single MetroCluster command that activates a secondary on the
survivor site. MetroCluster technology provides total data protection:
Near zero data loss, planned, and unplanned downtime: You seldom lose a transaction, whether
caused by an IT event or by an external event, such as a hurricane, flood, or loss of communications.
Set-it-once simplicity: MetroCluster technology does not require external devices or host-based
configuration.
Near zero change management: After the MetroCluster configuration is set up, all changes on one side
are automatically replicated on the other side.
Seamless integration with storage efficiency, back up (SnapVault software), data recovery (SnapMirror
software), and nondisruptive operations (NDO), and non-FAS storage (via FlexArray storage
virtualization software): The protection technologies are all built into the Data ONTAP operating system.
Hypervisor integration: MetroCluster software is integrated with VMware vSphere Metro Storage
Cluster, Oracle RAC, SAP, and others, with certified configurations with VMware, SAP, and Cisco.
Unified architecture: MetroCluster technology supports SAN and NAS topologies simultaneously; most
competitive solutions support only SAN protocols.

MetroCluster Range of Protection
MetroCluster Failover Events
MetroCluster failover events
Site or Bldg A
Up to 200 km
Site or Bldg B
METROCLUSTER RANGE OF PROTECTION: METROCLUSTER FAILOVER EVENTS

MetroCluster software is an active-active solution, meaning that all nodes in each cluster actively serve data
to applications. Data can be read from the primary and secondary clusters, a feature that can also improve
read performance. MetroCluster technology is foundational for creating an active-active data center like the
Cisco Virtualized Multi-Tenant Data Center concept.
MetroCluster software protects against several types of failures.

Controller Failure

Controller failure
Site or Bldg A
Up to 200 km
Site or Bldg B
METROCLUSTER RANGE OF PROTECTION: CONTROLLER FAILURE

If a controller fails, local high-availability (HA) failover is used for NDO.

Storage or Rack Failure

Controller failure
Site or Bldg A
Storage or rack failure
Up to 200 km
Site or Bldg B
METROCLUSTER RANGE OF PROTECTION: STORAGE OR RACK FAILURE

In the case of a storage or rack failure where both HA partners fail, you would enter the command to switch
over to the MetroCluster configuration partner site.

Network Failure

Controller failure
Site or Bldg A
Up to 200 km
Network failure
Site or Bldg B
METROCLUSTER RANGE OF PROTECTION: NETWORK FAILURE

In the case of a network failure that makes the cluster or building inaccessible, you enter the command to
switch over to the MetroCluster configuration partner site.

Local Data Center Failure

Controller failure
Site or Bldg A
Up to 200 km
Network failure
Local data center failure
Site or Bldg B
METROCLUSTER RANGE OF PROTECTION: LOCAL DATA CENTER FAILURE

Recovery is similar in the case of local data center failure. For example, if you have two data centers on one
campus and one data center is unavailable because of a power, cooling, or networking issue, you enter the
command to switch over to the MetroCluster configuration partner site.

Complete Site Failure

Controller failure
Site or Bldg A
Up to 200 km
Network failure
Local data center failure
Site or Bldg B
Complete site failure
METROCLUSTER RANGE OF PROTECTION: COMPLETE SITE FAILURE

The case of a complete site failure is somewhat different. For example, if a natural disaster requires
evacuation of the entire campus, there are two possible business continuance paths. The two possible plans
rely on combining Data ONTAP data protection technologies, such as MetroCluster configuration and
SnapMirror technology.
If the MetroCluster configuration partner site has not been affected by the natural disaster, you can switch
over to that partner site.
If the MetroCluster configuration partner, located no more than 200 km away, has been affected by the natural
disaster, then you can resort to failing over to your SnapMirror secondary copies of the volumes.

Components of the MetroCluster Configuration
MetroCluster Software on Data ONTAP 8.3.0
Two Data ONTAP clusters Two Separate Data ONTAP Clusters

synchronously replicate to Site A Site B
each other. Active Nodes Active Nodes
A MetroCluster disaster Node A1 Synchronous

Replication Node B1
recovery group consists of A
one HA pair at each site

Local
(four nodes total). HA
Local
HA
In normal operation, clients

are served from all nodes Node A2 Node B2
COMPONENTS OF THE METROCLUSTER CONFIGURATION: METROCLUSTER

SOFTWARE ON DATA ONTAP 8.3.0
A MetroCluster configuration consists of two Data ONTAP clusters that synchronously copy to each other.
They are two distinct clusters, not a single cluster that is separated by distance. MetroCluster configurations
protect data on a local level and on a cluster level.
MetroCluster configurations protect data by using two physically separated, mirrored clusters. Each cluster
synchronously mirrors the data and storage virtual machine (SVM) configuration of the other. When a
disaster occurs at one site, you can activate the mirrored SVM and begin serving the mirrored data from the
surviving site.
The two clusters in the peered network provide bidirectional disaster recovery, where each cluster can serve
clients and also be the source and backup of the other cluster.
Also, the two nodes in each cluster are configured as an HA pair, providing local failover.

Two-Node MetroCluster Configuration
Data ONTAP 8.3.1 Introduced Two-Node MetroCluster Technology
Data ONTAP 8.3.1 introduced support for MetroCluster

configurations of two nodes, with a single-node cluster at
each site.
Single Up to 200 km Single

node node
MetroCluster
TWO-NODE METROCLUSTER CONFIGURATION: DATA ONTAP 8.3.1 INTRODUCED

TWO-NODE METROCLUSTER TECHNOLOGY
Earlier than clustered Data ONTAP 8.3.1, MetroCluster configurations were supported only on four nodes.
Data ONTAP 8.3.1 introduced support for MetroCluster configurations of two nodes, with a single-node
cluster at each site.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick quiz on the MetroCluster deployment options.

Poll Questions
1. Which statement about the MetroCluster range of data

protection is true?
a. MetroCluster software provides comprehensive protection against
controller, storage, network, and site failures within 200 km.
b. MetroCluster software provides comprehensive protection; however,
power failures are beyond the scope of MetroCluster.
c. MetroCluster software provides comprehensive protection; however,
network failures are beyond the scope of MetroCluster.
d. MetroCluster software provides comprehensive protection; however, shelf
failures are beyond the scope of MetroCluster.
2. True or False: In a four-node MetroCluster configuration,

each site has switchover and local failover capability.
a. True
b. False
POLL QUESTION: CHECK YOUR UNDERSTANDING

Ken Asks
What are some of the

MetroCluster options
and use cases that I
should be aware of?
KEN ASKS

Lesson 3
Synchronous Mirroring and
MetroCluster Use Cases
LESSON 3: SYNCHRONOUS MIRRORING AND METROCLUSTER USE CASES

MetroCluster Deployment Options
Questions to Investigate and Answer
A discussion of the MetroCluster deployment options and the

built-in features of Data ONTAP brings up several questions:
What MetroCluster deployment options are available?
What advantages are available by integrating MetroCluster
technology with SnapMirror and SnapVault software?
If the customer already has clustered Data ONTAP, why
would they need MetroCluster software?
METROCLUSTER DEPLOYMENT OPTIONS: QUESTIONS TO INVESTIGATE AND

ANSWER

Within Data Center
METROCLUSTER DEPLOYMENT OPTIONS

MetroCluster software can address your continuous-availability requirements. MetroCluster software can be
deployed inside a data center, at different locations in a building or campus, or across city-wide or metro-wide
deployments. The maximum supported distance between the two MetroCluster sites is 200 kilometers. This
capability enables a level of availability that goes beyond the high-availability features of a local cluster,
which makes MetroCluster technology a versatile solution.
MetroCluster software supports FAS arrays and non-FAS arrays that are virtualized with NetApp FlexArray
software.

Across Floors, Buildings, or Campus
Within Data Center

Across City or Metro Area
Within Data Center

Across City or Metro Area
Within Data Center
MetroCluster: Dedicated FC up to 200 km

MetroCluster with SnapMirror and SnapVault
Unlimited Distance
Up to 200 km
MetroCluster
Multiple Recovery Points

Local Data Center, Campus, or Metro Area Unlimited Distance
METROCLUSTER WITH SNAPMIRROR AND SNAPVAULT: UNLIMITED DISTANCE

You can combine MetroCluster technology with SnapMirror and SnapVault technology to achieve continuous
availability for data, not limited by distance.

Zero-Data-Loss Disaster Recovery
Disaster
Recovery Site
Up to 200 km SnapMirror
Unlimited Distance
MetroCluster

METROCLUSTER WITH SNAPMIRROR AND SNAPVAULT: ZERO-DATA-LOSS

DISASTER RECOVERY
SnapMirror technology enables you to asynchronously copy data over any distance. Data can be stored on
disks for faster recovery or backed up to tape for archiving or near-line storage. This capability is sometimes
called three-way disaster recovery or zero-data-loss disaster recovery.

Disk and Tape Backup
Disaster
Recovery Site
Unlimited Distance
Backup and
Recovery Site
MetroCluster
SnapVault
Unlimited Distance

METROCLUSTER WITH SNAPMIRROR AND SNAPVAULT: DISK AND TAPE BACKUP

MetroCluster software enables data to be backed up remotely to disk and then tape using SnapVault software.
This option provides a low-cost long-term archiving solution for data.

Low-Cost Long-Term Archiving Solution
Disaster
Recovery Site
Unlimited Distance
Backup and
Recovery Site
MetroCluster

METROCLUSTER WITH SNAPMIRROR AND SNAPVAULT: LOW-COST LONG-TERM

ARCHIVING SOLUTION
MetroCluster software enables data to be backed up remotely to disk with either a SnapMirror or a SnapVault
secondary copy. You can then use the secondary copy to offload archive copies to tape. This option provides
an even lower-cost long-term archiving solution for data.
For a fully integrated business continuity solution with disaster recovery and backup, all three kinds of
software can be implemented. This option provides the range of data storage and protection options that are
needed to meet the most stringent enterprise demands.

SnapMirror and SnapVault Integration
Up to 200 km
MetroCluster
Read/
Write
SnapMirror SnapVault
Disaster
Recovery Site
Read Read
Only Only
Backup and
Recovery Site
SNAPMIRROR AND SNAPVAULT INTEGRATION

With MetroCluster technology, SnapMirror and SnapVault relationships can be created by using the volumes
in the source plex as the primary volume.
It is not possible to create SnapMirror or SnapVault relationships with volumes in the MetroCluster
destination plex.

MetroCluster for NDO
The clustered Data ONTAP operating

system provides NDO within the data
center:
Ability to withstand component failures
Ability to perform maintenance operations without
disruption
Data Center A
Ability to perform technology refresh without
Clustered Data ONTAP disruption
Up to 200 km
MetroCluster technology enables

business continuity and continuous
availability beyond the data center.
Cluster A in Cluster B in
Data Center A Data Center B
MetroCluster
METROCLUSTER FOR NDO

If you already have clustered Data ONTAP, you might wonder why you need MetroCluster software. The
clustered Data ONTAP operating system already provides NDO within the data center. The local high-
availability capabilities of clustered Data ONTAP enable your data center to withstand component failures
and provide maintenance and upgrades without disruption.
However, MetroCluster technology enables business continuity and continuous availability beyond the data
center. MetroCluster software protects your data from events that are beyond the control of the IT
organization. Businesses cannot control fires, floods, or hurricanes. Other events threaten data availability,
such as network outage, power loss, and unrecoverable inconsistency. With MetroCluster software, your
organization remains up and running by using the synchronously replicated copy at the secondary site.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick quiz on MetroCluster continuous availability.

Poll Questions
1. In what two ways can you accomplish continuous

availability over any distance? (Choose two.)
a. Configure the MetroCluster configuration for unlimited distance.
b. Combine the MetroCluster configuration with SnapMirror technology.
c. Combine the MetroCluster configuration with SnapVault technology.
d. Combine the MetroCluster configuration with storage efficiency
technology.
2. True or False: MetroCluster technology provides the ability

to perform maintenance operations without disruption.
a. True
b. False

Ken Shares Exciting Information
I found two excellent MetroCluster

classes on the NetApp University
Learning Management System.
MetroCluster in Clustered Data ONTAP 8.3 Overview
MetroCluster Installation Workshop

Check it out!
KEN SHARES EXCITING INFORMATION

Module 4
Using NDMP for Data Protection
MODULE 4: USING NDMP FOR DATA PROTECTION
4-1 Data ONTAP Data Protection Administration: Using NDMP for Data Protection

Module Objectives

Describe NDMP communications, modes, and scope used
by the Data ONTAP operating system to move data from
disk to tape
Describe NDMP design considerations and topographies for
the Data ONTAP 8.3 operating system
Recall NDMP commands to configure communication
between a Data ONTAP cluster and tape libraries
Monitor and manage NDMP configurations
MODULE OBJECTIVES

Lesson 1
NDMP
LESSON 1: NDMP

NDMP Technology
NDMP is an industry-standard protocol that can control backup,
recovery, and data transfer between primary and secondary
storage devices.
All communications occur over TCP/IP or TCP/IP v6.
NDMP provides low-level control of tape drives and media
changers.
NDMP TECHNOLOGY
NDMP is an industry-standard protocol for controlling backup, recovery, and data transfer between primary
and secondary storage devices, including storage systems and tape libraries.
Enabling NDMP on a NetApp storage system enables that storage system to communicate with NDMP-
enabled backup applications.

Ken Asks
I dont understand some

of the NDMP terminology.
Can you explain it?
KEN ASKS

NDMP Concepts and Key Terms
Data management
application (DMA)
Direct-access recovery
(DAR)
Cluster Aware Backup

(CAB) extension
Connection address
extension (CAE)
Affinity
NDMP CONCEPTS AND KEY TERMS

There are several NDMP concepts and key terms. How many of these terms do you already know?

NDMP Concepts
Key Terms
Data management
Refers to your NDMP-based backup application
application (DMA)
Direct-access recovery
(DAR)

(CAB) extension
Connection address
extension (CAE)
Affinity
NDMP CONCEPTS: KEY TERMS

NDMP Concepts
Key Terms
Data management
application (DMA)
Direct-access recovery Refers to a configuration that enables quick

(DAR) access to secondary media

(CAB) extension
Connection address
extension (CAE)
Affinity

Direct-access recovery: Enables quick access to the secondary media during a recovery operation. In Data
ONTAP 8.3, enhanced direct-access recovery functionality is enabled by default. This functionality supports
direct-access recovery of directories and of files with alternate data streams.

NDMP Concepts
Key Terms
Data management
application (DMA)

Cluster Aware Backup An NDMP v4 extension that enables the NDMP

(CAB) extension server to establish data connections
Connection address
extension (CAE)
Affinity

Cluster Aware Backup (CAB) extension: The CAB extension is an NDMP v4 extension. This extension
enables the NDMP server to establish a data connection on a node that owns a volume. This extension also
enables the backup application to determine whether volumes and tape devices are on the same node in a
cluster.
To enable the NDMP server to identify the node that owns a volume and to establish a data connection on
such a node, the backup application must support the CAB extension. The CAB extension requires the backup
application to inform the NDMP server about the volume to be backed up or restored before establishing the
data connection. This requirement enables the NDMP server to determine which node hosts the volume and to
appropriately establish the data connection.
When the backup application supports the CAB extension, the NDMP server provides affinity information
about volumes and tape devices. If a volume and tape device are on the same node in a cluster, the backup
application can use the affinity information to perform a local backup instead of a three-way backup.

NDMP Concepts
Key Terms
Data management
application (DMA)

(DAR) access to secondary media.

Connection address An NDMP v4 extension that is used for IPv6

extension (CAE) support
Affinity

Connection address extension: NDMP in Data ONTAP 8.3 supports IPv6. The connection address
extension is used for IPv6 support.

NDMP Concepts
Key Terms
Data management
application (DMA)


Connection address An NDMP v4 extension that is used for IPv6

extension (CAE) support
A feature of CAB that can make a three-way

Affinity backup possible

Affinity: When the backup application supports the CAB extension, the NDMP server provides unique
location information about volumes and tape devices. Using this affinity information, if a volume and a tape
device share affinity, the backup application can perform a local backup instead of a three-way backup. If the
volume moves from node 1 to node 2, affinity information about the volume and tape device changes.
Affinity provides continuity of the backup policy for the volume, regardless of the node to which the volume
is moved.

Additional NDMP Concepts
NDMP Modes, Connections, and Variables
Node-scoped NDMP
mode
SVM-scoped NDMP
mode
NDMP control
connection
NDMP data connection
NDMP environment
variables
ADDITIONAL NDMP CONCEPTS: NDMP MODES, CONNECTIONS, AND VARIABLES

There are several NDMP modes, connections, and variables that you might encounter. How many of these
terms do you already know?

Node-scoped NDMP In Data ONTAP 8.2, this mode is enabled by

mode default for tape backups at the node level.
SVM-scoped NDMP
mode
NDMP control
connection
NDMP environment
variables

Node-scoped NDMP mode: Enables you to perform tape backup and restore operations at the node level. In
Data ONTAP 8.2 and later, node-scoped NDMP mode is deprecated.


With CAB, this mode enables you to perform
SVM-scoped NDMP
tape backups at the storage virtual machine
mode
(SVM) level.
NDMP control
connection
NDMP environment
variables

SVM-scoped NDMP mode: Enables you to back up and restore all volumes that are hosted across different
nodes in a storage virtual machine (SVM), provided that the backup application supports the CAB extension.
If your backup application supports the CAB extension, and if a volume and tape device share affinity, the
backup application can perform a local backup or restore operation instead of a three-way restore operation.


SVM-scoped NDMP With CAB, this mode enables you to perform

mode tape backups at the SVM level.
NDMP control This connection is used to manage NDMP

connection backup and restore requests and replies.
NDMP environment
variables




The NDMP data connection is used only to

transfer data.
NDMP environment
variables




The NDMP data connection is used only to

transfer data.
NDMP environment Environment variables communicate

variables information about backup operations.

NDMP environment variables: Used to communicate information about a backup or restore operation
between an NDMP-enabled backup application and a storage system. Typically, the backup application sets
the environment variables automatically. However, to support unique circumstances, the backup administrator
can set some environment variables manually. A backup administrator rarely specifies environment variables;
however, you might want to change the value of an environment variable to characterize or work around a
functional or performance problem. Many backup applications provide a means to override or modify
environment variables or to specify additional environment variables. For information, see your backup
application documentation.
Data ONTAP supports environment variables that have an associated default value. However, you can
manually modify these default values.
For a complete list of environment variables that are supported for SMTape and dump operations, see the
Clustered Data ONTAP 8.3 Data Protection Tape Backup and Recovery Guide.

Node-Scoped NDMP
Deprecated as of Data ONTAP 8.3
Uses only physical

resources and is not aware
of other nodes or any logical
Node-Scoped
NDMP
management DMA
Requires you to enable and

configure NDMP per node
Source
Volume
Node-Scoped NDMP is the default

configuration in Data ONTAP 8.2 and earlier.
NODE-SCOPED NDMP: DEPRECATED AS OF DATA ONTAP 8.3

Node-scoped NDMP was the default configuration in Data ONTAP earlier than 8.3. This setting behaves
much like NDMP in Data ONTAP operating in 7-Mode because it uses only physical resources, not logical
SVMs or logical interfaces (LIFs). Node-scoped NDMP is not cluster aware; therefore, NDMP in this mode is
not aware of other nodes or any logical management.
Node-scoped NDMP requires you to enable and configure NDMP on each node. The NDMP user must also
be set and defined on each node.
For clustered Data ONTAP, node-scoped NDMP cannot use the NDMP CAB extension with the benefit of
affinity.

Node-Scoped NDMP Described
Deprecated as of Data ONTAP 8.3
If a volume is moved to DMA must be
another node in the cluster,

reconfigured.
the data management

Node-Scoped
NDMP
applications backup policy DMA
must be reconfigured with the

new volume location.
Source Source volume

Volume is moved.
NODE-SCOPED NDMP DESCRIBED: DEPRECATED AS OF DATA ONTAP 8.3

If a volume is moved to another node in the cluster, or if the LIF fails over to a different node, the you must
reconfigure data management applications backup policy with the new volume location. Therefore, for
clustered Data ONTAP earlier than Data ONTAP 8.3, you must disable node-scoped NDMP and enable
SVM-scoped NDMP.
In Data ONTAP 8.3 and later, the default NDMP mode is SVM-scoped NDMP.

SVM-Scoped NDMP
Enabled by Default in Data ONTAP 8.3
SVM-scoped NDMP must

use an appropriate logical
SVM-Scoped
interface (LIF) type. NDMP
SVM-scoped NDMP DMA
automatically tracks the Control Data

source volume when moved. Connection Connection
Data or
Intercluster LIF
Source
Volume
SVM-Scoped NDMP is the default

configuration in Data ONTAP 8.3 and later.
SVM-SCOPED NDMP: ENABLED BY DEFAULT IN DATA ONTAP 8.3

In a new installation of Data ONTAP 8.3, by default, NDMP is enabled and appears in the allowed
protocols list. Also by default, NDMP is configured in SVM-scoped mode. You can only perform node-
scoped NDMP operations if you explicitly enable node-scoped NDMP mode.
An upgrade of Data ONTAP from 8.1 to 8.3 has different default NDMP configurations. NDMP might be
enabled or not. By default, NDMP is set to node-scoped mode. You must explicitly disable node-scoped
NDMP mode, so that tape backup and restore operations are performed in SVM-scoped NDMP mode.
NDMP authentication is now integrated with role-based access control (RBAC), which can be a single
cluster-wide user (such as admin).
SVM-scoped NDMP introduces LIF limitations and restrictions. NDMP must use an appropriate LIF type for
some resources. Some resource limitations are negated by a CAB extension.

SVM-Scoped NDMP
Enabled by Default in Data ONTAP 8.3
An upgrade of Data ONTAP

from 8.1 to 8.3 causes
NDMP to follow the node-
scoped behavior. DMA
If you upgrade from 8.1, you Control Data

must disable node-scoped Connection Connection
NDMP.
With CAB, SVM-scoped Source
NDMP can back up any Volume
volume on any node and use

any tape device in the entire
cluster.
SVM-SCOPED NDMP: ENABLED BY DEFAULT IN DATA ONTAP 8.3

If the data management application is CAB enabled, then NDMP can back up any volume on any node and
use any tape device in the entire cluster.

Volume and Tape Availability with CAB
NDMP CONTROL AVAILABLE VOLUMES AVAILABLE TAPE

CONNECTION DEVICES
LIF TYPE
Node-management LIF All volumes hosted by Tape devices connected
the node to the node hosting the
node-management LIF
Data LIF All volumes that belong to None

the SVM that hosts the
data LIF
Cluster-management LIF All volumes in the cluster All tape devices in
the cluster
Intercluster LIF All volumes in the cluster All tape devices in

the cluster
VOLUME AND TAPE AVAILABILITY WITH CAB

With a CAB application, the NDMP server provides affinity informationunique location information about
volumes and tape devices. Using this affinity information, the backup application can perform a local backup
instead of a three-way backup if a volume and a tape device share affinity.
The backup application can use the affinity information to determine whether a volume and tape device are on
the same node if the NDMP control connection is established on one of these LIF types:
Node management LIF
Cluster management LIF
Intercluster LIF
The backup application can then perform either a local or a three-way backup or restore operation. If the
NDMP control connection is established on a data LIF, then the backup application always performs a three-
way backup.
Using the affinity information about volumes and tape devices, the backup application performs a local
NDMP backup on the volume and tape device on node 1 in the cluster. If the volume moves from node 1 to
node 2, affinity information about the volume and tape device changes. Therefore, for a subsequent backup,
the backup application performs a three-way NDMP backup operation. Affinity information provides
continuity of the backup policy for the volume, regardless of the node to which the volume is moved.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick poll on NDMP terminology, modes, and scope.

Poll Questions
1. What does the abbreviation DMA refer to?

a. data maintenance application (refers to NDMP protocol)
b. data management application (refers to NDMP backup application)
c. direct management application (refers to quick access to media)
d. data migration application (refers to SnapMirror and data migration)
2. Which NDMP mode enables you to perform tape backups in

a cluster at the SVM level?
a. node-scoped NDMP with CAB capability on the data management
application
b. node-scoped NDMP without CAB on the data management application
c. SVM-scoped NDMP without CAB capability on the data management
application
d. SVM-scoped NDMP with CAB capability on the data management
application

Lesson 2
NDMP Models and Design
Considerations
LESSON 2: NDMP MODELS AND DESIGN CONSIDERATIONS

NDMP Backup Models
Defines Who Is Responsible for What
Clustered Data ONTAP supports three NDMP models:
Direct Indirect Three-

(local) (remote) way
NDMP BACKUP MODELS: DEFINES WHO IS RESPONSIBLE FOR WHAT

Support for the CAB feature was first introduced in the NetApp clustered Data ONTAP 8.2 operating system.
This feature provides seamless and efficient NDMP backups to tape in the multi-tenant SVM architecture of
clustered Data ONTAP. Third-party data management applications, in conjunction with the CAB extension in
their code, can perform backups to tape in the clustered Data ONTAP environment. With implementation of
the CAB solution, you can manage local, three-way, and remote backups to tape.

Local NDMP Backup
DMA
Control Connection Tape and Data Service
NDMP Control
Connection LIF Cluster
Node 1 Node 2
Data
Connection
LOCAL NDMP BACKUP

For local backup to tape in a CAB-aware clustered Data ONTAP environment, the volume to be backed up
and the tape drive must be present together on a node. The tape drive is visible to both of the nodes in the
cluster by way of the FC SAN.
For local backup to tape, data travels directly from the controller-node-hosting volume to the tape.

Remote NDMP Backup
DMA
Data Connection
Control Connection Tape and Data Service

NDMP Control
Connection LIF Cluster
Node 1 Node 2
REMOTE NDMP BACKUP

In a remote backup topology, the tape subsystem is hosted by the backup or media server that belongs to the
data management application architecture. This configuration is also known as controller-server backup
architecture.

Three-Way NDMP Backup
DMA
Control Connection
Tape Service Data Service
NDMP Control Cluster

Connection LIF
Node 1 NDMP Data

Node 2
Connection LIF
Data Connection
THREE-WAY NDMP BACKUP

A three-way backup is performed if a tape subsystem that is connected to one of the nodes in a cluster is used
to back up a volume that is hosted on another node in the same or a different cluster.
The path for a given backup (three-way or local) is determined by the data management application without
user intervention, depending on the location of the volume and the tape drive.
In a three-way backup, data travels from the node hosting the volume to the node hosting the tape drive and is
then written to the tape.

Supported NDMP Authentication Methods
There are two methods of authentication:

Plaintext type
Not used by SVM-scoped NDMP mode
Can be disabled by node-scoped NDMP mode
Challenge type
Default method used by SVM-scoped NDMP mode
Can be used by node-scoped NDMP mode
SUPPORTED NDMP AUTHENTICATION METHODS

In node-scoped NDMP mode, both authentication methods are enabled by default: challenge and plaintext.
You can disable plaintext, but you cannot disable challenge. In the plaintext authentication method, the login
password is transmitted as clear text.
In SVM-scoped NDMP mode, the default authentication method is challenge. You can choose to enable or
disable plaintext or challenge; however, one authentication mode must be enabled.

User Authentication in SVM-Scoped Mode
NIS
LDAP
NDMP user name and

password
Role-based access control (RBAC)
SVM Cluster
vsadmin admin
vsadmin-backup backup
USER AUTHENTICATION IN SVM-SCOPED MODE

In SVM-scoped NDMP mode, NDMP user authentication is integrated with RBAC. In the SVM context, the
NDMP user must have either the vsadmin or vsadmin-backup role. In a cluster context, the NDMP user
must have either the admin or backup role.
In SVM-scoped NDMP mode, you must generate an NDMP password for a given user account. The password
is created based on RBAC roles. Cluster users in an admin or backup role can access a node-management
LIF, cluster-management LIF, or an intercluster LIF. Users in a vsadmin-backup or vsadmin role can
access only the data LIF for that SVM. Therefore, depending on the role of a user, the availability of volumes
and tape devices for backup and restore operations varies.
This mode also supports user authentication for Network Information Service (NIS) and Lightweight
Directory Access Protocol (LDAP) users. Therefore, NIS and LDAP users can access multiple SVMs with a
common user ID and password. However, NDMP authentication does not support Active Directory users.
In SVM-scoped NDMP mode, a user account must be associated with the Secure Shell (SSH) application and
the user password authentication method.

NDMP Design Considerations
Generating file history

Firewall policy
LIF connections
CAB extension support
NDMP backup path format
Using ndmpcopy
Backup of SnapMirror
destination data
Scalability limits for NDMP
sessions
NDMP DESIGN CONSIDERATIONS

There are some design considerations to note when you start the NDMP service on the storage system. Details
follow.

Generating File History
NDMP services can generate file history data at the request

of NDMP backup applications.
Backup applications use file history to enable optimized
recovery of selected subsets of data from a backup image.
File history generation and processing might be time-
consuming and CPU-intensive for the storage system and the
backup application.
You can disable file history generation to reduce backup time.
GENERATING FILE HISTORY

NDMP services can generate file history data at the request of NDMP backup applications. Backup
applications use file history to enable optimized recovery of selected subsets of data from a backup image.
File history generation and processing might be time-consuming and CPU-intensive for the storage systems
and the backup applications.
If your data protection is configured for disaster recoverywhere the entire backup image is recoveredyou
can disable file history generation to reduce backup time. See your backup application documentation to
determine if it is possible to disable NDMP file history generation.

Firewall Policy
The firewall policy for NDMP is enabled by default on all

LIF types.
In node-scoped NDMP mode, to back up a FlexVol volume,
you must use the backup application to initiate a backup on
a node that owns the volume.
You cannot back up a node root volume.
FIREWALL POLICY
The firewall policy for NDMP is enabled by default on all LIF types. In node-scoped NDMP mode, to back
up a FlexVol volume, you must use the backup application to initiate a backup on a node that owns the
volume. However, you cannot back up a node root volume.

NDMP and Data ONTAP LIFs
Steps you must follow to set up LIFs for NDMP transfers:

Identify the intercluster LIF that you plan to use for NDMP
transfers.
Verify that NDMP services have been enabled on the firewall
policy.
Set the LIF failover policy to local-only so that the LIF does
not fail over to a different node in the cluster.
If a LIF fails over to a different node during an NDMP operation,
the NDMP operation fails and must be rerun.
NDMP AND DATA ONTAP LIFS

You must identify a LIF that will be used for establishing a data connection and control connection between
the node and the backup application. After identifying the LIF, you must verify that firewall and failover
policies are appropriately set for the LIF. Here are the steps to remember for setting up LIFs for NDMP
backups:
1. Identify the intercluster LIF that is hosted on the nodes by using the network interface show
command with the role parameter.
2. Verify that the firewall policy is enabled for NDMP by using the system services firewall
policy show command. If the firewall policy is not enabled, enable the firewall policy by using the
system services firewall policy modify command with the -service parameter.
3. Verify that the failover policy is set to local-only. To determine if the failover policy is correctly set,
use the network interface show failover command. If the failover policy is not set to
local-only, modify the failover policy by using the network interface modify command with the -
failover-policy parameter.

CAB Extension Support
The data management application must support CAB

extensions to use separate control and data connections with
the Data ONTAP cluster.
Data ONTAP Cluster

Upgraded to Version 8.3
Control
CAB supported here
Connection
DMA
Data
Connection
CAB EXTENSION SUPPORT

Format of the NDMP Backup Path
The NDMP backup path uses the following format:
IP_address:/vserver_name/volume_name/path_name
The vserver_name is the SVM name.

The path_name is the path of the directory, file, or Snapshot
copy.
FORMAT OF THE NDMP BACKUP PATH

The NDMP backup path uses the format IP_address:/vserver_name/volume_name/path_name, where
path_name is the path of the directory, file, or Snapshot copy.

Use of the ndmpcopy Command
The ndmpcopy command transfers full and incremental data

between storage systems using NDMP v4.
You can run ndmpcopy at the CLI of the source or destination
storage systems, or a storage system that is not the source or
destination of the data transfer.
You can also run ndmpcopy on a single storage system that
is both the source and destination of the data transfer.
USE OF THE NDMPCOPY COMMAND

The ndmpcopy command transfers data between storage systems using NDMP v4. Both full and incremental
data transfers can be performed. You can transfer full or partial volumes, qtrees, directories, or individual
files.
You can run ndmpcopy at the CLI of the source or destination storage systems, or a storage system that is
not the source or the destination of the data transfer. You can also run ndmpcopy on a single storage system
that is both the source and destination of the data transfer.
For the syntax and examples of the ndmpcopy command, see the Clustered Data ONTAP 8.3 Data
Protection Tape Backup and Recovery Guide.

Backup of SnapMirror Destination Data
When a SnapMirror destination is backed up to tape, only the

data on the volume is backed up.
The SnapMirror relationships and the associated metadata
are not backed up to tape.
Therefore, during restore, only the data on that volume is
restored.
BACKUP OF SNAPMIRROR DESTINATION DATA

When a SnapMirror destination is backed up to tape, only the data on the volume is backed up. The
SnapMirror relationships and the associated metadata are not backed up to tape. Therefore, during restore,
only the data on that volume is restored; the associated SnapMirror relationships are not restored.

Scalability Limits for NDMP Sessions
The maximum number of NDMP sessions depends on the

system memory of a storage system.
System Memory of a Maximum Number

Storage System of NDMP Sessions
Less than 16 GB 8
Greater than or equal to 16 GB 20

but less than 24 GB
Greater than or equal to 24 GB 36
SCALABILITY LIMITS FOR NDMP SESSIONS

You must be aware of the maximum number of NDMP sessions that can be established simultaneously on
storage systems of different system memory capacities. This maximum number depends on the system
memory of a storage system.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick quiz on NDMP models and design considerations.

Poll Questions
1. What are the three NDMP backup models? (Choose three.)

a. one-way
b. two-way
c. remote
d. local
e. three-way
2. Which two statements about NDMP design are true?

(Choose two.)
a. You must set the LIF failover policy to local-only.
b. NDMP services file history generation is not CPU intensive for the data
management application.
c. Whether NDMP is set to node-scope or SVM-scope mode, CAB
extension support on the data management application is required for
cluster-aware backups.
d. You cannot run ndmpcopy on a storage system that is not either the
source or the destination of the data transfer.

Lesson 3
Configuring NDMP on Data
ONTAP 8.3
LESSON 3: CONFIGURING NDMP ON DATA ONTAP 8.3

Configuring NDMP Services
Required NDMP Configurations
Data ONTAP Cluster
DMA
Data
Connection
CONFIGURING NDMP SERVICES: REQUIRED NDMP CONFIGURATIONS

In clustered Data ONTAP, there are several required NDMP configurations, all of which can be entered on
the cluster CLI. This slide shows a Data ONTAP cluster that has been upgraded from Data ONTAP 8.1 to
Data ONTAP 8.3.
The next slides show the required configurations to enable and configure NDMP for Data ONTAP clusters.

Data ONTAP Cluster
1. Enable NDMP services for the

cluster and SVMs. DMA
Data
Connection
system services ndmp on
vserver services ndmp on

vserver svm1

NDMP services must be enabled as a service. Use the system services ndmp on command to enable
NDMP as a service. Next, NDMP services must be enabled at the cluster level and at the SVM level. Use the
vserver services ndmp on command to enable NDMP for the cluster and for each SVM. The
cluster is actually a type of SVM; an administrative SVM.

Data ONTAP Cluster

Data
Connection
2. Allow NDMP services for
SVMs.

vserver svm1
vserver modify vserver

svm1 allowed-protocols

NDMP services must be allowed for SVMs as a protocol. You use the vserver -allowed-protocols
command to allow NDMP for each SVM. With this command, you cannot add one protocol without blocking
any protocol that is not specified in the command. When you use this command, ensure that you allow NDMP
and all of the protocols that should be allowed.
Example:
vserver modify vserver svm1 allowed-protocols cifs,iscsi,nfs,ndmp

Data ONTAP Cluster

Data
Connection
SVMs.
3. Enable SVM-scoped mode. system services ndmp on

vserver svm1
vserver modify vserver

svm1 -allowed-protocols
system services ndmp

node-scoped-mode off

If you are upgrading from an earlier version of Data ONTAP, node-scoped NDMP is set by default. You must
disable node-scoped mode. Disable node-scoped mode by enabling SVM-scoped NDMP.

Data ONTAP Cluster

Data
Connection
SVMs.
4. Generate the NDMP vserver services ndmp on

vserver svm1
password. vserver modify vserver
svm1 -allowed-protocols
system services ndmp

node-scoped-mode off
vserver services ndmp
generate-password

The NDMP password must be generated at the cluster level for the admin user. To generate a password,
you use the ndmp generate-password command.

Configuring NDMP Services Refresh
Data ONTAP Cluster

Data
Connection
SVMs.
4. Generate the NDMP vserver services ndmp on

vserver svm1
password. vserver modify vserver
svm1 allowed-protocols
5. From the data management system services ndmp
application server, refresh to node-scoped-mode off
detect NDMP connectivity. vserver services ndmp

generate-password

The data management application server must be refreshed to detect NDMP connectivity. How you refresh or
establish an NDMP data connection to the data management application depends on the type of backup
application server or solution you are deploying.

Enabling NDMP Services for the Cluster
Use the system services Command
The command to determine the status of NDMP services at

the cluster level:
system services ndmp show
The command to enable NDMP services at the cluster level:

ENABLING NDMP SERVICES FOR THE CLUSTER: USE THE SYSTEM SERVICES
COMMAND
You have allowed NDMP on all of the SVMs. However, even though NDMP is allowed, it must also be
enabled at the cluster level and for each SVM in all of the clusters involved in the SnapProtect
implementation.
The following are the two commands that you need to know to determine the status of NDMP services at the
cluster level and to enable NDMP services at the cluster level:

Enabling NDMP Services for SVMs
Use the vserver services Command
Enable NDMP services for data and administrative SVMs.

The command to determine the status of NDMP services at
the SVM level:
vserver services ndmp show
The commands to enable NDMP services for administrative

and data SVMs:
vserver services ndmp on vserver cluster1
vserver services ndmp on vserver svm1
ENABLING NDMP SERVICES FOR SVMS: USE THE VSERVER SERVICES COMMAND
You have enabled NDMP services at the cluster level. Next, you must enable NDMP services for each SVM.
The cluster itself is also a type of SVM, an administrative SVM. NDMP services must also be enabled for the
administrative SVM, which has the same name as the cluster.
The two commands that you need to know are similar to the commands that you used to enable NDMP
servers at the cluster level. At the cluster level, the command begins with system. At the SVM level, the
command begins with vserver. Assuming that the name of the cluster is cluster1, the following
commands are examples of how to show and enable NDMP services at the SVM level:
vserver services ndmp on vserver cluster1
vserver services ndmp on vserver svm1

Showing Allowed Protocols
Verifying NDMP for SVMs
The command to show allowed protocols for an SVM:

vserver show vserver <svm_name>
fields allowed-protocols
The expected output is the list of allowed protocols:

vserver show -vserver svm1
-fields allowed-protocols
vserver allowed-protocols
------- -----------------
svm1 nfs,cifs,iscsi
SHOWING ALLOWED PROTOCOLS: VERIFYING NDMP FOR SVMS

In clustered Data ONTAP, you must allow NDMP for each SVM without blocking other protocols that are in
use. If NDMP is not allowed, SnapProtect software cannot communicate with the SVM. When you attempt to
enable NDMP, if NDMP is not allowed, you get an error message that tells you NDMP is not allowed for the
SVM.
To allow NDMP for each SVM, you use the modify -allowed-protocols command; however, the
command that is used to add protocols to the SVM must contain all protocols that are to be allowed. Protocols
that are not listed in the modify -allowed-protocols command will be blocked.
Use the vserver show -allowed-protocols command to list the protocols that are currently
allowed so that you can include them when you enter the command to add NDMP.
NOTE: When you are working in the clustered Data ONTAP CLI, you can copy commands from the
Clustered Data ONTAP Commands Manual. Note, however, that the hyphen (-) in the command is often
pasted as a period. Your pasted command will fail until you edit the period and change it to a hyphen.

Allowing NDMP
All Allowed Protocols Must Be Included
The command syntax to allow NDMP on each of the SVMs:

vserver modify vserver <svm_name>
allowed-protocols <protocol_list>
Example command that includes all allowed protocols so that

none become disabled:
vserver modify vserver svm1
allowed-protocols cifs,iscsi,nfs,ndmp
ALLOWING NDMP: ALL ALLOWED PROTOCOLS MUST BE INCLUDED

After using the vserver show allowed-protocols command, you use the vserver modify -
allowed-protocol command to add NDMP and add back the other protocols that were shown to be
allowed.

Enabling Cluster-Aware NDMP
Turning off Node-Scoped Mode Automatically Turns on SVM-Scope Mode
In new installations of clustered Data ONTAP 8.3 and later,

node-scoped NDMP is disabled.
In a mixed cluster of different Data ONTAP 8.2 and 8.3
versions, node-scoped NDMP is enabled by default.
Ensure that you disable the node-scoped mode of NDMP to
allow NDMP communications at the SVM level.
Command to disable node-scoped NDMP:
system services ndmp node-scoped-mode off
ENABLING CLUSTER-AWARE NDMP: TURNING OFF NODE-SCOPED MODE

AUTOMATICALLY TURNS ON SVM-SCOPE MODE
In a mixed cluster where nodes are running Data ONTAP 8.2 and earlier versions in the Data ONTAP 8.x
release family, NDMP defaults to the node-scoped behavior (at the node level). This NDMP behavior
continues even after an upgrade to Data ONTAP 8.2. You must explicitly disable the node-scoped NDMP
mode to perform tape backup and restore operations in the SVM-aware mode.
In the node-scoped NDMP mode, the NDMP data connection uses the same LIF as the NDMP control
connection.

Generating NDMP Passwords
Specify the Cluster Admin Account
The syntax of the command to generate an NDMP password for a

user account for each SVM:
vserver services ndmp generate-password -vserver
<svm_name> <user_name>
Example command and output:

vserver services ndmp generate-password -vserver
cluster1 admin
Vserver: cluster1
User: admin
Password: IIXoLZjpf1R2Fhza
GENERATING NDMP PASSWORDS: SPECIFY THE CLUSTER ADMIN ACCOUNT

You can configure a cluster as a NAS server client or an SVM. If you configure an SVM as the SnapProtect
client, the CommCell Browser needs to authenticate with the NAS file server at the SVM level with the
vsadmin user name, rather than the admin user name.
You generate an NDMP password at the SVM level for the vsadmin user with the same command as for the
admin user on the cluster level. Be sure to record the admin and vsadmin encrypted passwords to use in
the CommCell Browser when you are configuring the cluster or SVM as a CommCell client.
NDMP user authentication is integrated with the role-based access control mechanism.
In an SVM context, the user must have either the "vsadmin" or "vsadmin_backup" role.
In a cluster context, the user must have either the "admin" or "backup" role.
The users NDMP password is based on the user's login password. To change a users NDMP password, use
the vserver services ndmp generate-password command. The NDMP password must be
regenerated every time the users login password changes.

Ken Asks
What are the commands

that I can use to
troubleshoot NDMP issues?
KEN ASKS

Verify the Preferred Data Connection LIF Type
Verify That the Data Management Application Can Connect to the Cluster via
NDMP
The -preferred-interface-role option of the vserver
services ndmp modify command determines the order in
which LIFs are tried when an NDMP data connection is being
established.
The default setting in the cluster context is
intercluster,node-mgmt,
cluster-mgmt.
The default setting in the SVM context is
intercluster,data.
VERIFY THE PREFERRED DATA CONNECTION LIF TYPE: VERIFY THAT THE DATA
MANAGEMENT APPLICATION CAN CONNECT TO THE CLUSTER VIA NDMP
In an SVM-aware NDMP mode, you can control the LIF type on which an NDMP data connection is
established.
You can specify the LIF types that are required for the NDMP data connection by using the preferred-
interface-role option. The format of this option is a comma-separated list of LIF types. When an
NDMP data connection is being established, NDMP chooses an IP address that belongs to the LIF type, as
specified by the preferred-interface-role option. The LIF type that is chosen is in the order that is
defined by this option. If the IP addresses do not belong to any of the LIF types, the NDMP data connection
cannot be established.
In the node-scoped NDMP mode, the NDMP data connection uses the same LIF as the NDMP control
connection.

Commands to Verify NDMP Configuration
Commands for Troubleshooting NDMP Issues for Clustered Data ONTAP
Commands to find the root cause of common NDMP issues:

1. Verify that node-scope-mode is disabled.
system services ndmp node-scope-mode status
2. Verify that NDMP is enabled for the cluster.

3. Verify that NDMP is enabled for each of the SVMs.

4. Verify that there is a network interface that is enabled for

intercluster network traffic.
network interface show
COMMANDS TO VERIFY NDMP CONFIGURATION: COMMANDS FOR

TROUBLESHOOTING NDMP ISSUES FOR CLUSTERED DATA ONTAP
NDMP configurations are a key part of successful SnapProtect operations. To prevent issues, verify that the
NDMP configurations have been implemented correctly.
To verify that NDMP is properly configured for clustered Data ONTAP systems, enter commands on the Data
ONTAP cluster CLI to be sure to set the following configurations:
1. Disable NDMP node-scope mode.
2. Enable NDMP for the cluster.
3. Enable NDMP for each of the SVMs.
4. Enable a network interface for intercluster network traffic.
To verify that NDMP is properly configured for Data ONTAP operating in 7-Mode, confirm that NDMP has
been enabled.

ACTION: Try This
In your exercise kit, log in to cluster 1 and enter the following command:
vserver services ndmp version

What NDMP version does the cluster support?

Is NDMP enabled for the cluster?

In NDMP enabled for node1 or node2?
ACTION: TRY THIS

Take a few minutes to try these commands and become familiar with the output.

I had no idea that I could use

NDMP in so many useful
ways. I am looking forward to
getting my applications set up
for SVM-scoped backup.

References
NetApp University course:

NetApp Documentation:
Clustered Data ONTAP 8.3 Data Protection Tape Backup and
Recovery Guide
NetApp KB ID: 1014598. How to identify which resources are
available through NDMP based on LIF type.
REFERENCES

Module 5
Implementing and Managing
MODULE 5: IMPLEMENTING AND MANAGING SNAPMIRROR TECHNOLOGY

In this module, you learn how SnapMirror technology works. You learn how to implement SnapMirror
relationships and how to use SnapMirror replicas to fail over during a disaster and then fail back to normal
operations.
5-1 Data ONTAP Data Protection Administration: Implementing and Managing SnapMirror Technology

Module Objectives

Describe SnapMirror technology and design criteria
Configure and implement SnapMirror relationships
Manage SnapMirror failover and resynchronization scenarios
Recall several SnapMirror administration topics
MODULE OBJECTIVES
After you complete this module, you should be able to describe, implement, and administer SnapMirror
relationships in normal and disaster scenarios.

Lesson 1
LESSON 1: SNAPMIRROR TECHNOLOGY

Lesson 1 discusses the basics of SnapMirror technology, including the following topics:
Business uses of SnapMirror technology
SnapMirror replication workflow
SnapMirror and Snapshot copies
Intracluster and intercluster SnapMirror requirements
SnapMirror technology and storage efficiency
SnapMirror technology and the volume automatic resizing feature
SnapMirror technology and the volume move feature
SnapMirror technology and version flexibility

SnapMirror Capabilities in Normal Mode
SnapMirror technology is an enterprise solution for data

replication.
Increasing Probability Increasing Downtime
Operational Application Component Site Regional

Failures Failures Failures Failures Disasters
Source Destination
SnapMirror Relationship
Clients
Normal Mode
SNAPMIRROR CAPABILITIES IN NORMAL MODE

SnapMirror software is an enterprise solution for replicating data between nodes or between clusters, over
local-area, wide-area, and FC networks.

SnapMirror Capabilities in Failover Mode
No matter what the issue, if you have configured a SnapMirror

relationship, SnapMirror enables you to fail over to a secondary
source of your data.
Increasing Probability Increasing Downtime
Operational Application Component Site Regional

Failures Failures Failures Failures Disasters
Offline Source Writable Destination
SnapMirror Broken SnapMirror Relationship
Clients
Failover Operations
SNAPMIRROR CAPABILITIES IN FAILOVER MODE

The SnapMirror solution addresses multiple objectives, such as protection of mission-critical data and
business continuance.

SnapMirror Capabilities in Other Scenarios
Uses for SnapMirror relationships:

Data protection
Data migration
Load sharing
Staging for remote tape archival
SnapMirror
Destination
SNAPMIRROR CAPABILITIES IN OTHER SCENARIOS

SnapMirror relationships can be deployed to facilitate data migration, load sharing, and remote tape archival.
Data ONTAP 8.3 provides the following types of SnapMirror replications:
Data protection mirror copies: These copies provide replication to create a backup copy within the
same cluster (intracluster) or in a different cluster (intercluster).
Data migration: With SnapMirror technology, you can migrate data from one clustered Data ONTAP
node or cluster to another without interrupting access to the data.
Load-sharing (LS) mirror copies: These copies provide replication from one volume to multiple
volumes in the same cluster to distribute a read-only workload across a cluster. You can distribute data to
load-balancing client access to provide local, read-only access to more clients.
Staging: You can use SnapMirror copies for staging backup offloading to tape archival. SnapMirror
technology attaches the off-site cluster to the SnapMirror destination node and volume, offloading tape
backup overhead from production servers.

SnapMirror Replication Workflow
Step 1
When the scheduler triggers a replication update, the

following operations are performed:
The SnapMirror destination 1
triggers the source to
create a Snapshot copy.
Source Destination
SnapMirror
SNAPMIRROR REPLICATION WORKFLOW: STEP 1

When the job schedule signals a time for action, the SnapMirror destination starts a four-step process to
update the SnapMirror destination volume.
First, the scheduler on the SnapMirror destination node triggers the source storage virtual machine (SVM) to
create a Snapshot copy on the source volume.

Step 2

2 The SnapMirror destination 1

A Snapshot copy is created on triggers the source to create
the source volume. a Snapshot copy.
Source Destination
SnapMirror

The second step is performed on the SnapMirror primary volume. Data ONTAP creates a Snapshot copy of
the SnapMirror primary volume.

Step 3


Source Destination
SnapMirror
3 Block-level differences are

mapped and transferred to
the destination volume.

The third step is also performed on the SnapMirror primary volume. The Data ONTAP operating system
calculates the block-level difference between the new Snapshot copy and the most recent Snapshot copy.
Then Data ONTAP transfers the changed blocks to the destination volume. Data ONTAP also transfers any
other Snapshot copies that were created between the most recent Snapshot copy and the new Snapshot copy.

Step 4


Source Destination
SnapMirror
3 Block-level differences are When the transfer is complete, a 4

mapped and transferred to Snapshot copy is created on the
the destination volume. updated destination volume.

The fourth step takes place on the SnapMirror destination volume. When the transfer of changed data from
the primary volume to the destination volume is complete, Data ONTAP creates a Snapshot copy on the
SnapMirror destination volume.
At the conclusion of the SnapMirror update process, a SnapMirror destination volume is available for read-
only access if it is shared using the CIFS protocol and is exported using the NFS protocol. A LUN in the
replicated volume can be made available to a client that supports connection to read-only LUNs.
Replication occurs at the volume level. Qtrees can be created in clustered Data ONTAP and copied with the
mirrored volume. However, individual qtrees cannot be mirrored separately.

SnapMirror and Snapshot Copies
SnapMirror software maintains a history of one SnapMirror

Snapshot copy on the source volume and two copies on the
destination volume.
Source Destination
SnapMirror
One Snapshot copy Two Snapshot copies on

on the source volume the SnapMirror destination
volume
SNAPMIRROR AND SNAPSHOT COPIES

SnapMirror software maintains a history of one SnapMirror Snapshot copy on the source volume and two
copies on the destination volume. Between the source and destination volumes, there is always at least one
common Snapshot copy. The common Snapshot copy is used whenever you need to resynchronize the
SnapMirror relationship.
To preserve optimum performance, you should schedule SnapMirror updates to occur on the source volume at
a different time from other Snapshot copies.

Intracluster and Intercluster SnapMirror
Location and Uses of the Destination Volume: 1 of 3
Source Destination
SnapMirror
Intracluster
SnapMirror
relationship
INTRACLUSTER AND INTERCLUSTER SNAPMIRROR: LOCATION AND USES OF

THE DESTINATION VOLUME: 1 OF 3
SnapMirror technology in Data ONTAP 8.3 provides asynchronous, volume-level replication based on a
replication update schedule that you configure. SnapMirror technology begins the replication process with a
NetApp Snapshot copy of the source volume and then a transfer of the data across the network to the
SnapMirror destination volume.
SnapMirror relationships can be configured as intracluster relationships or intercluster relationships. In
intracluster relationships, the source and destination volumes reside in the same cluster, either on the same
node or on different nodes. In the example, the source and destination volumes are located in the same Data
ONTAP cluster, in different SVMs of the cluster.

Source Destination
SnapMirror
Intracluster
SnapMirror
relationship
WAN Intercluster
SnapMirror SnapMirror
relationship
Destination

In intercluster SnapMirror relationships, the source and destination volumes reside in different clusters. To
create an intercluster SnapMirror relationship, you must configure cluster peering relationships and SVM
peering relationships.

Source Destination
SnapMirror
Intracluster
SnapMirror
relationship
WAN Intercluster
relationship
Destination Tape Using

FlexClone destination
volumes volumes

Whether you have deployed an intracluster or an intercluster SnapMirror relationship, you can use the
SnapMirror destination volume for disaster recovery and other purposes.
You can use the SnapMirror destination volume as a source for FlexClone volume clones. FlexClone volume
clones are writable and can facilitate application development & test or reporting. FlexClone volume clones
are storage efficient and can be deleted without consequence to the primary data.
If you use the SnapMirror destination volume as a parent volume for a FlexClone volume clone, be sure to
create a separate SnapMirror Snapshot copy for it on the source volume. Otherwise, you might encounter a
busy Snapshot copy issue because the FlexClone volume clone locks the Snapshot copy.
You can also use the SnapMirror destination as a staging device for tape backups. You can attach a tape
library directly to a node in the Data ONTAP cluster, or you can offload data indirectly to a tape library
attached to a server in the network. Regardless of the tape topology you deploy, you can use the SnapMirror
destination volume to offload the data, rather than backing up from the production volume.

Try This
Determine if cluster peering has been configured:

Determine if storage virtual machine (SVM) peering has been
configured:
cluster1::> vserver peer show
Determine if there is a subnet that can be used for intercluster

traffic:
cluster1::> network subnet show
TRY THIS
Take this opportunity and determine if cluster and SVM peering have been configured. You can also
determine if there is a subnet for intercluster traffic.

SnapMirror and Volume Automatic Resizing
When the source volume automatically grows, the destination

volume also grows.
Source Destination
Automatic Automatic
SnapMirror updates
Resizing Resizing
SNAPMIRROR AND VOLUME AUTOMATIC RESIZING

You can manage data growth in the primary volume by configuring volume automatic resizing. As source
data grows, Data ONTAP automatically increases the size of the source volume based on size thresholds that
you configure on that volume.
When the source volume size automatically increases, the size of the destination volume automatically
increases. In clustered Data ONTAP, there are several types of volumes, including FlexVol volumes and
infinite volumes. The automatic resizing feature is available only with FlexVol volumes, not infinite volumes.

SnapMirror and Volume Move
A data protection source or destination volume can be moved

nondisruptively to another node in the cluster without
reconfiguring the SnapMirror relationship.
Cluster1 Cluster2
Aggr1 Aggr2 Aggr3 Aggr3 Aggr1 Aggr2
Source Destination
Volume Move Volume Move
SNAPMIRROR AND VOLUME MOVE

With clustered Data ONTAP, you can nondisruptively move a SnapMirror source volume or destination
volume to another aggregate on the same node or to an aggregate on a different node within a cluster.
You might want to move a volume from FC to SATA disks, or you might want to free disk space without
affecting the SnapMirror relationship. SnapMirror configurations, and even storage efficiency configurations,
are revised automatically and do not need to be manually changed.
To nondisruptively move a volume, even a volume that is a part of a SnapMirror configuration, uses the
volume move command.

SnapMirror and Storage Efficiency
Deduplication and Compression
If a SnapMirror source volume is in a deduplicated or

compressed state, the destination volume remains so.
Storage efficiency Storage efficiency
enabled on source Maintained on destination
Source Destination
SnapMirror updates
Compression Compression maintained

enabled on source on destination
SNAPMIRROR AND STORAGE EFFICIENCY: DEDUPLICATION AND COMPRESSION

In Data ONTAP 8.3 and later, the term volume deduplication has been replaced with the term storage
efficiency. SnapMirror technology supports NetApp deduplication and compression storage efficiency
technologies.
If you implement storage efficiency and a SnapMirror source volume is in a deduplicated state, the destination
volume remains in a deduplicated state. Along with storage efficiency, you have network efficiency because
SnapMirror does not inflate the deduplicated data during the transfer from primary to secondary storage.
Likewise, if a SnapMirror source volume is in a compressed state, the destination volume remains
compressed. SnapMirror does not decompress the source data before or during the transfer to the destination
volume. Data is replicated in a compressed state.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick quiz on SnapMirror data protection technology.

Poll Questions
1. Which two statements about SnapMirror technology are

true? (Choose two.)
a. SnapMirror replicates data between nodes or between clusters, over
LAN, WAN, and FC networks to protect mission-critical data.
b. Data protection mirrors and load-sharing mirrors serve the same purpose.
c. SnapMirror can protect against site failures but not regional disasters.
d. SnapMirror software maintains a history of one SnapMirror Snapshot
copy on the source volume and two copies on the destination volume.
2. How does the SnapMirror policy work to trigger updates?

a. The SnapMirror destination SVM triggers replication updates.
b. The primary SVM triggers replication updates.
c. The primary cluster triggers replication updates.
d. The SnapMirror primary volume triggers replication updates.

Ken Asks
How do I set up a SnapMirror

relationship?
KEN ASKS

Steps to Configure SnapMirror Relationships
If you use the CLI to create and schedule updates for a

SnapMirror relationship, the following steps are required:
1. Verify that the Data ONTAP cluster is licensed for
SnapMirror.
2. Create a destination volume.
3. Select an update schedule.
4. Specify a data protection SnapMirror policy.
5. Initialize the SnapMirror baseline copy.
6. Monitor the SnapMirror transfers.
STEPS TO CONFIGURE SNAPMIRROR RELATIONSHIPS

SnapProtect management software, Symantec, and other data protection solutions use SnapMirror technology
to mirror volumes. You can also configure SnapMirror relationships from the CLI or from OnCommand
System Manager. To create and schedule an intracluster SnapMirror relationship, follow these steps:
1. Verify that the Data ONTAP cluster is licensed for SnapMirror. The SnapMirror license must be installed
on the cluster and then enabled on the primary and destination SVM.
2. Create a destination volume that is of the appropriate size. Verify that the volume automatic resizing
settings for the destination volumes are the same as the settings for the source volumes.
3. Select an update schedule. The list of default Snapshot copy schedules includes a schedule for mirror
replication.
4. Specify a data protection SnapMirror policy. The SnapMirror policy designates the source and destination
volumes.
5. Initialize the SnapMirror baseline copy. To save time, you should create a dedicated network for the
initial copy of the source volume onto the destination volume.
6. Monitor the SnapMirror transfers. Connect to the destination SVM from the CLI or from OnCommand
System Manager. From the destination SVM, you can verify that the initial and scheduled update
transfers are complete.
Details and commands for implementing each step follow.

Verifying That SnapMirror Is Licensed
For intercluster SnapMirror relationships, both clusters must be

licensed.
To verify that SnapMirror licenses are installed on the source
and destination clusters, use one of the two license-show
command variations:
cluster1::> license show -package SnapMirror

cluster2::> license show -instance -package SnapMirror
VERIFYING THAT SNAPMIRROR IS LICENSED

Before you begin to create SnapMirror relationships, verify that your SnapMirror software is licensed. If you
are setting up an intercluster SnapMirror relationship, verify that the SnapMirror license has been installed on
the source cluster and the destination cluster.
To verify that the SnapMirror licenses are installed, use the following command:
cluster1::> license show -package SnapMirror
Serial Number: 1-80-000099
Owner: cluster1
Package Type Description Expiration
----------------- ------- --------------------- -------------
SnapMirror site SnapMirror License -

You can use a slightly different command to view the SnapMirror license on cluster2:
cluster2::> license show -instance -package SnapMirror
(system license show)
Serial Number: 1-80-000099
Package: SnapMirror
Owner: cluster2
Expiration Date: -
Description: SnapMirror License
Type: site
Legacy: no
Customer ID: 1-82-0000000000000000000000000
The licenses are in place.

Creating a Destination Volume
Create a SnapMirror Destination Volume on the Same or a Different Cluster
The SnapMirror destination volume must be a data-protection

type volume.
To create a data protection volume to be used as the
destination volume, use the following example command:
cluster2::> volume create -vserver svm1_2 -volume

svm1_2_vol2 -aggregate aggr1 -size 200m -security-
style ntfs -type dp
CREATING A DESTINATION VOLUME: CREATE A SNAPMIRROR DESTINATION

VOLUME ON THE SAME OR A DIFFERENT CLUSTER
You can create a SnapMirror relationship between volumes on different clusters for disaster recovery. You
must create a destination volume for creating a SnapMirror relationship.
If you are using the CLI to create a SnapMirror relationship, you must manually create the destination
volume. The destination volume must be type DP:
cluster2::> volume create -vserver svm1_2 -volume svm1_2_vol2 -aggregate
aggr1 -size 200m -security-style ntfs -type dp
cluster2::> volume show -volume svm1_2_vol2
Vserver Volume Aggregate State Type Size Available Used%
------ ------- ---------- ------- ---- ------ ---------- -----
svm1_2 svm1_2_vol2 aggr1 online DP 200MB 199.88MB 0%

Create a SnapMirror Relationship
Specify Four Settings for a New SnapMirror Relationship
You must specify the destination path, the source path, the
schedule, and the SnapMirror type.
To create a SnapMirror relationship, use this command:
cluster2::> snapmirror create -destination-path

svm1_2:svm1_2_vol2 -source-path svm1:svm1_vol3
-type DP -schedule 5min
Use the following command to verify the new relationship:
cluster2::> snapmirror show
CREATE A SNAPMIRROR RELATIONSHIP: SPECIFY FOUR SETTINGS FOR A NEW

SNAPMIRROR RELATIONSHIP
Remember that SVM peering is a required configuration for intracluster SnapMirror relationships. SVM
peering and cluster peering are required configurations for intercluster SnapMirror relationships.
Create a data protection mirror relationship by using the snapmirror create command. Four settings are
specified in the sample command: destination path, source path, schedule, and mirror type.
cluster2::> snapmirror create -destination-path svm1_2:svm1_2_vol2 -
source-path svm1:svm1_vol3 -type DP -schedule 5min
Operation succeeded: snapmirror create for the relationship with
destination "svm1_2:svm1_2_vol2".
To verify that the relationship was created, use the snapmirror show command:
The output of the snapmirror show command informs you that the SnapMirror relationships begin in an
uninitialized state.

Initializing the SnapMirror Relationship
Initialization Copies Baseline from Source to Destination Volume
The following command initializes the SnapMirror relationship

for the specified destination volume:
cluster2::> snapmirror initialize destination-path
svm1_2:svm1_2_vol2
The following commands verify initialization:

cluster2::> snapmirror show -instance
INITIALIZING THE SNAPMIRROR RELATIONSHIP: INITIALIZATION COPIES

BASELINE FROM SOURCE TO DESTINATION VOLUME
After you have created the SnapMirror relationship, you must initialize it to copy the source data to the
destination volume. In the initialization command, you only have to specify the destination path. The
SnapMirror relationship that you already defined supplies the initialization command with the source path.
In the sample snapmirror initialize command, the destination path is the only field specified.
cluster2::> snapmirror initialize -destination-path svm1_2:svm1_2_vol2
Operation is queued: snapmirror initialize of destination
"svm1_2:svm1_2_vol2".
To verify that the initialization occurred correctly, use the snapmirror show command:
The output of the snapmirror show command contains detailed information about the initialization
transfer. The snapmirror show command also informs you that the SnapMirror relationship in now in the
snapmirrored state, rather than in the uninitialized state.

Monitoring SnapMirror Snapshot Copies
You can view the Snapshot copies on the source and

destination volumes:

cluster2::> volume snapshot show volume svm1_2_vol2
SnapMirror maintains a history of one SnapMirror

Snapshot copy on the source volume and two copies on
the destination volume.
MONITORING SNAPMIRROR AND SNAPSHOT COPIES

You can use the volume snapshot show command to view the Snapshot copies that are maintained on the
source and destination volumes. To preserve optimum performance, you can use this command to verify that
SnapMirror updates are not scheduled to occur on the source volume at the same time as other Snapshot
copies.
Notice that the names of the Snapshot copies on the source and destination volumes have the prefix
snapmirror and end with a date stamp:
Sample names of SnapMirror Snapshot copies:

snapmirror.1383c700-4345-11e4-97f5-0050560140c1_2147484679.2015-09-24_131500
snapmirror.1383c700-4345-11e4-97f5-0050560140c1_2147484679.2015-09-24_131000
snapmirror.1383c700-4345-11e4-97f5-0050560140c1_2147484679.2015-09-24_131500

Scheduling SnapMirror Updates with Cron
Create an Hourly Cron Job on the Destination Cluster
To create a cron job on the destination cluster to run at the

top of every hour, use the following command:
cluster2::> job schedule cron create Hourly_SnapMirror

hour all minute 0
To verify that the cron job was created correctly, use the
following command:
SCHEDULING SNAPMIRROR UPDATES WITH CRON: CREATE AN HOURLY CRON

JOB ON THE DESTINATION CLUSTER
In the snapmirror create command, you specify a schedule for the automatic update of the SnapMirror
relationship. You can use a default cron schedule or create a customized cron job to schedule SnapMirror
updates.
In the example, a cron job called Hourly_SnapMirror is created. This cron job is configured to run every hour
at the zero minute of every hour. Verify cron jobs with the job schedule cron show command.
cluster2::> job schedule cron create Hourly_SnapMirror -hour all -minute
0
Name Description
---------------- ---------------------------------------------------
5min @:00,:05,:10,:15,:20,:25,:30,:35,:40,:45,:50,:55
8hour @2:15,10:15,18:15
Hourly_SnapMirror @:00
SnapVaultJob @:10
daily @0:10
hourly @:05
weekly Sun@0:15

Modifying the SnapMirror Relationship
Change the SnapMirror Update Schedule
Apply the Hourly_SnapMirror schedule to an existing

relationship:
cluster2::> snapmirror modify -destination-path

cluster2://svm1_2/svm1_2_vol2 -schedule
Hourly_SnapMirror
Verify that the schedule is applied to the relationship:
cluster2::> snapmirror show -destination-path

cluster2://svm1_2/svm1_2_vol2 -fields schedule
MODIFYING THE SNAPMIRROR RELATIONSHIP: CHANGE THE SNAPMIRROR

UPDATE SCHEDULE
The schedule that you specify at the time that you create a SnapMirror relationship can be modified by using
the snapmirror modify command and the schedule option.
After you enter the example snapmirror modify command, the SnapMirror updates are performed on
the new schedule:
cluster2::> snapmirror modify -destination-path cluster2://svm1_2/svm1_2_vol2 -
schedule Hourly_SnapMirror
Operation succeeded: snapmirror modify for the relationship with destination
"svm1_2:svm1_2_vol2".
Verify the change of schedule with the snapmirror show command:
cluster2::> snapmirror show -destination-path cluster2://svm1_2/svm1_2_vol2 -
fields schedule
source-path destination-path schedule
-------------- ------------------ -----------------
svm1:svm1_vol3 svm1_2:svm1_2_vol2 Hourly_SnapMirror
SnapMirror updates are now performed hourly.

ACTION: Exercise

exercise
equipment.
Open your
credentials
provided Turn to: Complete the
by your Exercise 5, specified tasks.
instructor. Part 1.
Stop after
Task 2. Q&A
ACTION: EXERCISE

What commands can you use to

determine if the source and destination
SVMs are prepared for a SnapMirror
relationship?
What are some of the items of
information that you can determine from
the snapmirror show command?
What are the necessary steps to access
data that was replicated to the
SnapMirror destination read-only
volume?

BASED EXERCISE

Lesson 2
SnapMirror Failover and
Resynchronization
LESSON 2: SNAPMIRROR FAILOVER AND RESYNCHRONIZATION

Normal Operations
Clients Write to the Source Volume
A data center volume named src_vol that clients access is

mirrored to a disaster-recovery volume named dst_vol.
Source Destination
SnapMirror
SVM1 SVM2
Clients src_vol dst_vol
NORMAL OPERATIONS: CLIENTS WRITE TO THE SOURCE VOLUME

A critical volume is being accessed by clients. A SnapMirror relationship has been created with the CLI to
protect the source volume, similar to the SnapMirror relationship that you created earlier in the equipment-
based exercise.

Initialize the SnapMirror Relationship
The snapmirror initialize Command
To initialize the SnapMirror relationship, use this command:
snapmirror initialize destination -path svm2:dst_vol
Source Destination
SnapMirror
SVM1 SVM2
Command is
run here
Writing Data
src_vol dst_vol
Clients
INITIALIZE THE SNAPMIRROR RELATIONSHIP: THE SNAMPMIRROR INITIALIZE

COMMAND
To initialize the SnapMirror relationship, you run the snapmirror initialize command from the
SnapMirror destination node.
The snapmirror initialize command establishes normal operations with the writable data on the
source volume and a read-only copy stored on the destination volume in the disaster recovery colocation.
Clients continue accessing the SnapMirror source volume with read and write requests in normal operation
mode.

Test Mode
Clients Access Source Volume; SnapMirror Relationship Is in Normal Mode
Verify that clients can access the SnapMirror source volume.

Verify that the SnapMirror destination is up to date and idle.
Source Destination
dc>
SnapMirror
SVM1 SVM2
Writing Data
src_vol dst_vol
Clients
TEST MODE: CLIENTS ACCESS SOURCE VOLUME; SNAPMIRROR RELATIONSHIP

IS IN NORMAL MODE
After setting up and initializing a SnapMirror relationship, test it.
To prepare for test mode, verify that clients are able to read and write to the SnapMirror source volume. Also
verify that the state of the SnapMirror relationship is mirrored and that the transfer state is idle and not
transferring.

Test Mode
Quiesce the SnapMirror Relationship
The command to quiesce the SnapMirror relationship:
snapmirror quiesce -source-path svm1:src_vol
Source Destination
dc>
SnapMirror
SVM1 SVM2 Command is
run here
Writing Data
src_vol dst_vol
Clients
TEST MODE: QUIESCE THE SNAPMIRROR RELATIONSHIP

For testing purposes, you should quiesce the SnapMirror relationship so that scheduled updates are not started
during the test. To quiesce the SnapMirror relationship, run the following command from the destination
SVM: snapmirror quiesce.
The snapmirror quiesce command disables future transfers for a SnapMirror relationship. If there is
no transfer in progress, the relationship becomes quiesced. If there is a transfer in progress, it is not
affected, and the state of the SnapMirror relationship is posted as quiescing until the transfer is complete. If
you use the snapmirror abort command to abort the transfer, the current transfer aborts and does not
restart.

Test Mode
SnapMirror Relationship Is Stopped
The command to break the SnapMirror relationship:
snapmirror break -source-path svm1:src_vol
Source Destination
(Writable)
dc>
SnapMirror
run here
Writing Data
src_vol dst_vol
Clients
TEST MODE: SNAPMIRROR RELATIONSHIP IS STOPPED

Next, you run the snapmirror break command from the destination volume. The destination volume is
now writable, and you can run test writes to the destination volume.
During the test, verify that clients can continue to read and write data to the source volume.

Test Mode
Write to the Destination Volume
Test your ability to write to the destination volume, share the

volume, map a drive to the shared volume, and attempt to
create a file.
Source Destination
(Writable)
dc>
SnapMirror
run here
Writing Data Writing Test Data

src_vol dst_vol
Clients \\SVM2\dst_vol
TEST MODE: WRITE TO THE DESTINATION VOLUME

After SnapMirror software stops and the destination volume becomes writable, run test writes to the
destination volume. During test mode, while you are writing data to the destination volume, clients continue
to write data to the source volume. The data that you write to the destination volume during test mode is
nonproduction data that can be overwritten or deleted.

Resumption of Normal Operations
Clients Write to Source Volume; Destination Returns to Read-Only
Reestablish the original SnapMirror relationship by running the

snapmirror resync command from the destination:
snapmirror resync destination-path svm2:dst_vol
Source Destination
SnapMirror
run here
Writing Data
src_vol dst_vol
Clients
RESUMPTION OF NORMAL OPERATIONS: CLIENTS WRITE TO SOURCE VOLUME;

DESTINATION RETURNS TO READ-ONLY
After the test is complete and you want to return to normal operations, you use the snapmirror resync
command. The snapmirror resync command establishes or reestablishes a SnapMirror relationship
between the source and destination volumes. The snapmirror resync command must be run from the
destination node CLI.
If it is run from the wrong node, the snapmirror resync command can cause data loss on the
destination volume because the command removes the newest Snapshot copies and written data on the
destination volume.
The snapmirror resync command first finds the most recent common Snapshot copy between the
source and destination volumes. The command next removes Snapshot copies on the destination volume that
are newer than the common Snapshot copy on the source volume. Finally, the command mounts the
destination volume as a data protection volume, retaining the common Snapshot copy.
Next, Data ONTAP snapmirror resync creates a Snapshot copy of the source volume and calculates to
determine what data is newer than the common Snapshot copy. The source transfers newer data to the
destination volume.
With these actions, the original SnapMirror relationship is reestablished, and the test data that was written to
the destination volume is gone.

Disaster Mode
Source Unavailable
Disaster strikes.
Source Destination
SnapMirror
SVM1 SVM2
Clients cannot
src_vol read or write data
to source volume.
dst_vol
Clients
DISASTER MODE: SOURCE UNAVAILABLE

Disaster strikes. For this example, assume that a backhoe dug up the network cables that connect the data
center to clients. The data center volume (src_vol) is unavailable.

Disaster Mode
Clients Fail Over to Destination
Break the SnapMirror relationship and direct clients to the

destination volume.
snapmirror break -source-path svm1:src_vol
Source Destination
(Writable)
SnapMirror
Command is
SVM1 SVM2 run here
Clients read and
write data to the
src_vol destination dst_vol
volume
Clients
DISASTER MODE: CLIENTS FAIL OVER TO DESTINATION

From the destination node, you break the SnapMirror relationship. When the SnapMirror relationship is
broken, SnapMirror updates are interrupted, and the SnapMirror replica becomes writable. Then you direct
clients to the writable destination volume (dst_vol), and clients continue reading and writing their data.
Because the source volume is offline, its data is becoming out of date. However, the most recent shared
Snapshot copy is preserved, ready, and waiting for the reestablishment of the SnapMirror relationship.

Resumption of Normal Operations: Part 1
Write New Data from Destination to Source
To update the source from the destination, run the snapmirror

resync command from the original source SVM.
snapmirror resync -source-path svm1:src_vol
Updates
SnapMirror Source
(Original) (Writable)
Source Destination
Command is SnapMirror
run here SVM1 Resync SVM2
Clients read and
src_vol
write data to the
dr_vol
destination dst_vol
Clients volume.
RESUMPTION OF NORMAL OPERATIONS: PART 1: WRITE NEW DATA FROM

DESTINATION TO SOURCE
To return from failover mode back to normal mode, you first need to capture the data that was written to the
destination volume while the source volume was offline. To update the original source volume with the new
data that was written to the destination volume, you run the snapmirror resync command from the
original source SVM. In effect, the resync command, run from the source, reverses the direction of the
SnapMirror relationship.
When you use OnCommand System Manager to manage SnapMirror, you use the Reverse Resync tool. Until
the source volume is updated with the data that was written to the destination, the original destination
becomes the source. To update the source when you use the CLI, ensure that you run the snapmirror
resync command from the original source. Data written to the destination is reverse synchronized to the
original source.
Before you run the snapmirror resync command, check the size of the secondary volume compared to
the primary volume. It is possible that, when the primary volume was offline, the automatic resizing feature or
the administrator increased the size of the secondary volume. The secondary volume could have become
larger than the primary volume.
Increase the size of the primary volume if necessary. You might need to turn off the fs_size_fixed
volume option to change the size of the data center volume.

Breaking the Temporary Mirror Relationship
To reverse the direction of the SnapMirror relationship, break

the SnapMirror relationship from the source system.
snapmirror break svm1:src_vol
(Original)
Source Destination
Command is
run here
SVM1 SVM2
Clients read and
write data to the
src_vol destination dr_vol
dst_vol
volume.
Clients
RESUMPTION OF NORMAL OPERATIONS: PART 2: BREAKING THE TEMPORARY

MIRROR RELATIONSHIP
After the snapmirror resync command has been run from the original source SVM (src_vol), the
SnapMirror relationship is updated with the production data that was written in disaster mode, when clients
were writing to the destination volume. In this temporary, reversed SnapMirror relationship, the original
source is now the destination and the original destination is the source.
To reverse the temporary relationship, you must break the temporary relationship from the temporary
destination. Run the snapmirror break command from the original source. The syntax of the
snapmirror break command is:
destination>snapmirror break destination_vol
In this slide, the temporary SnapMirror relationship is now broken; however, clients are not yet writing to the
original source volume.

Resynchronize the SnapMirror relationship and redirect users

to the original source volume.
snapmirror resync source-path svm2:dst_vol
Source Destination
dc>
Command is
run here
Writing Data Clients can again

dc_vol
src_vol read or write data dst_vol
to source volume.
Clients
RESUMPTION OF NORMAL OPERATIONS: PART 3

The final step to resuming normal operations is to run the snapmirror resync command from the
disaster recovery site. The syntax of the snapmirror resync command is:
destination>snapmirror resync destination_vol
This final snapmirror resync command that is run from the disaster recovery site returns SnapMirror to
the original source and destination relationship.
You can now redirect users to the original source volume to continue writing their data.

SnapMirror Management Interfaces
You have several management interfaces to select from to

configure SnapMirror replication:
Data ONTAP cluster CLI
NetApp OnCommand System Manager
NetApp OnCommand Unified Manager
NetApp SnapManager suite of management products
NetApp SnapProtect
SNAPMIRROR MANAGEMENT INTERFACES

You have several management interfaces to choose from to configure SnapMirror replication:
From the storage system command line of the source and destination storage systems, you can manage
SnapMirror relationships. Relationships that belong to each destination storage system are managed
individually and separately.
From the NetApp OnCommand System Manager interface, you can add many storage systems into the
interface, set up SnapMirror relationships, and centrally manage SnapMirror replications.
From the NetApp OnCommand Unified Manager, protection capabilities, you access the NetApp
Management Console and use protection and provisioning policies to manage SnapMirror relationships.
From the SnapProtect central-control UI called the CommServe, you can use storage policies to manage
SnapMirror relationships. In the Implementing SnapProtect Solution three-day instructor-led course,
you practice installing SnapProtect, configuring SnapProtect data agents on application server hosts, and
configuring SnapMirror replication from Data ONTAP primary to secondary storage.
Symantec Plug-in for Data ONTAP interoperates with Symantec NetBackup software and clustered and
7-Mode Data ONTAP. From the Symantec NetBackup interface, you can manage Data ONTAP data
protection and data recovery operations, including SnapMirror replication, even without extensive
training in the operation of NetApp Data ONTAP.
In the hands-on exercise of this module, you use the storage system CLI and the OnCommand System
Manager interface to configure SnapMirror replications.

ACTION: Exercise

exercise
equipment.
Open your
credentials
provided Turn to: Complete the
instructor. Part 2.
Stop at the
end of Q&A
Exercise 5.
ACTION: EXERCISE

How can you monitor the health of the

source volumes?
After failing over to the SnapMirror
destination volume, what are the steps
for restoring the SnapMirror
relationship without losing data?
From which SVM do you always run a
snapmirror resync command?

BASED EXERCISE

Lesson 3
SnapMirror Administration
Topics
LESSON 3: SNAPMIRROR ADMINISTRATION TOPICS

SnapMirror Administration Topics
Breakout Session
The following administration topics are the subjects of our

breakout session:
SnapMirror and FlexClone volume clones
Intercluster SnapMirror throttle
Network compression
SnapMirror load-sharing mirrors
Version-independent SnapMirror
SNAPMIRROR ADMINISTRATION TOPICS: BREAKOUT SESSION

The following administration topics are outlined in the next few pages. After you hear a brief introduction to
the breakout session topics, you go into a breakout session. Upload the breakout session question for your
group, discuss the answer, choose a spokesperson, and then present your answer in class. The administration
topics are as follows:
SnapMirror and FlexClone volume clones
Intercluster SnapMirror throttle
Network compression
SnapMirror load-sharing mirrors
Version-independent SnapMirror

SnapMirror and FlexClone Technology
1. Create an unscheduled
Snapshot copy at the
source.
FlexClone
Volume
Snapshot
Copies
3. Use the unscheduled Snapshot copy

2. To copy the unscheduled as the base for the FlexClone volume.
Snapshot copy to the destination,
perform a SnapMirror update.
SNAPMIRROR AND FLEXCLONE TECHNOLOGY

With NetApp FlexClone volume clone functionality, you can create a writable point-in-time clone of a
FlexVol volume. A FlexClone volume clone shares all data blocks with the parent volume and stores only
new data or changes that are made to the clone.
FlexClone technology works well with SnapMirror replications to enable you to create writable volumes,
using the read-only SnapMirror destination volumes as the source. With FlexClone technology, you can
create a copy of a production volume without interrupting production operations.
If you use one of the scheduled SnapMirror Snapshot copies to create a FlexClone volume clone, you can
disrupt the SnapMirror replication process. To create a FlexClone volume clone of a SnapMirror destination
volume without interrupting the SnapMirror replication schedule, follow these steps:
1. On the source volume, create an unscheduled Snapshot copy.
2. On the destination volume, perform a SnapMirror update to copy the unscheduled Snapshot copy to the
destination volume.
3. On the destination volume, use the unscheduled Snapshot copy as the base for the FlexClone volume
clone.
The FlexClone volume clone has all of the properties of a normal, writable volume.

Intercluster SnapMirror Throttle
To limit the amount of bandwidth that is used by intercluster

SnapMirror transfers, apply a throttle to intercluster SnapMirror
relationships.
Network Bandwidth
SnapMirror Throttle
INTERCLUSTER SNAPMIRROR THROTTLE

To limit the amount of bandwidth that is used by intercluster SnapMirror transfers, apply a throttle to
intercluster SnapMirror relationships.
After you create a relationship, you can use the CLI to set a throttle. Use the snapmirror modify
command with the throttle option and a value in kilobytes.
NetApp OnCommand System Manager 3.0 does not currently support SnapMirror throttle
management.
In the following example, a 10-MB throttle is applied to an existing relationship by using the snapmirror
modify command:
cluster02::> snapmirror modify -destination-path cluster02://vs1/vol1
throttle 10240
To change the throttle of an active SnapMirror relationship, terminate the existing transfer, and then restart it
to use the new value. The SnapMirror feature restarts the transfer from the most recent restart checkpoint by
using the new throttle value, rather than restarting from the beginning.
Starting with clustered Data ONTAP 8.2.1, both intracluster throttle and intercluster throttle are supported,
and both are configured with the throttle variable.

SnapMirror Network Compression
SnapMirror network compression enables data compression

over the network for SnapMirror transfers.
SnapMirror
transfer
Read Write
Compressed
data across
the network
You can enable or disable SnapMirror network compression by

using the -is-network-compression-enabled option in
the SnapMirror policy.
SNAPMIRROR NETWORK COMPRESSION

SnapMirror network compression enables data compression over the network for SnapMirror transfers. It is a
Data ONTAP feature that is built into the SnapMirror software. SnapMirror network compression is not the
same as volume compression. With SnapMirror network compression, data is not compressed on the source
or destination system SVMs. The data blocks that need to be sent to the destination system are handed off to
the compression engine, which compresses the data blocks.
The compression engine on the source system creates several threads, depending on the number of CPUs
available on the storage system. These compression threads help to compress data in a parallel fashion. The
compressed blocks are then sent over the network.
On the destination system, the compressed blocks are received over the network and are then decompressed.
The destination compression engine also has several threads to decompress the data in a parallel fashion. The
decompressed data is reordered and is saved to the disk on the appropriate volume.
In other words, when SnapMirror network compression is enabled, two additional steps are performed:
Compression processing occurs on the source system before data is sent over the network.
Decompression processing occurs on the destination system before the data is written to the SnapMirror
destination.
You can enable or disable the SnapMirror network compression by using the -is-network-
compression-enabled option in the SnapMirror policy.

SnapMirror Load-Sharing Relationships
Introduction to Load-Sharing Mirror Relationships
SnapMirror load-sharing mirror copies can support only NAS

(CIFS and NFSv3).
Load-sharing mirror copies do not support NFSv4 clients or
SAN client protocol connections (FC, FCoE, or iSCSI).
Source Destination
Clients Load-Sharing SnapMirror Clients
SNAPMIRROR LOAD-SHARING MIRROR RELATIONSHIPS: INTRODUCTION TO

LOAD-SHARING MIRROR RELATIONSHIPS
How should you deploy load-sharing mirror relationships?
SnapMirror load-sharing mirror copies increase performance and availability for NAS clients. Load-sharing
mirrors distribute an SVM namespace root volume to other nodes in the same cluster. By distributing data
volumes to other nodes in the cluster, performance for large read-only workloads is improved.
NOTE: SnapMirror load-sharing mirror copies support only NAS (CIFS and NFSv3). Load-sharing mirror
copies do not support NFSv4 clients or SAN client protocol connections (FC, FCoE, or iSCSI). Data ONTAP
routes NFSv4 clients to the source of the load-sharing mirror for direct read and write access.

Implementing Load-Sharing Relationships
Create the Load-Sharing Mirror Destination Volumes
Two volumes, which are named svm1_root_lsm1 and

svm1_root_lsm2, are created as load-sharing mirror destination
volumes for the SVM root volume named svm1_root:
cluster1::> volume create -vserver svm1 volume
svm1_root_lsm1 -aggregate n1_aggr1 -size 20m type DP
cluster1::> volume create -vserver svm1 volume

svm1_root_lsm2 -aggregate n2_aggr1 -size 20m type DP
IMPLEMENTING LOAD-SHARING RELATIONSHIPS: CREATE THE LOAD-SHARING

MIRROR DESTINATION VOLUMES
You can manage load-sharing mirror relationships only in the Data ONTAP CLI. Currently, you cannot
manage load-sharing mirror relationships by using OnCommand System Manager.
A group of load-sharing mirror destination volumes that copy from the same source volume is called a
load-sharing mirror set.
When a load-sharing mirror set is created, each destination volume must be created in the appropriate
aggregate, which creates the destination volumes with a type of data protection.
In this example, two volumes named svm1_root_lsm1 and svm1_root_lsm2 are created as load-sharing mirror
destination volumes for the SVM root volume named svm1_root:
cluster1::> volume create -vserver svm1 -volume svm1_root_lsm1 -aggregate
n1_aggr1 -size 20m -type DP
cluster1::> volume create -vserver svm1 -volume svm1_root_lsm2 -aggregate
n1_aggr1 -size 20m -type DP

Create the Load-Sharing SnapMirror Relationships
A load-sharing SnapMirror relationship is created for each of

the destination volumes, vs1_ls_a and vs1_ls_b, with an hourly
update schedule:
cluster1::> snapmirror create -source-path
svm1:svm1_root -destination-path
svm1:svm1_root_lsm1 -type LS -schedule hourly
cluster1::> snapmirror create -source-path

svm1:svm1_root -destination-path
svm1:svm1_root_lsm2 -type LS -schedule hourly
IMPLEMENTING LOAD-SHARING RELATIONSHIPS: CREATE THE LOAD-SHARING

SNAPMIRROR RELATIONSHIPS
After all load-sharing mirror destination volumes are created, each SnapMirror relationship can be created
with a type of LS. In this example, a load-sharing SnapMirror relationship is created for each of the
destination volumes, vs1_ls_a and vs1_ls_b, with an hourly update schedule.
cluster1::> snapmirror create -source-path svm1:svm1_root -destination-
path svm1:svm1_root_lsm1 -type LS -schedule hourly
[Job 117] Job is queued: snapmirror create for the relationship with
destination[Job 117] Job succeeded: SnapMirror: done
cluster1::> snapmirror create -source-path svm1:svm1_root -destination-
path svm1:svm1_root_lsm2 -type LS -schedule hourly
[Job 119] Job is queued: snapmirror create for the relationship with
destination[Job 119] Job succeeded: SnapMirror: done

Initialize the Load-Sharing SnapMirror Relationship
Initialize the load-sharing SnapMirror relationship:

cluster1::> snapmirror initialize-ls-set -source-
path cluster1://svm1/svm1_root
All destination volumes are initialized simultaneously.
Verify that the initialization was performed:

Check the LS SnapMirror relationship:

cluster1::> snapmirror show -type LS
IMPLEMENTING LOAD-SHARING RELATIONSHIPS: INITIALIZE THE LOAD-SHARING

SNAPMIRROR RELATIONSHIP
You can update load-sharing mirror relationships manually or by setting the desired schedule in the
schedule option. For load-sharing mirror relationships, you set the desired schedule on any one of the
destinations in the load-sharing mirror set. Data ONTAP automatically applies that schedule to all
destinations in that load-sharing mirror set.
A later change to the update schedule for any of the destination volumes in the load-sharing mirror set
applies the new schedule to all volumes in that load-sharing mirror set. Therefore, in the previous
example, the
schedule option was used only in the creation of the most recent relationship, which applied the
schedule to both relationships.
Initialize the LS SnapMirror relationship:
cluster1::> snapmirror initialize-ls-set -source-path cluster1://svm1/svm1_root
[Job 120] Job is queued: snapmirror initialize-ls-set for source
"cluster1://svm1/svm1_root".

Verify that the initialization was performed:
Progress
Source Destination Mirror Relationship Total
Last
Path Type Path State Status Progress Healthy
Updated
----------- ---- ------------ ------- -------------- --------- -------
cluster1://svm1/svm1_root
LS cluster1://svm1/svm1_root_lsm1
Snapmirrored
false - Transferring 696KB
cluster1://svm1/svm1_root_lsm2
Snapmirrored Transferring 696KB
The initialize process is still transferring data.

Progress
Last
Updated
----- ------- ----- ------- ------------ -------- -------
Snapmirrored Idle -
true -
Snapmirrored
true -
Idle -
You can update load-sharing mirror relationships on demand by using the snapmirror update-ls-set
command. Data ONTAP updates all destination volumes for the LS set in one operation.
cluster1::> snapmirror update-ls-set -source-path svm1:svm1_root
[Job 121] Job is queued: snapmirror update-ls-set for source "cluster1://svm1/svm1_root".

Failover Load-Sharing Relationships
Update the Load-Sharing Mirror Before You Run the snapmirror promote
Command
Manually update the load-sharing mirror relationship
cluster1::> snapmirror update-ls-set -source-path
svm1:svm1_root
Promote the LS destination volume:

cluster1::> snapmirror promote -destination-path
Verify that the volume is online and writable:

cluster1::> volume show -volume svm1_root_lsm2
Notice that the svm1_root_lsm2 volume

is now read/write.
FAIL OVER LOAD-SHARING RELATIONSHIPS: UPDATE THE LOAD-SHARING

MIRROR BEFORE YOU RUN THE SNAPMIRROR PROMOTE COMMAND
If the SVM root volume of a load-sharing mirror becomes unavailable, you can promote one of the load-
sharing mirrored volumes to a writable volume. The promote operation also deletes the original source
volume, and the specific SnapMirror relationship for the promoted destination volume is removed. You can
then rename the promoted volume to take the place of the original source volume.
Check the LS SnapMirror relationship:
cluster1::> snapmirror show -type ls
Progress
Last
Updated
----------- ---- ----------- ------- -------------- --------- --
Snapmirrored
Idle -
true -
Snapmirrored
Idle -
true -

Promote the LS destination volume:
cluster1::> snapmirror promote -destination-path
Warning: Promote deletes the read-write volume cluster1://svm1/svm1_root
and replace it with cluster1://svm1/svm1_root_lsm2.
[Job 122] Job is queued: snapmirror promote of destination
"cluster1://svm1/svm1[Job 122] Job succeeded: SnapMirror: done
Verify that the volume is online and writable:

cluster1::> volume show -volume svm1_root_lsm2
Vserver Volume Aggregate State Type Size Available Used%
--------- ------------ ------------ ------- ---- ----- -------- ---
svm1 svm1_root_lsm2
n1_aggr1 online RW 20MB 18.85MB 5%
The svm1_root_lsm2 volume is now read/write.
The destination volume that is the target of the promote command is now the source volume for the load-
sharing mirror set, and no NFS file manages and CIFS connections are interrupted.
Remember that load-sharing mirror volumes are read-only and that all client access requests are directed
only to destination volumes. Thus, no read-only connections to the source volume that were removed by
the promote operation exist, except for connections that might access the read/write admin share.
NFS file manages and CIFS connections to the read/write admin share are nondisruptively transferred to
the new source volume.
Read-only connections to the promoted volume are nondisruptively transferred to other destination
volumes in the load-sharing mirror set.

Failover Load-Sharing Relationships
Rename the Source Volume
The snapmirror show command shows the change in the

list of load-sharing mirrors. Notice that the promote operation
has deleted the original source volume and replaced it with
the load-sharing volume:
cluster1::> snapmirror show -type LS
To retain the name for the source load-sharing mirror set to

the original source volume name, rename the volume:
cluster1::> volume rename -vserver svm1 -volume
svm1_root_lsm2 -newname svm1_root
FAIL OVER LOAD-SHARING RELATIONSHIPS: RENAME THE SOURCE VOLUME

The promote operation also deletes the original source volume, and the specific SnapMirror relationship for
the promoted destination volume is removed.
Progress
Last
Updated
----------- ---- ------------ ------- -------------- --------- -------
Snapmirrored
Idle -
true -
Because the promoted volume would have had a different volume name than the original source volume, the
new source volume can be renamed. To retain the original name for the source of the load-sharing mirror,
configure the load-sharing volume, as shown in the following example.

To retain the name for the source load-sharing mirror set, rename the volume:
cluster1::> volume rename -vserver svm1 -volume svm1_root_lsm2 -newname
svm1_root
[Job 123] Job succeeded: Successful
The source volume has changed for the svm1_root_lsm1 volume.
Best practice: The promote operation deletes the original source volume; therefore, you might need to create
another load-sharing mirror destination volume on the node where the current source volume was located.

Version-Independent SnapMirror
Upgrade Without Disruption
You can upgrade to future

Data ONTAP versions
Data ONTAP 8.3 without disruption.
Source Destination
Version-Independent SnapMirror Relationship
VERSION-INDEPENDENT SNAPMIRROR: UPGRADE WITHOUT DISRUPTION

In earlier versions of Data ONTAP, the destination controller required the same version or a later version of
Data ONTAP as the source controller. Because of this limitation, you would have to upgrade your SnapMirror
destination before upgrading your SnapMirror source. If you had a complex or bidirectional replication
topology, you might have been required to take a disruption at upgrade time.
Beginning with Data ONTAP 8.3, you can upgrade without disruption. Data ONTAP 8.3 introduces a new
type of SnapMirror relationship that is no longer tied to the Data ONTAP version. Now, even with complex
replication topologies, you can perform nondisruptive upgrades without having to do the upgrades
concurrently across source and destination, and without having to resynchronize the relationship.
Before you create version-independent SnapMirror relationships, there are guidelines to consider.

Workloads for Version-Independent SnapMirror
High-file count
Mid-file and low-file count Mid-file and low-file count
(more than 10 million files)
(less than 10 million files) (less than 10 million files)
Recovery point objective
RPO of less than RPO of more than
(RPO) of more than two
two hours two hours
hours
Bidirectional Topologies
Single-Copy Disaster Recovery
Single-Copy Backup and

Restore
(Default Behavior) (Version-Independent
Feature)
WORKLOADS FOR VERSION-INDEPENDENT SNAPMIRROR

Version-independent SnapMirror brings the ability to upgrade to future versions of Data ONTAP without
disruption. However, the performance requirements make this type of SnapMirror relationship more suitable
in some situations than others.
The default, version-dependent SnapMirror relationships are suitable for a wide range of workloads and
recovery point objective (RPO) requirements. Performance might be inadequate if version-independent
relationships are used for high-count, small-file workloads or if an RPO of less than two hours is required.
For mid-file-count to low-file-count workloads with an RPO of more than two hours, either the default
SnapMirror relationships or the version-independent SnapMirror relationships are suitable.
Use version-independent relationships if bidirectional topologies exist or if single-copy disaster recovery or
backup and restore is desired.

ACTION: Breakout Session
Self-Directed Learning in Smaller Groups
Instructor starts Breakout. Duration: 30 minutes

Click Yes. Students collaborate.
Discuss and answer Instructor leads debrief.

the question.
Save answers on the Students share
whiteboard. whiteboard content.
Select a
Click Yes. spokesperson.
To share content, check the box.
ACTION: BREAKOUT SESSION: SELF-DIRECTED LEARNING IN SMALLER GROUPS

For a change of pace, instead of a lecture, you can discover the details of SnapMirror administration in a
breakout session. Join a group, read about your topic in Module 5, discuss the details in your group, select a
spokesperson, and then report your findings to the class.

ACTION: Answer Group 1 Question
Read, Discuss, and Answer the Question
Scenario: Testing Testing

How can you test your SnapMirror implementation without
taking your production volume offline?
ACTION: ANSWER GROUP 1 QUESTION: READ, DISCUSS, AND ANSWER THE

QUESTION
In your breakout group, read, discuss, and then answer the question.

Topic 2: Bandwidth Blues

SnapMirror transfers that occur during peak times might affect
performance. What can you do to prevent bandwidth issues?

QUESTION

Topic 3: Compressed
What are the two types of compression used in SnapMirror
implementations and how do they work?

QUESTION

Topic 4: Performance and Availability

What type of mirror copies increase performance and data
availability and how does this type of SnapMirror copy work?

QUESTION

Topic 5: Version-Independent SnapMirror Relationships

In what scenarios would you choose to implement the default
SnapMirror relationships or version-independent relationships?

QUESTION

I now understand how to

design and implement a
SnapMirror solution. Even
more importantly, I now
understand how to recover
my data by using SnapMirror
software in case there is a
disaster.

References

SnapMirror Planning and Implementation
SnapMirror Disaster Recovery
NetApp Documentation:
TR-4015: SnapMirror Configuration Best Practices Guide
for Clustered Data ONTAP
REFERENCES

Module 6
SnapVault Backup and Recovery
MODULE 6: SNAPVAULT BACKUP AND RECOVERY
6-1 Data ONTAP Data Protection Administration: SnapVault Backup and Recovery

Module Objectives

Create, schedule, and monitor SnapVault replication
Manage SnapVault backup and restore operations
Use SnapVault software to recover data
Create clustered Data ONTAP SnapMirror and SnapVault
relationships
Monitor and manage SnapVault and SnapMirror relationships
MODULE OBJECTIVES

Lesson 1
Implementing a SnapVault
Solution
LESSON 1: IMPLEMENTING A SNAPVAULT SOLUTION

Components of the SnapVault Solution
SnapVault Relationship, Snapshot Copy Policies, and the SnapMirror Label
A SnapVault policy is the component of the SnapVault

relationship that determines schedule and retention rules.
Primary SnapVault Secondary

Relationship
Vol1 SnapVault Vol1_2

Policy
-SnapMirror
Label nightly
COMPONENTS OF THE SNAPVAULT SOLUTION: SNAPVAULT RELATIONSHIP,

SNAPSHOT COPY POLICIES, AND THE SNAPMIRROR LABEL
In this lesson, you learn how to create, schedule, and monitor SnapVault replication.
A SnapVault configuration is controlled from the SnapVault secondary storage virtual machine (SVM). The
SnapVault configuration components on the secondary SVM consist of:
A SnapVault relationship that specifies the primary and secondary volumes
A SnapVault policy that specifies the retention rules
A SnapMirror label that specifies the update schedule
You can configure a SnapVault solution by creating a SnapVault relationship and then assigning the default
SnapVault policy with the default retention rules and SnapMirror label.

SnapVault Relationship, Snapshot Copy Policies, and the SnapMirror Label
The SnapVault policy is the component of the SnapVault


Relationship
Vol1 Snapshot Vol1_2

SnapVault
Copy
Policy
Policy
-SnapMirror -SnapMirror
Label nightly Label nightly

The SnapMirror label specified in the SnapVault policy on the secondary SVM matches the SnapMirror label
configured in the Snapshot copies on the primary SVM.
The matching SnapMirror label identifies the Snapshot copy to transfer to the secondary SVM.

SnapVault Relationship, Snapshot copy Policies, and the SnapMirror Label
The SnapVault policy is the component of the SnapVault


Relationship
Vol1 Snapshot Vol1_2

SnapVault
Copy
Policy
Policy
Label nightly Label nightly
SnapVault Updates Based on SnapMirror Label

Default SnapMirror labels are weekly, nightly, and hourly, with set schedule and retention rules that
apply. The SnapVault policy specifies the weekly, nightly, or hourly SnapMirror label and sets the schedule
and retention rules for SnapVault updates.
You can customize the SnapVault backup intervals by creating a customized Snapshot copy policy, or a
customized schedule, or a customized SnapVault label.

Steps to Implement SnapVault Backups
1. Verify 2. Create 3. Create a 4. Initiate

required secondary SnapVault baseline
settings volume relationship transfer
STEPS TO IMPLEMENT SNAPVAULT BACKUPS

If you are using the CLI to implement the SnapVault solution, follow these steps:
1. To ensure that the required preconfigurations are performed, create a checklist.
2. Create a secondary volume.
3. Create a SnapVault relationship.
4. Initiate the baseline transfer.

Ken Asks
How do I create a SnapVault

relationship in the CLI?
KEN ASKS

1. SnapVault Preconfiguration Checklist
Planning a SnapVault Deployment
Verify that the following preconfigurations are set correctly:

Install SnapVault license codes.
Verify that language setting requirements are met.
Verify that firewall settings permit SnapVault transfers.
Verify that cluster and SVM peer relationships are healthy.
Identify the primary volumes and estimate the amount of time
required to complete the baseline transfer.
Verify that the Snapshot copy policy on the primary volume
has the snapmirror-label attribute.
1. SNAPVAULT PRECONFIGURATION CHECKLIST: PLANNING A SNAPVAULT

DEPLOYMENT
Before you begin to implement your SnapVault backups, make a checklist of that the required
preconfigurations and then verify that preconfigurations are set correctly.
Careful planning is also recommended. Plan which primary volumes you are protecting and what SnapVault
topography you are deploying. The amount of data and network congestion make it necessary to plan for the
amount of time required to complete the baseline transfer.

Preconfigure Required License Codes
License Primary and Secondary SVMs
To verify that the required license codes are installed, use the
following command.
cluster1::> system license show
Owner: cluster1-01
Package Type Description
Expiration
----------------- ------- -----------------
SnapMirror license SnapMirror
SnapVault license SnapVault
SnapRestore license SnapRestore
FlexClone license FlexClone
PRECONFIGURE REQUIRED LICENSE CODES: LICENSE PRIMARY AND

SECONDARY SVMS
The SnapVault solution requires license codes for SnapMirror, SnapVault, SnapRestore, and FlexClone
software. SnapMirror software is required because SnapVault software is a type of SnapMirror replication.
SnapRestore and FlexClone software are required for restore operations.
The following command displays the license codes that are installed on the cluster:
cluster1::> system license show
These licenses must be installed on both primary and secondary clusters for intracluster and intercluster
SnapVault relationships. Other required licenses include NFS, CIFS, iSCSI, and FC licenses for NAS clients
and SAN clients.

Language Setting Requirement
Primary and Secondary Volumes Must Match
The primary and secondary volumes of a SnapMirror or

SnapVault relationship must have the same language setting.
Command to verify the language setting on a volume:
volume show -fields language
Command to verify the default language setting on the SVMs:
vserver show -fields language
LANGUAGE SETTING REQUIREMENT: PRIMARY AND SECONDARY VOLUMES

MUST MATCH
For SnapMirror and SnapVault relationships, the primary and secondary volumes must have the same
language setting. If volume languages are not matched, the NFS or CIFS clients might not be able to access
data.
Language is a volume setting; however, you can set the default language at the SVM level. You should verify
that the default language setting for the primary and secondary SVM is set to the UTF-8 language.

Firewall Requirements
For Intercluster SnapMirror and SnapVault Relationships
Firewalls and the intercluster

firewall policy must permit the
following:
ICMP and HTTPS services
Port 10000 for NDMP
Ports 11104 and 11105
for SnapMirror and SnapVault
Command to show firewall
settings:
system services firewall policy show
FIREWALL REQUIREMENTS: FOR INTERCLUSTER SNAPMIRROR AND SNAPVAULT

RELATIONSHIPS
For intercluster SnapMirror and SnapVault relationships, verify that firewalls and the intercluster firewall
policy allow ICMP service, HTTPS, and TCP ports 10000, 11104, and 11105. Before you attempt to
configure cluster peering or intercluster SnapMirror and SnapVault relationships, set TCP to the IP addresses
of all of the intercluster logical interfaces (LIFs) over all of the required ports.
Port 10000 is the well-known port for NDMP, the backup protocol. SnapMirror relationships use port 11104
and port 11105 on the intercluster network to copy data from their primary volumes to their secondary
volumes. Clustered Data ONTAP uses port 11104 to manage intercluster communication sessions and uses
port 11105 to transfer data.
The default intercluster firewall policy allows access through the HTTPS protocol and from all IP addresses
(0.0.0.0/0), but the policy can be altered or replaced.

Peer Relationship Requirement
Intracluster and Intercluster Peering Configuration
For intracluster relationships, SVM peering is required.

cluster1::> vserver peer create -vserver cluster1-svm1
-peer-vserver cluster1-svm2 applications snapmirror
For intercluster relationships, cluster peering and SVM

peering are both required.
cluster1::> cluster peer create peer-addrs
cluster2,10.98.234.246 username admin
Remote Password: Netapp123
cluster1::> vserver peer create -vserver cluster1-svm1

-peer-vserver cluster2-svm3 -applications snapmirror
-peer-cluster cluster2
PEER RELATIONSHIP REQUIREMENT: INTRACLUSTER AND INTERCLUSTER

PEERING CONFIGURATION
Like SnapMirror, cluster and SVM peering are required. In fact, because SnapMirror is a type of SnapVault
solution, the only application that you can specify is the SnapMirror application. Create a peer SVM on
cluster2.

Planning Space Requirements
Estimate SnapVault Primary Data and Secondary Space Requirements
On the SnapVault secondary system, plan the space required

for your backup plans:
Size of the primary volume
Rate of increase of the data on the primary volume
Number of Snapshot copies to be retained on the secondary
volume
12 hourly Snapshot copies
Secondary 8 daily Snapshot copies
Primary 8 weekly Snapshot copies
PLANNING SPACE REQUIREMENTS: ESTIMATE SNAPVAULT PRIMARY DATA AND

SECONDARY SPACE REQUIREMENTS
To avoid the inconvenience of running out of disk space, be sure to calculate the amount of disk space you
need on the SnapVault secondary system. Consider the following factors as you plan the space required for
your backups:
Size of the primary volume
Rate of increase of the data on the primary volume
Number of Snapshot copies to be retained on the secondary volume
NetApp offers sizing guides for the major application servers that you can use to calculate disk space.

The Snapshot Copy Policy
Requirements
Must have the snapmirror-label attribute enabled.
Must match the snapmirror-label attribute in the

SnapVault policy.
Must decide whether to use a preconfigured Snapshot copy

policy or to create a policy.
THE SNAPSHOT COPY POLICY: REQUIREMENTS

The Snapshot copy policy sets the Snapshot schedule for volumes. For SnapVault updates, the default
SnapVault policy uses the daily and weekly snapmirror-label attribute specified by the default
Snapshot copy policy. You can use the preconfigured Snapshot copy policy or, if you need a different
schedule, you can create a Snapshot copy policy.
If you create a Snapshot copy policy, you must modify the snapmirror-label attribute to match the
snapmirror-label attribute in the SnapVault policy.

Verifying the Snapshot Copy Policy
Check for the SnapMirror Label Attribute on the Primary SVM
Command to determine if a Snapshot copy policy has the

snapmirror-label attribute:
The default-1weekly
policy does not have
a SnapMirror label.
VERIFYING THE SNAPSHOT COPY POLICY: CHECK FOR THE SNAPMIRROR LABEL
ATTRIBUTE ON THE PRIMARY SVM
The Snapshot copy policy controls the Snapshot copy schedule and retention rules for all volumes. For
SnapVault relationships, the Snapshot copy policy on the primary volume should have the snapmirror-
label attribute. The snapmirror-label attribute controls the SnapVault update schedule and the
retention rules for the primary and secondary volumes.
As a prerequisite check, verify that the Snapshot copy policies on the primary volume are using the
snapmirror-label attribute. If your Data ONTAP cluster has been upgraded several times, you might
have to modify the Snapshot copy policy by adding the snapmirror-label attribute.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick quiz on the preconfigurations for the SnapVault solution.

Poll Questions
a. Which two statements about SnapVault policies are true?

(Choose two.)
a. The SnapVault policy determines the schedule and retention rules.
b. Snapshot copies for SnapVault updates must match the SnapMirror label name.
c. SnapVault updates are initiated by the SnapVault primary SVM.
d. You can modify the default SnapMirror labels (weekly, nightly, and hourly).
b. Which statement about SnapVault requirements is true?

a. You only need to verify that SnapVault is licensed.
b. You need to verify licensing, language, firewall, peering, snapmirror-label
attribute, and storage capacities for the primary and secondary SVMs.
c. You only need to verify that cluster and SVM peering are correct.
d. You need to verify that the SnapVault secondary volume has the snapmirror-
label attribute set.

2. Create a SnapVault Destination Volume
Required Volume Settings
The SnapVault secondary volume must have the following

configurations:
FlexVol volume type: DP
(data protection) Primary Secondary
Sizing management:
automatic resizing
Space efficiency: enabled
Sample command to create a secondary volume:
cluster2::> volume create -vserver svm2 -volume svm2_vol1
-aggregate aggr1 -size 200g -type DP -security-style ntfs
2. CREATE A SNAPVAULT DESTINATION VOLUME: REQUIRED VOLUME SETTINGS

After you verify that the prerequisite configurations are set, you create the SnapVault secondary volume. If
you are using OnCommand System Manager, OnCommand Unified Manager, NetApp SnapProtect, or
another backup management solution, the secondary volume is created automatically. If you are setting up
SnapVault software on the CLI, you create the SnapVault secondary volume manually.
When you create a FlexVol volume and use the -type DP option, the volume is created with settings that
reflect best practices for secondary volumes. The volume settings are different from the default settings used
for read/write (RW) volumes.
Space setting RW volume DP volume
Space guarantee volume volume
autosize false true
autosize-mode off grow_shrink
autosize-growthreshold-
Percent 85 (percent) 85 (percent)
autosize-shrinkthreshold % 50 (percent) 80 (percent; autosize-growthreshold-percent-5)
min-autosize Initial volume size Initial volume size
max-autosize 120% of volume size Maximum aggregate size
Snap reserve 5 (percent) 0 (percent)
fractional-reserve 100 (percent) 0 (percent)

3. Create a SnapVault Relationship
Assign Default SnapVault Policy and Snapshot Copy Schedule
Use the snapmirror create command:

To create a SnapVault relationship (SnapMirror type XDP)
To assign the default SnapVault policy
cluster2::> snapmirror create -source-path svm1:svm1_vol1

-destination-path svm1_2:svm2_vol1 -type XDP
-policy XDPDefault
SnapVault type of
The default SnapMirror relationship
SnapVault policy
3. CREATE A SNAPVAULT RELATIONSHIP: ASSIGN DEFAULT SNAPVAULT POLICY

AND SNAPSHOT COPY SCHEDULE
On the destination SVM, create a SnapVault relationship and assign an XDP policy by using the
snapmirror create command with the -type XDP parameter and the policy parameter. The
snapmirror create command with the type XDP specified creates the SnapVault relationship
between the primary and secondary volumes.
The source-path specifies the primary SVM and volume.
The -destination-path specifies the secondary SVM and volume.
The -policy XDPDefault specifies the default SnapVault policy.
In the example command, the default SnapVault policy was specified. If no policy is specified, Data ONTAP
automatically selects the default SnapVault policy.
You cannot change the default SnapVault policy; however, you can create your own SnapVault policy.

4. Initiate the Baseline Transfer
Copies Primary Data to Secondary Volume
Command to start the baseline transfer:
cluster2::> snapmirror initialize

destination-path cluster2://svm2/svm2_vol1
Verify the SnapVault status:
4. INITIATE THE BASELINE TRANSFER: COPIES PRIMARY DATA TO SECONDARY

VOLUME
After the SnapVault relationship is created, you must start the baseline transfer by using the snapmirror
initialize command.
The snapmirror initialize command creates a Snapshot copy on the primary volume that is
transferred to the secondary volume. The initial Snapshot copy is used as a baseline for subsequent
incremental Snapshot copies. The command does not transfer any Snapshot copies that currently exist on the
primary volume.
Scheduled updates do not succeed until the SnapVault relationship completes initialization.
You do not have to initialize the SnapVault relationship when you create it. You can initialize the relationship
from the secondary SVM at a time that can better accommodate the baseline transfer.

ACTION: Exercise

exercise
equipment.
Open your
credentials
instructor. Part 1.
Stop after
Task 2. Q&A
ACTION: EXERCISE

Ken Asks
Easy! Create a secondary

volume, create a SnapVault
relationship, and start the
baseline transfer.
But what if I need to modify the

default SnapVault policy?
KEN ASKS

Modifying the SnapVault Policy
SnapVault Policies, Snapshot Policies, SnapMirror Labels, and Cron
Modify the SnapVault policy by creating a SnapVault policy,

creating a Snapshot copy policy, modifying the SnapMirror
label, or adding a cron schedule.

Relationship
vol1 Snapshot svm2_vol1

Cron SnapVault
Copy
Schedule Policy
Policy
Label custom1 Label custom1
MODIFYING THE SNAPVAULT POLICY: SNAPVAULT POLICIES, SNAPSHOT

POLICIES, SNAPMIRROR LABELS, AND CRON
The process of updating a SnapVault relationship follows these steps:
1. The SnapVault policy that is assigned to the SnapVault relationship specifies the primary Snapshot copy
policy and SnapMirror label to use for the SnapVault relationship.
2. The primary Snapshot copy policy has the matching SnapMirror label name that the SnapVault policy has
specified. (Because the SnapVault policy seeks the matching SnapMirror label, these labels must match.)
The example shows a SnapVault relationship that uses the default SnapVault policy named XDPdefault.
The default policy specifies Snapshot copies with the daily and weekly SnapMirror labels. The default
policy keeps seven daily Snapshot copies and 52 weekly Snapshot copies. However, you might want a
different schedule or different retention rules.
You cannot modify the default SnapMirror labels. However, you can modify the Snapshot copy policy on the
primary volume by adding your own SnapMirror label. You cannot modify the default SnapVault policy by
changing the SnapMirror label. Instead, you create your own SnapVault policy. The new SnapVault policy
can specify the SnapMirror labels that you created on the primary Snapshot copy policy. The next three slides
explain how to make the changes.

Modifying SnapVault Policy Rules
SnapVault policy rules set Snapshot copy retention criteria.

Specifies the maximum number of Snapshot copies that are retained
-keep on the SnapMirror vault secondary volume for a rule
Specifies the behavior when the Snapshot copy retention count is

reached on the SnapMirror vault secondary volume. If the number
-preserve specified is reached, the update fails.
The value can be true or false. The default value is false.
Specifies the warning threshold count for the rule.

-warn The default value is 0.
-vserver Specifies the SVM for the SnapMirror policy
-policy Specifies the SnapMirror policy name
MODIFYING SNAPVAULT POLICY RULES

You can use the snapmirror policy modify-rule command to modify the retention count, preserve
setting, and warning threshold count in a SnapMirror policy. The total number of Snapshot copies that are
retained for all the rules in a policy cannot exceed 251. A SnapMirror policy that is associated with a
SnapMirror vault relationship must have at least one rule.
If you reduce the retention count or disable the preserve setting for a rule in a SnapMirror policy, it might
result in the deletion of Snapshot copies on the vault secondary volume. The deletion occurs when the next
transfer snapmirror update occurs.
The keep rule specifies the maximum number of Snapshot copies that are retained on the SnapMirror vault
secondary volume.
The preserve rule specifies the behavior when the Snapshot copy retention count is reached on the
SnapMirror vault secondary volume for the rule. The default value is false. The false value means that,
if the number of Snapshot copies has exceeded the retention count that is specified in the -keep rule, the
oldest Snapshot copy is deleted. When set to true, an incremental SnapMirror vault update fails when the
Snapshot copies reach the retention count.
The warn rule specifies the warning threshold count for the rule. When set to a value greater than zero, an
event is generated after the number of Snapshot copies that are retained on a SnapMirror vault secondary
volume reaches the specified warn limit. The preserve parameter for the rule must be true to set the -warn
parameter to a value greater than zero.
To remove a rule from a SnapMirror policy, run the snapmirror policy remove-rule command
from CLI of the SnapVault secondary cluster. You might need to delete Snapshot copies with a SnapMirror
label that match the rule that is no longer processed by the snapmirror update command.

Modify a SnapVault Policy
The command to modify the policy attributes:

snapmirror policy modify
Attribute Description
-comment Specify a text comment for the policy
-tries Specify the maximum number of times to attempt
each manual or scheduled transfer
-transfer-priority Normal or low. Normal-priority transfers are
scheduled before low-priority transfers.
-ignore-atime True or false. File access time is ignored.
-restart Always, never, or default. By default, transfers
always resume from the restart checkpoint.
MODIFY A SNAPVAULT POLICY

You can use the snapmirror policy modify command to modify policy attributes. For example, use
the comment attribute to enter details about the policy. Other attributes include the maximum number of
times to attempt a failed transfer, the transfer priority, whether to record file access time, or whether to restart
an interrupted transfer.

Modifying a Snapshot Copy Policy
On the Primary SVM
Command to view the SnapMirror label:

cluster1::> volume snapshot policy -policy 2Hour_Policy show
Command to modify a Snapshot copy policy on the primary

SVM to include the snapmirror-label attribute:
cluster1::> volume snapshot policy modify -vserver svm1
-policy 2Hour_Policy -snapmirror-labels SnapVault
The snapmirror-label on the primary SVM must match the SnapVault policy.
Command to verify that the SnapMirror label is correct:

MODIFYING A SNAPSHOT COPY POLICY: ON THE PRIMARY SVM

To determine if a Snapshot copy policy has the snapmirror-label attribute, use the following
command:
To modify the Snapshot copy policy to add the snapmirror-label attribute for SnapVault updates, use
the following command:
cluster1::> volume snapshot policy modify -vserver svm1 -policy
2Hour_Policy -snapmirror-labels SnapVault
To verify that the snapmirror-label attribute is added to the Snapshot copy policy, use the following
command:
The SnapMirror label in the policy must exactly match the snapmirror-label attribute in the SnapVault
policy.

Snapshot Copy Policy and SnapMirror Label
Schedule and Retention Rules
The weekly, nightly, and hourly default SnapMirror labels

contain the following schedules and retention rules:
SnapMirror Primary Snapshot Primary Snapshot Secondary
Label Name Copy Schedule Copies Retained Snapshot Copies
Retained
weekly Every Saturday at 4 8
19:00
nightly Every Monday 10 60
through Friday at
19:00
hourly Every hour from 11 120
07:00 through 18:00
Total Snapshot
copies 25 188
SNAPSHOT COPY POLICY AND SNAPMIRROR LABEL: SCHEDULE AND RETENTION

RULES
This table shows you the three default SnapMirror labels, their schedules, their retention rules, and the
number of Snapshot copies each SnapMirror label accumulates. This table is useful for planning data
protection and space requirements.
If you plan to modify the Snapshot copy policy, first verify that the Snapshot copy policy on the primary
SVM is using the snapmirror-label attribute. If your Data ONTAP cluster has been upgraded several
times, you might have to modify the Snapshot copy policy by adding the snapmirror-label attribute.
If you modify or create a Snapshot copy policy, you must also modify the SnapVault policy. The SnapMirror
label must match the SnapMirror label specified in the Snapshot copy policy.
The next slides step through the commands to create and modify a Snapshot copy policy. The steps include
adding the new SnapMirror label. To modify a SnapVault policy for a revised Snapshot copy policy, you
must identify the new SnapMirror label by using its exact name.

Scheduling Snapshot Copies with Cron
The job schedule cron create Command
If the default Snapshot copy schedule does not meet your

needs, you can create a schedule that does.
Command to view available cron schedules on the cluster:
Command to create a schedule:
cluster2::> job schedule cron create -name

SnapVaultJob -dayofweek all -hour all -minute 10
This job runs every day, every hour, at 10 minutes past the hour.
SCHEDULING SNAPSHOT COPIES WITH CRON: THE JOB SCHEDULE CRON

CREATE COMMAND
You can also use the job schedule cron feature of Data ONTAP clusters to create a Snapshot copy schedule.
Create a Snapshot copy schedule by using the job schedule cron create command or the job
schedule interval create command. The command you use depends on how you want to
implement the schedule.
To review schedules on the cluster to see whether any of them meet your requirements, use the job
schedule show command. To create a schedule that runs every day of the week, every hour of the day, at
10 minutes past the top of the hour, use the following job schedule cron create command:
cluster2::> job schedule cron create -name SnapVaultJob -dayofweek all -
hour all -minute 10
Verify that the new schedule was created correctly:

Name Description
---------------- -----------------------------------------------------
5min @:00,:05,:10,:15,:20,:25,:30,:35,:40,:45,:50,:55
8hour @2:15,10:15,18:15
Hourly_SnapMirror @:03
SnapVaultJob @:10
daily @0:10
hourly @:05
weekly Sun@0:15

Creating a SnapVault Policy
On the Secondary SVM
Command to create a SnapVault policy:

cluster2::> snapmirror policy create -vserver svm2
-policy svm2_vault-policy
Command to add the snapmirror-label attribute:

cluster2::> snapmirror policy add-rule vserver svm2
-policy svm2_vault-policy -snapmirror- label SnapVault
-keep 20
The SnapMirror label matches
Secondary SVM retention is different from primary. the primary SVM.
Command to verify that the SnapMirror label is correct:

cluster2::> snapmirror policy show -vserver svm2
CREATING A SNAPVAULT POLICY: ON THE SECONDARY SVM

SnapVault relationships in the example show that you can use a default policy that is named XDPdefault.
The default SnapVault policy protects Snapshot copies with the daily and weekly SnapMirror labels. The
default policy keeps seven daily Snapshot copies and 52 weekly Snapshot copies.
Depending on how it is defined, a SnapVault policy can be available to a specific SVM or to the entire
cluster. SVM administrators and cluster administrators can configure SVM-wide policies, but only cluster
administrators can configure a cluster-wide policy. For more information, see the Clustered Data ONTAP
Data Protection Guide.
The example in this procedure creates an SVM-wide policy. Create a SnapVault policy by using the
snapmirror policy create command:
cluster2::> snapmirror policy create -vserver svm1_2 -policy
svm1_2_vault-policy

Add the snapmirror-label attribute and Snapshot copy retention:
cluster2::> snapmirror policy add-rule -vserver svm1_2 -policy
svm1_2_vault-policy -snapmirror-label SnapVault-Backup -keep 20
Verify that the SnapMirror label is correct.
cluster2::> snapmirror policy show -vserver svm1_2
SVM Policy Policy Number Transfer
Name Name Type Of Rules Tries Priority Comment
------- ------------ ------ -------- ----- -------- ----------
svm1_2 svm1_2_vault-policy vault 1 8 normal -
SnapMirror Label: SnapVault Keep: 20 Total Keep: 20

Creating a SnapVault Policy
Create the SnapVault Policy Container on the Secondary SVM
Instead of using the default SnapVault policy, you can create

a SnapVault policy.
The SnapVault policy must be created on the secondary
SVM.
Example of the command to create a SnapVault policy:
cluster2::> snapmirror policy create -vserver svm2
-policy svm1-vault-policy
The name of the new

SnapMirror policy for
SnapVault relationships.
CREATING A SNAPVAULT POLICY: CREATE THE SNAPVAULT POLICY CONTAINER

ON THE SECONDARY SVM
The SnapVault policy is a container that is used to define the primary and secondary SnapVault relationship.
You first create a SnapVault policy with the snapmirror policy create command shown here.
Because SnapVault is a type of SnapMirror technology, many SnapMirror commands also apply to SnapVault
software. The example policy is a SnapVault policy for primary volumes on svm1. The name of the new
SnapVault policy is svm1-vault-policy.
You first create the SnapVault policy as a container, and then you modify the policy to add the SnapVault
policy rules.

Adding a SnapVault Policy Rule
The snapmirror-label Attribute
Add the snapmirror-label attribute and a Snapshot copy

retention:
cluster1::> snapmirror policy add-rule vserver svm2
-policy svm1-vault-policy -snapmirror-label SnapVault
-keep 7 -preserve false
Seven Snapshot copies After seven copies, the oldest

are retained on the Snapshot copy is rotated out for
secondary volume. the newest copy.
Verify that the rule is using the correct label:

cluster1::> snapmirror policy show
ADDING A SNAPVAULT POLICY RULE: THE SNAPMIRROR-LABEL ATTRIBUTE

After creating the SnapVault policy, you modify it by adding a rule that specifies a SnapMirror label that
matches the SnapMirror label specified in the Snapshot copy policy of the primary volume.
You also can add the keep option, which specifies how many Snapshot copies to retain on the SnapVault
secondary volume.
The -preserve option enables you to keep any Snapshot copies that are more recent than the common
Snapshot copy on the SnapVault secondary volume, and that are not present on the primary volume. The
-preserve option can be set to true or false. If the preserve option value is set to true, then no
rotation occurs, and Snapshot copy transfers halt when the SnapVault destination reaches the count specified
in the
keep option. If the -preserve value for this rule is false, Snapshot copy transfers continue after the
specified count is reached. The oldest copy is rotated out for the newest copy.

Modify a SnapVault Relationship
The command to change an existing SnapVault relationship:

cluster2::> snapmirror modify
Change the update schedule to use the 5min schedule:

cluster2::> snapmirror modify
-destination-path svm1_2:svm1_2_vol1 -schedule 5min
MODIFY A SNAPVAULT RELATIONSHIP

The snapmirror modify command enables you to change one or more properties of SnapMirror
relationships. The key parameter that identifies any SnapMirror relationship is the secondary volume.
Changes that are made by the snapmirror modify command do not take effect until the next manual or
scheduled update of the SnapMirror relationship. Changes do not affect updates that are started but are not yet
finished.
Configure the 5min update schedule:
cluster2::> snapmirror modify -destination-path svm1_2:svm1_2_vol1 -
schedule 5min
Operation succeeded: snapmirror modify for the relationship with
secondary "svm1_2:svm1_2_vol1".

Perform a SnapVault Manual Update
The snapmirror update command must be used from the

secondary cluster:
cluster2::> snapmirror update -source-path
svm1:svm1_vol1 -destination-path
svm1_2:svm1_2_vol1 -source-snapshot
Emergency_SnapVault_Update
You can select a specific Snapshot copy on

the primary volume to use.
PERFORM A SNAPVAULT MANUAL UPDATE

If it becomes necessary to perform a SnapVault update in between regularly scheduled updates or instead of
scheduled updates, use the snapmirror update command.
The snapmirror update command updates the secondary volume of a SnapMirror relationship.
The snapmirror update command behaves differently for data protection, vault, and load-sharing
relationships.
For vault relationships, the snapmirror update does not create a Snapshot copy on the primary
volume but transfers only selected Snapshot copies that are newer than the common Snapshot copy to the
secondary volume. (To transfer copies that are older than the common copy, use the -source-
snapshot parameter.)
Snapshot copies are selected by matching the -snapmirror-label Snapshot copy with the
SnapMirror label corresponding to the SnapMirror policy that is assigned to the SnapMirror relationship.
The snapmirror update command must be run from the secondary cluster:
cluster2::> snapmirror update -source-path svm1:svm1_vol1 -destination-
path svm1_2:svm1_2_vol1 -source-snapshot Emergency_SnapVault_Update

Managing SnapMirror and SnapVault Updates
To Do This Use This Command
Get SnapVault status snapmirror show
Manually update a SnapVault relationship snapmirror update
Modify SnapVault relationship properties snapmirror modify

Modify a mirror policy or SnapVault policy snapmirror policy modify
Modify an existing rule in a SnapVault policy snapmirror policy
modify-rule
Remove a rule in a SnapVault policy snapmirror policy
remove-rule
Delete a mirror policy or SnapVault policy snapmirror policy delete
SnapMirror commands are used to manage SnapMirror and SnapVault

relationships.
MANAGING SNAPMIRROR AND SNAPVAULT UPDATES

Cluster administrators can use the snapmirror policy commands to create and manage all data
protection mirror and SnapVault policies. SVM administrators can use the same commands to create and
manage all data protection mirror and SnapVault policies within SVMs.
All policy-management commands (except for the snapmirror policy show command) must be
run on the SVM that contains the secondary volume.
Only FlexVol volumes support commands for SnapVault policies.

ACTION: Exercise

exercise
equipment.
Open your
credentials
instructor. Part 2.
Stop after
Task 7. Q&A
ACTION: EXERCISE

What steps did you take to implement

a SnapVault relationship?
What was different about using
OnCommand System Manager to
create a SnapVault relationship
compared with using the CLI?
What was the name of the SnapMirror
label that you used for the SnapVault
relationship?

BASED EXERCISE

Lesson 2
Restoring Data from
SnapVault Secondary Volumes
LESSON 2: RESTORING DATA FROM SNAPVAULT SECONDARY VOLUMES

Restoring Data with SnapVault Software
Guidelines
In the restore operation from a SnapVault backup, a single,

specified Snapshot copy is copied from a SnapVault
secondary volume to a specified volume.
Before you restore a volume, you must shut down any
application that accesses data in a volume to be restored.
You can use SnapVault software to restore data to these
volumes:
Original primary volume
New, empty secondary volume
New secondary volume that already contains data
RESTORING DATA WITH SNAPVAULT SOFTWARE: GUIDELINES

In the restore operation from a SnapVault backup, a single, specified Snapshot copy is copied from a
SnapVault secondary volume to a specified volume. Restoring a volume from a SnapVault secondary volume
changes the view of the active file system but preserves all earlier Snapshot copies in the SnapVault backup.
Before restoring a volume, you must shut down any application that accesses data in a volume to which a
restore is writing data. Therefore, if you are using a logical volume manager (LVM), you must unmount the
file system, shut down any database, and deactivate and quiesce the LVM. The restore operation is disruptive.
When the restore operation finishes, the cluster administrator or SVM administrator must remount the volume
and restart all applications that use the volume.
The restore secondary volume must not be the secondary of another mirror or the secondary of another
SnapVault relationship. You can restore to the following volumes:
Original primary volume: You can restore from a SnapVault secondary volume back to the original
SnapVault primary volume.
New, empty secondary volume: You can restore from a SnapVault secondary volume to a new, empty
secondary volume. You must first create the volume as a data protection volume.
New secondary volume that already contains data: You can restore from a SnapVault secondary volume
to a volume that is populated with data. The volume must have a Snapshot copy in common with the
restore primary volume and must not be a data protection volume.

Restore Data Workflow
During a restore operation, the following actions occur:

A new temporary relationship is created from the restore
primary. The restore secondary can be the original volume
or a new volume.
During the restore operation, the secondary volume is
changed to read-only.
When the restore operation finishes, the temporary
relationship is removed.
RESTORE DATA WORKFLOW

A restore operation from a SnapVault backup consists of a series of actions that are performed on a temporary
restore relationship and on the secondary volume. During a restore operation, the following actions occur:
A new temporary relationship is created from the restore primary (which is the original SnapVault
relationship secondary volume) to the restore secondary. The temporary relationship is a restore type
(RST). The snapmirror show command displays the RST type while the restore operation is in
progress.
The restore secondary might be the original SnapVault primary volume or might be a new SnapVault
secondary volume.
During the restore process, the restore secondary volume is changed to read-only.
When the restore operation finishes, the temporary relationship is removed, and the restore secondary
volume is changed to read/write.

Restoring a Volume
Restore a volume by using the snapmirror restore

command:
cluster1::> snapmirror restore -destination-path
svm1:svm1_vol1 -source-path svm1_2:svm1_2_vol1
-source-snapshot 5min.2014-09-23_2010
Select exactly and carefully which Snapshot

copy to use in the restore operation.
Verify the restore status:

cluster1::> snapmirror show-history
RESTORING A VOLUME
If the data on a volume becomes unavailable, you can restore the volume to a specific time by copying a
Snapshot copy in the SnapVault backup. You can restore data to the same primary volume or to a new
location. This operation is disruptive.
CIFS traffic must not be running on the SnapVault primary volume when a restore operation is running.
This task describes how to restore a whole volume from a SnapVault backup. To restore a single file or LUN,
you can restore the whole volume to a different, nonprimary volume, and then select the file or LUN. If you
prefer, you can use the NetApp OnCommand management software online management tools.
If the volume to which you are restoring has compression enabled, and the secondary volume from which you
are restoring does not have compression enabled, disable compression. You disable compression to retain
storage efficiency during the restore. (The snapmirror restore command warns you that all data that is
newer than the Snapshot copy will be deleted.)
Restore a volume by using the snapmirror restore command:
cluster1::> snapmirror restore -destination-path svm1:svm1_vol1 -source-path
svm1_2:svm1_2_vol1 -source-snapshot 5min.2014-09-23_2010
Verify the restore status:
cluster1::> snapmirror show-history
Destination Source Start End
Path Path Operation Time Time Result
----------- -------- --------- ------------- ------------- -------
svm1:svm1_vol1 svm1_2:svm1_2_vol1 restore 9/23/14 20:14 9/23/14 20:14 success

Restoring a Single File or LUN
You can restore a single file or LUN or a set of files from a

Snapshot copy in a SnapVault secondary volume to the active
file system of a primary volume.
You can restart a failed or aborted single file or LUN restore
operation by reissuing the snapmirror restore
command.
Several SnapVault restore guidelines apply.
RESTORING A SINGLE FILE OR LUN

In clustered Data ONTAP environments, you can restore a single file or a single LUN from a SnapVault
secondary volume by using the NetApp OnCommand management software online management tools. The
following guidelines apply to SAN environments:
When you restore a LUN by overwriting it, new access controls do not need to be configured.
You must configure new access controls for the restored LUN only when you restore a LUN as a newly
created LUN on the volume.
If a LUN on the SnapVault secondary volume is online and mapped before the restore operation begins, it
remains so during the restore operation and after the operation finishes.
The host system can discover the LUN and issue a nonmedia access command for the LUN. Such
inquiries or commands are to set persistent reservations while the restore operation is in progress.
During a restore operation, you cannot use the lun create command to create a LUN in a volume.
Restore operations from tape and from a SnapVault backup are identical.
You cannot restore a single LUN from a SnapVault secondary volume on a system that is running in Data
ONTAP operating in 7-Mode.
For more information about restoring LUNs, see the Clustered Data ONTAP 8.3 SAN Administration Guide.

ACTION: Exercise

exercise
equipment.
Open your
credentials
instructor. Part 3.
Stop at the
end of Q&A
Exercise 6.
ACTION: EXERCISE

What steps did you take to restore a

primary volume from a SnapVault
secondary volume?
What temporary relationship was
created between the secondary volume
and the recovery target?
How did you verify the success of the
restore operation?

BASED EXERCISE

Ken Asks
I have a couple of
administration questions.
Can we discuss things like
monitoring backups and
storage efficiency?
KEN ASKS

SnapVault Administration Topics
Monitoring the SnapVault relationship status

Managing SnapVault and SnapMirror policies
Modifying SnapVault policy attributes
Restoring a single file or LUN
Managing storage efficiency for SnapVault secondary
volumes
SNAPVAULT ADMINISTRATION TOPICS

Monitoring SnapVault Relationship Status
Run the snapmirror show Command from the Secondary SVM
The command to show the status of the SnapVault

relationship:
Use the fields option to get more granular data.

Command for detailed output:
-destination-path svm1_2:svm1_2_vol1
MONITORING SNAPVAULT RELATIONSHIP STATUS: RUN THE SNAPMIRROR SHOW

COMMAND FROM THE SECONDARY SVM
You can use the snapmirror show command to get various levels of detail about a SnapVault
relationship.
Use these commands on the secondary cluster:
Get more details by using the destination-path or the instance options.
This is a small part of the output of the snapmirror show command with options:
cluster2::> snapmirror show -destination-path svm1_2:svm1_2_vol1
Source Path: svm1:svm1_vol1
Destination Path: svm1_2:svm1_2_vol1
Relationship Type: XDP
Relationship Group Type: none
SnapMirror Schedule: SnapVaultJob
SnapMirror Policy Type: vault
SnapMirror Policy: svm1_2_vault-policy
Tries Limit: -
Throttle (KB/sec): unlimited
Mirror State: Snapmirrored
Relationship Status: Idle

Commands to Manage Storage Efficiency
How Storage Efficiency Works with SnapVault
You can enable storage efficiency on the primary volume, the

secondary volume, or both.
Command to enable storage efficiency:
volume efficiency -on
Command to manually start a storage efficiency operation to

manually scan a volume:
volume efficiency -start -scan-old-data
Compression and storage efficiency do not interoperate.
COMMANDS TO MANAGE STORAGE EFFICIENCY: HOW STORAGE EFFICIENCY

WORKS WITH SNAPVAULT
Storage efficiency is important for SnapVault secondary volumes, which typically contain a large amount of
data. If primary and secondary volumes have storage efficiency enabled, data transfers to the SnapVault
secondary volume preserve storage efficiency. If the primary volume in a SnapVault relationship is enabled
for storage efficiency, all data backup operations preserve the storage efficiency. If storage efficiency is not
enabled on the primary volume, you might want to enable storage efficiency for the secondary volume
because it is likely to contain a large amount of data over time. If data from transfers is already present on the
volume, you can use the volume efficiency command to start a scan on the volume. If the relationship
is new with no transfers, you do not need to run the scan manually.
When storage efficiency is enabled on the SnapVault secondary volume, the SnapVault relationship manages
the schedule. When a data transfer begins, the storage efficiency process automatically pauses and then
automatically restarts when the transfer is finished. After the transfer and the post-transfer storage efficiency
processes are complete, the final Snapshot copy that was created in the secondary volume is replaced by a
new, storage-efficient Snapshot copy. If the final Snapshot copy that is created in the secondary volume is
locked before it can be replaced by the storage-efficient Snapshot copy, the new storage-efficient Snapshot
copy is still created. However, the nonefficient Snapshot copy is locked and is not deleted. That Snapshot
copy is deleted later during the storage-efficient cleanup process, after a subsequent update to the SnapVault
secondary volume and after the lock is released. A Snapshot copy in a SnapVault secondary volume might be
locked because the volume is the primary in another relationship, such as a data protection mirror
relationship.
If the secondary volume has additional compression enabled, storage efficiency is not preserved. Storage
efficiency on all data transfers in SnapVault relationships is not preserved when the secondary volume has
additional compression enabled. Because of the loss of storage efficiency, a warning message is displayed
when you enable compression on a SnapVault secondary volume. After you enable compression on the
secondary volume, you can never have storage-efficient transfers.

Now I know the differences between

SnapVault and SnapMirror software.
I learned how to design and
implement a SnapVault solution.
I know how to use SnapVault software
to recover my data and I learned how
to monitor and manage my SnapVault
and SnapMirror relationships.

References

NetApp Documentation
Clustered Data ONTAP 8.3 Data Protection Tape Backup and
Recovery Guide
REFERENCES

Module 7
Using Data Protection Management Solutions
MODULE 7: USING DATA PROTECTION MANAGEMENT SOLUTIONS
7-1 Data ONTAP Data Protection Administration: Data ONTAP Data Protection Administration

Module Objectives

Recall data protection management solutions
Describe the OnCommand Unified Manager interface
Describe the NetApp SnapManager suite of products
Describe the NetApp SnapProtect solution
Describe the features of the Symantec Plug-in for Data
ONTAP
Given a set of business requirements, select an appropriate
NetApp or third-party data protection management solution
MODULE OBJECTIVES


FlexClone
NDMP

NDMP-compatible backup solutions
Scripted solutions system:\

As you have seen in the course, NetApp data protection for FAS systems includes Snapshot copies, and
SnapRestore, FlexClone, SyncMirror, MetroCluster, SnapMirror, SnapVault, and NDMP technologies.
You have learned to use CLI commands and the OnCommand System Manager to manage data protection
and recovery for the Data ONTAP data protection technologies.
In this module, you become familiar with NetApp data protection management solutions:
NetApp OnCommand Unified Manager
NetApp SnapManager suite
NetApp SnapProtect solution
NetApp Plug-in for Symantec NetBackup

Unified View of the Storage Environment
OnCommand Console Dashboard
UNIFIED VIEW OF THE STORAGE ENVIRONMENT: ONCOMMAND CONSOLE

DASHBOARD
This is the NetApp OnCommand Unified Manager dashboard. OnCommand Unified Manager software
provides a single console for displaying dashboards, monitoring and active management, reporting, storage
provisioning, and data protection.
Storage administrators can use the OnCommand console to access dashboards to manage workflows for
backup, restore, and reporting. The NetApp Web Framework delivers a standard look and feel and similar
controls across various views, such as storage, server, inventory, and protected and unprotected data. The
OnCommand console provides an end-to-end view of the virtual infrastructure. By using the storage
inventory view, you can easily retrieve the server-to-storage and storage-to-VM mapping, and protect your
data.
There are variations across the versions of OnCommand Unified Manager; however, there is always a
comprehensive dashboard.

Using NetApp OnCommand Unified Manager
Protected data
Unprotected data Status indicators
USING NETAPP ONCOMMAND UNIFIED MANAGER

You can use OnCommand Unified Manager to protect your data with a centralized management console that
enables you to configure and control all SnapMirror, SnapVault, SnapManager, and SnapProtect operations.
Similar data can be combined within datasets, enabling you to:
Apply consistent data protection policies across the enterprise
Automate complex data protection processes
Pool backup and replication resources for higher utilization
The Unified Manager dashboard depicts complete data protection information at a glance, including
unprotected data and protection jobs that are not meeting SLAs.

Protection and Provisioning Capabilities
Available through the NetApp Management Console, which is the

client system for NetApp management software applications
Applied to a container of data called a dataset
Protection Capability Provisioning Capability

Simplifies the management of backup Simplifies provisioning of storage for
and mirror relationships NAS and SAN access
Automates data protection in Automates complex parameters, such
accordance with the selected backup or as space guarantee and deduplication
mirror topology and schedule
Performs dynamic secondary sizing Enhances the use of primary storage
and enhances the use of secondary
storage
PROTECTION AND PROVISIONING CAPABILITIES

The NetApp Management Console has data protection and provisioning capabilities, including continual
monitoring of all components. You can verify that your data is provisioned and protected as defined by the
policy that is applied to its dataset. The protection capability enables disaster recovery by performing failover
operations easily and efficiently.

Using NetApp SnapManager Suite
NetApp Data Protection Management for Specific Applications
SnapManager products provide application-aware data

protection for the major applications.
USING NETAPP SNAPMANAGER SUITE: NETAPP DATA PROTECTION

MANAGEMENT FOR SPECIFIC APPLICATIONS
SnapManager products provide application-aware data protection for the major applications, which include:
SnapManager for Exchange
SnapManager for SQL
SnapManager for SharePoint
SnapManager for Oracle

Using SnapManager to Restore Data
USING SNAPMANAGER TO RESTORE DATA

Archived backups that are created with SnapManager for Microsoft Exchange (SME) are available for restore
purposes. In the example on the slide, the navigation pane of the SME Restore UI expands so that you can
access local backups or archived backups.
Using an archived backup, you can restore only the Exchange mailbox database to the point in time when that
backup was created. With archived backup copies, you cannot replay the transaction logs up to the point in
time of failure. Archived backups are therefore primarily used for restore purposes with Single Mailbox
Recovery, or to meet compliance laws.

The SnapProtect Solution Overview
SnapProtect
Centralized Management
Application Awareness
VMware Backup Hyper-V
NAS Files, LUNs,
Exchange
Catalog and Datastores
SharePoint NAS File
Ms SQL Oracle DB2 SAP
Services
Unified granular restores from Snapshot copies, SnapVault, or tape

Multi-Tiered Backup and Disaster Recovery Third-party storage Tape
for a selection of apps
OnCommand Block-level transfer
Support
Unified Manager
to 7-Mode target
5.x
NetApp Snapshot
copies Thin replication NetApp storage efficiency
OnCommand Tape support

Unified Manager
6.x
Thin replication
THE SNAPPROTECT SOLUTION OVERVIEW

Data centers are composed of many types of application servers. All of these application servers require
protection.
The SnapProtect solution is an application-specific data protection management solution that provides
indexed, centrally managed, end-to-end, disk-to-disk replication to Data ONTAP storage, and to archival-to-
tape libraries.
SnapProtect software interoperates with application servers to create application-consistent Snapshot copies
of application server data that is stored on Data ONTAP primary storage systems. Application servers that the
SnapProtect solution supports include Oracle, SAP, and other database servers, and VMware ESX and
Microsoft Hyper-V virtual machines. The SnapProtect solution also supports other application data that is
stored on Data ONTAP LUNs (SAN) and NAS volumes.
For third-party primary storage, a feature in SnapProtect 10, Open Systems SnapVault, provides replication
from third-party storage to SnapVault secondary volumes on Data ONTAP operating in 7-Mode. With Open
Systems SnapVault, you can back up a local file system on Windows, Linux, and Solaris DAS and third-party
storage to Data ONTAP 7-Mode storage systems.
The SnapProtect solution interoperates with OnCommand Unified Manager to create SnapMirror replication
and SnapVault replication. Different versions of OnCommand Unified Manager support the Data ONTAP
operating system. Data ONTAP operating in 7-Mode requires OnCommand Unified Manager 5.2; clustered
Data ONTAP requires OnCommand Unified Manager 6.0.
The SnapProtect solution enables you to restore file and LUN data from Snapshot copies, SnapVault replicas,
or tape archives. To hasten search and recovery operations, SnapProtect software catalogs all backup copies,
including local Snapshot copies, SnapMirror and SnapVault copies, and tape backup copies.

Components of a SnapProtect CommCell
The SnapProtect solution is composed of several server and

client computers that are collectively called a CommCell.
The CommCell
CommServe OnCommand Media Agents Clients Disk Storage Tape Storage
Server Unified with Devices Devices
Manager iDataAgents
COMPONENTS OF A SNAPPROTECT COMMCELL

The SnapProtect solution is composed of one CommServe server, several other servers, and the client
machines that are being protected. This solution is collectively called a CommCell. The CommCell is one
instance of a SnapProtect environment. A SnapProtect CommCell has these components:
CommServe is the master server in a SnapProtect environment. The administrative interface of the
CommServe is called the CommCell Console or the CommCell Browser. The CommCell Browser is the
home of storage policies, schedule policies, clients, subclients, disk libraries, and other mechanisms.
OnCommand Unified Manager provisions secondary storage. It also processes SnapMirror and
SnapVault replication under the control of the CommServe host. Provisioning is provided through
resource pools that you create with the OnCommand Unified Manager UI. SnapMirror and SnapVault
replication are handed off to Unified Manager by the CommServe based on CommCell storage policies
that you configure within the SnapProtect UI.
MediaAgent software processes disk-to-disk and disk-to-tape data movement. MediaAgent software is
installed on SnapProtect CommServe. It can also be installed on a separate host to preserve good
performance. Media agents also perform indexing and maintain the index and the index cache in disk
libraries.
Clients with intelligent DataAgents (iDataAgents or iDAs) are application servers, such as Microsoft
SQL Server or Oracle database server, onto which you install application-specific iDA software packages
to control data consistency during backup operations. As you install iDA packages, the installation
process also joins clients to the CommCell. You then configure subclients that contain subsets of the
clients data. Subclients are separate, individual SQL or Oracle databases, separate mailbox databases, or
separate volumes.
Storage devices are disk or tape devices that provide primary, secondary, and tertiary storage. Disk
storage is provided by Data ONTAP 7-Mode storage systems and clustered Data ONTAP storage virtual
machines (SVMs). You can use Data ONTAP 7-Mode, clustered Data ONTAP, and tape libraries in the
same CommCell.

ACTION: Take a Poll

polling session.

polling panel.
Answer each Correct
click Submit. mark.
Raise your hand
Compare your
to ask a question
answers to the
or make a
correct
comment.
answers.

This poll is a quick poll on the NetApp SnapProtect solution.
When the instructor begins the polling session, see the polling questions that you are to answer. After all

Poll Questions
1. Which two statements about the features of OnCommand

Unified Manager are true? (Choose two.)
a. provides a single UI for viewing protected and unprotected data
b. does not provide information about unprotected data
c. provides a UI to configure SnapMirror and SnapProtect software
d. does not provide an information UI to manage storage provisioning
2. Which two statements about SnapProtect software are true?

(Choose two.)
a. provides indexed, disk-to-disk and to disk-to-tape data protection
b. provides replication from third-party storage to SnapVault secondary
volumes on Data ONTAP 7-Mode
c. does not interoperate with OnCommand Unified Manager
d. does not enable you to restore file or LUN data from Snapshot copies,
SnapVault replicas, or tape archives

Ken Asks
Many of the customers I work

with use Symantec. Does the
Data ONTAP operating
system work with NetBackup
software?
KEN ASKS

NetApp Plug-In 2.0 for Symantec NetBackup
Symantec NetBackup Replication Director
NetApp Plug-in for Symantec interoperates with NetBackup

(NBU) software and clustered Data ONTAP or 7-Mode.
NBUPlugin2.0 Unified
Manager
OnCommand djc1 1
Unified Manager
2 3
NetBackup Machines:
Cluster1-01 Cluster1-02 Clustered
(Master and Media) 1. NetBackup Master and Media
Data ONTAP
2. NBUPlugin2.0
1 (Linux or Windows)
SVM1 SnapVault SVM2
SnapMirror 3. OnComamand Unified Manager
SVMs (VMware appliance)
NFS or VOL1 VOL2
4. Clustered Data ONTAP
CIFS
Client (NetApp cluster)
4 5. NetBackup client
5
NETAPP PLUG-IN 2.0 FOR SYMANTEC NETBACKUP: SYMANTEC NETBACKUP

REPLICATION DIRECTOR
Many data centers are implemented with Data ONTAP and Symantec NetBackup. The NetApp Plug-in for
Symantec NetBackup supports 7-Mode and clustered Data ONTAP for the NetBackup Replication Director.
Support for clustered Data ONTAP is new with NetApp Plug-in 2.0 for Symantec.
The combination of Symantec NetBackup software with NetApp SnapVault and SnapMirror replication
technologies provides an integrated and scalable disk-based data protection and recovery solution.

I am confident in my
understanding of
NetApp and third-party
data protection
management solutions.

Course Summary
Now that you have completed this course, you should be
able to:
Describe Data ONTAP data protection technologies and data
protection management solutions
Create and manage Snapshot copies
Describe SyncMirror and MetroCluster configuration
Configure NDMP for backing up to tape
Create and manage SnapMirror relationships
Create and manage SnapVault relationships
Describe Data ONTAP and third-party management solutions
COURSE SUMMARY

Ken Revisits the Data Protection Assessment
I remember taking an
assessment at the beginning
of class.
I would like to see how I would
score on that data protection
assessment now!
KEN REVISITS THE DATA PROTECTION ASSESSMENT

ACTION: Post-Class Assessment
20-Question Quiz
Instructor provides Duration: 15 minutes

exam link.
Open the Submit your

assessment in answers.
a browser.
Read and Click Submit
answer each Compare to your
after each baseline score.
question. question.
After the final
See how much
question, your
you have learned
score is
in the class.
displayed.
ACTION: POST-CLASS ASSESSMENT: 20-QUESTION QUIZ

To begin the post-class assessment, click the link that your instructor provides. To measure the knowledge
you have gained from this course, compare your score to your own pre-class assessment baseline score.

References

Getting Started with NetApp Software: Installing, Configuring,
and Using Unified Manager 6.0
REFERENCES

Thank You
THANK YOU

STRSW Ilt Dataprot Rev6 Studentguide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

STRSW Ilt Dataprot Rev6 Studentguide

Uploaded by

Copyright:

Available Formats

Data ONTAP Data

Data ONTAP Data Protection Administration

NetApp University - Do Not Distribute

U.S. GOVERNMENT RIGHTS

2 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

3 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

DATA ONTAP DATA PROTECTION ADMINISTRATION

4 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Getting Started Classroom Facilities Virtual Classroom

5 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

By the end of this course, you should be able to:

6 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Session 1 (Day 1, Morning)

Session 2 (Day 1, Afternoon)

Session 3 (Day 2, Morning)

Session 4 (Day 2, Afternoon)

7 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Virtual setting Classroom setting

I am Marc. I am a NetApp partner selling

INTRODUCTIONS: NAME, JOB TITLE, GOALS FOR THIS CLASS

8 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Click the whiteboard arrow. Your name appears on the arrow.

WHERE DO YOU LIVE?

9 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Ken is a professional who does the following:

KEN, YOUR GUIDE TO THIS COURSE

10 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Fundamental Courses Intermediate Courses Advanced Categories

Clustered Data ONTAP Data ONTAP

Data ONTAP Management

Data ONTAP Data Enterprise

DATA ONTAP LEARNING PATH

11 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

I wonder how much I already

KEN TAKES THE DATA PROTECTION ASSESSMENT

12 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Instructor provides Duration: 20 minutes

Open the Submit your

After the final

ACTION: PRE-CLASS ASSESSMENT: 20-QUESTION QUIZ

13 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

W2K12 CentOS 6.5

Data ONTAP 8.3

cluster1-01 cluster1-02 cluster2-01

CLASS EQUIPMENT: BASIC ARCHITECTURE

14 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Access your Duration: 15 minutes

15 Data ONTAP Data Protection Administration: Welcome

NetApp University - Do Not Distribute

Do you have any questions about your