Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Exercise Guide
Content Version 1.0
NETAPP UNIVERSITY
Exercise Guide
Course ID: STRSW-ILT-DATAPROT-REV07
Catalog Number: STRSW-ILT-DATAPROT-REV07-EG
COPYRIGHT
2016 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.
TRADEMARK INFORMATION
NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Customer Fitness, CyberSnap,
Data ONTAP, DataFort, FilerView, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexCache, FlexClone,
FlexPod, FlexScale, FlexShare, FlexVol, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore,
OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator,
SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore,
Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, 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.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
OBJECTIVES
This exercise focuses on enabling you to do the following:
Ensure connectivity to an ONTAP cluster.
Synchronize system time between the ONTAP clusters and the Windows domain controller.
Assign a network time server IP address for the ONTAP clusters.
Ensure that required licenses are installed on the ONTAP clusters.
STUDY-AID ICONS
These four icons are used throughout the exercise to identify steps that require your special attention.
Warning
You should follow all of the exercise steps, but misconfiguring steps labeled with this icon
might cause later steps to not work properly. Check this step carefully before continuing to
the next step.
Attention
Steps or comments labeled with this icon should be reviewed carefully to save time, learn a
best practice, or avoid errors.
Information
Comments labeled with this icon provide additional information about the topic or
procedure.
Knowledge
Comments labeled with this icon provide reference material that gives additional context
that you may find useful.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. Ensure that you see the Start page of your assigned Windows 2012 Server.
2. On the Windows 2012 Server Start page, scroll down and click the Desktop tile.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
3. Verify that you see the desktop and that it contains the PuTTY program.
4. To connect to the ONTAP cluster UI, browse to the NetApp OnCommand System
Manager URL which is built in to ONTAP 9.0.
To connect to the CLI of the ONTAP cluster, you use PuTTY. PuTTY is a UI for the
Telnet and Secure Shell (SSH) protocols.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. In the PuTTY Configuration dialog box, verify that the svl-nau-mgmt saved session is listed.
Double-click svl-nau_mgmt:
7. You can also connect to the ONTAP cluster CLI by connecting to any node in the
cluster: svl-nau-01_mgt (node 1) or svl-nau-02_mgt (node 2).
8. The first time you connect, you receive a PuTTY Security Alert. Click Yes.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. If you have any difficulty logging in to the ONTAP cluster CLI, refer to this table.
Ensure that you are using the correct username and password in the correct case (both
are case-sensitive).
System Host Name IP Address User Name Password
ONTAP cluster
svl-nau 192.168.0.50 admin (case sensitive) Netapp123
management LIF
11. Verify that both nodes of the ONTAP cluster are healthy and eligible:
cluster show
12. If the health or eligibility of either node is listed as false, alert your instructor.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2. Display the date and time on the Windows 2012 Server desktop by clicking the time and date
display in the lower-right corner of the desktop window:
3. To view the time zone, date, and time, click Change date and time settings:
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
4. Review the date, time, and time zone on the Windows 2012 Server:
5. In the following steps, you determine what time zone has been configured on your
ONTAP cluster and then, if necessary, you change the cluster time zone to
US/Pacific.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
7. Your ONTAP clusters might have a different time zone from the one displayed in this
example. However, your goal is to make the time zone of the ONTAP clusters match
the time zone of the Windows domain controller. In the next step, verify the time zone
of the Windows Server.
8. On the ONTAP cluster, change the time zone to US/Pacific by entering this case-sensitive
command:
timezone US/Pacific
9. Display the date, time, and time zone in the ONTAP cluster:
date
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. Compare the date and time on the Windows 2012 Server with the date and time in the ONTAP
cluster.
11. If the system date and time are not synchronized to within 5-minutes, correct the
ONTAP cluster date.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
12. Enter the date command plus the accurate date and time. Use the 24-hour time format with the
following syntax:
date [YYYY][MM][DD][HH][MM]
13. When you enter the date command on any node in the cluster, the date command
sets the date and time on all nodes in the ONTAP cluster.
NTP service synchronizes the date and time for all nodes in the cluster. If an NTP
time server has been configured, then all nodes in the cluster remain in time sync with the NTP
time server.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
14. Connect to rtp-nau and repeat Steps 2 -12 to change the time zone and synchronize time for rtp-
nau.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
4. Enter the administrators user name and password for svl-nau, and then click Sign In.
6. In ONTAP, the NTP Service is enabled by default. However, you must add the time
servers and you must also ensure that the hosts you add as time servers have the NTP
Service enabled.
In the next step, you configure the Windows domain controller as the NTP time server.
Host
System Name IP Address User Name Password
Windows 2012 Server w2k12 192.168.0.11 LEARN\Administrator Netapp123
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
8. Verify that the domain controllers IP address has been set as the time server for svl-nau.
9. From your Windows browser, open OnCommand System Manager for rtp-nau.
SYSTEM HOST NAME IP ADDRESS USER NAME PASSWORD
ONTAP cluster
rtp-nau 192.168.0.100 admin (case sensitive) Netapp123
management LIF
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. To set the domain controller as the time server for rtp-nau, edit the date and time.
11. To avoid issues with the CIFS protocol, always assign one of the domain controllers
as the network time server for ONTAP clusters. The ONTAP cluster NTP service
setting keeps all nodes in the cluster synchronized with Windows domain time.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2. The licenses enable features of ONTAP that are required for later exercises. Verify that these
required license codes have been installed:
NFS
CIFS
SnapRestore
SnapMirror
FlexClone
SnapVault
Cluster Base License
NOTE: There may be an iSCSI license installed on the rtp-nau cluster. The iSCSI license is not
needed for any exercises in this course.
3. If any of the licenses listed in Step 2 are not installed, contact NetApp University
Support for assistance.
END OF EXERCISE
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
OBJECTIVES
By the end of this exercise, you should be able to:
Create an intercluster subnet and an intercluster LIFs for both clusters
Configure cluster peering
Configure storage virtual machine (SVM) peering
1. You are implementing the network connectivity that is necessary to enable peering
relationships between clusters. First, you create a subnet on svl-nau to be used for
intercluster traffic.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
4. Click Create.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
7. In the Network window, click the Network Interfaces tab, select svl-nau-01_clus1, and then
click Create.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
8. In the Create Network Interface window, enter the following configurations for the new LIF:
Name: Intercluster_LIF1 Assign IP Address: Using a subnet
Interface Role: Intercluster Connectivity Port: svl-nau-01:e0e
IPspace: Default
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
9. In the Add Details window, select the Assign IP Address: Using a subnet option, and then
click OK.
11. For fault tolerance, every node of the cluster must have an intercluster LIF. In the
next step, you repeat steps 710 to create an intercluster LIF that is named
Intercluster_LIF2 and is located on cluster node 2.
12. Repeat steps 710 to create a second intercluster LIF with the following configurations:
Name: Intercluster_LIF2 Assign IP Address: Using a subnet
Interface Role: Intercluster Subnet: Intercluster_Subnet/Auto-select the
Connectivity IP address from this subnet
IPspace: Default Port: svl-nau-02:e0e
13. In the Network window, click the Network Interfaces tab, and verify that the two new
intercluster LIFs (named Intercluster_LIF1 and Intercluster_LIF2) are listed.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. The next steps repeat the steps of Task 1 to create an intercluster subnet and an
intercluster LIF on the secondary cluster, rtp-nau.
5. Click Create.
6. In the next step, you create a single intercluster LIF on the secondary cluster, rtp-nau.
7. In the Network window, click the Network Interfaces tab, select the intercluster LIF (named
cluster_mgmt), and then click Create.
8. In the Create Network Interface window, enter the following configurations for the new LIF:
Name: Intercluster_LIF1 Assign IP Address: Using a subnet
Interface Role: Intercluster Connectivity Subnet: Intercluster_Subnet/Auto-select the
IP address from this subnet
IPspace: Default Port: rtp-nau-01:e0f
9. Click Create.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. In the Network window on the Network Interfaces tab, verify that the intercluster LIF (named
Intercluster_LIF1) was created on rtp-nau.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. On svl-nau, on the Configurations tab, select Cluster Peers, and then click Create.
3. Click Create.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. On rtp-nau, on the Configurations tab, select Cluster Peers, and then click Create.
8. Click Create.
10. You can verify that the cluster peers are available by returning to the Configurations
tab and clicking Refresh. If they are reported as unavailable, you must ensure that
the intercluster LIF IP addresses were entered correctly for svl-nau and rtp-nau.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. To configure SVM peers, you must use the CLI. SVM peering is not yet configurable
using OnCommand System Manager.
2. To create SVM peer relationships, the intended SVM peer partner must accept the
relationship. In the steps that follow, you enter the vserver peer create
command on the svl-nau CLI and the vserver peer accept command on the
rtp-nau CLI.
Normal output:
Info: [Job 219] 'vserver peer create' job queued
Normal output:
Info: [Job 140] 'vserver peer accept' job queued
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
8. Verify that the SVMs are peered by entering the following command from either the svl-nau or
rtp-nau CLI:
vserver peer show
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
In the next exercise you will implement SnapMirror relationships to replicate volumes between
the two SVMs.
END OF EXERCISE
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
OBJECTIVES
This exercise focuses on enabling you to do the following:
Create a SnapMirror policy
Create a SnapMirror relationship
Perform a SnapMirror initial transfer
Perform a manual SnapMirror update
Schedule automatic SnapMirror updates
Verify data transfer
1. On svl-nau, click the SVMs tab, and then select svm_yellow > Volumes.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. Before you leave the Create Protection Relationship window, create a schedule to automate the
SnapMirror updates:
a. In the Configuration Details section, click the Create Schedule link.
b. In the Create New Schedule window, enter the following configurations:
Schedule Name: svm_yellow:yellow_share_CIFS
Select the Basic radio button.
Repeat: Daily
Time: 2:00AM
c. Click Create.
7. In the Create Protection Relationship window, verify that the Initialize Relationship checkbox
is selected, and then click Create.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
8. Click OK.
The Create Protection Relationship wizard has a Status area that reports when the secondary
volume has been created and the mirror relationship.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
9. Verify the SnapMirror status on the destination cluster, rtp-nau, by clicking Protection >
Relationships.
11. You should make a note of the source volume settings, such as thin provisioning,
deduplication, compression, and auto-grow. You can use this information when you
break the SnapMirror relationship and verify the destination volume settings.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. In the process of creating and initializing the SnapMirror relationship, the SnapMirror
secondary volume is not automatically mounted.
To see the data that has been copied to the SnapMirror secondary volume, you must
first mount the secondary volume in the cluster namespace. In the next steps, you mount the
secondary volume in the rtp-nau namespace.
4. Click Mount.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. In the next steps, you create a share for the volume that you added to the namespace.
Then you map a Windows drive letter to the share.
8. Create a share:
a. In the Create Share window, enter the following configurations:
Folder To Share: Browse to the /svm_yellow_yellow_share_CIFS_volume_mirror
volume.
Share Name: Accept the default share name.
Comment: Leave blank.
b. Click Create.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
9. Open Windows File Explorer, and then double-click the blue_root mapping.
On the Windows Server, a drive letter is already mapped to a share on svm_blue.
11. Using Windows File Explorer, right-click Network, and then select Map network drive...
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
13. In the previous step, the IP address used is one of two that are assigned to the SVM
data LIF with the CIFS protocol access permitted.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
14. Copy the file named File_240M from the C:\CourseFiles folder into the yellow_share folder.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
16. In the Update window, do not change anything, and then click Update.
17. Wait for the Transfer Status to change from Transferring to Idle.
19. In Windows File Explorer, check for the file in the destination volume.
The SnapMirror relationship has successfully transferred the file.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
20. Monitor the status of SnapMirror data transfers in the Relationships window on the destination
cluster to ensure that the transfers are occurring on the specified schedule:
The Is Healthy field must display Yes.
The Relationship State field must display Snapmirrored.
The Lag Time must be no more than the transfer schedule interval.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. Verify that you have configured the following relationships between the ONTAP clusters,
SVMs, and volumes:
END OF EXERCISE
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
OBJECTIVES
This exercise focuses on enabling you to do the following:
Create a simulated disaster on the SnapMirror source volume
Perform disaster recovery procedures on the SnapMirror destination volume
Return the SnapMirror relationship to its original configuration
Verify data transfer
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2. In the Unmount Volume dialog box, select the Force volume unmount operation checkbox,
and then click Unmount.
3. Click the Volumes tab, select yellow_share_CIFS_volume, and then click Status > Offline.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. On your Windows desktop, attempt to access the yellow_share (W:) mapped drive.
After 1 or 2 minutes of searching, Windows should display an error message.
Results might vary. You might get a different error message from Windows.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. The first steps of the volume disaster workflow include the following actions:
a. You verify the source volume status.
b. You quiesce and break the SnapMirror relationship.
c. You verify the destination volume status.
2. You must always perform the SnapMirror break operation from the destination
volume. On the destination SVM, you check the SnapMirror status to see whether a
transfer is in progress. The SnapMirror relationship must be in an idle state before
you can break the SnapMirror relationship.
3. On rtp-nau, expand Protection > Relationships, and then check the Transfer Status column.
4. Before you begin, the destination volume must be mounted on the destination SVM
namespace.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
7. You must ensure that the transfer status of the SnapMirror relationship is quiesced
before you run the SnapMirror break operation. The quiesce operation might take
some time if there was a transfer in progress.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
9. In the Break dialog box, select the checkbox labeled OK to break the selected relationship,
and then click Break.
10. Verify that the Relationship State column displays Broken Off.
11. During normal SnapMirror operations, the secondary volume is a data protection
type volume which is read-only. In the next step, you look at the volume type of the
secondary volume to see whether it is still read-only or the type has changed to RW.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
12. In the OnCommand System Manager, select the columns shown on the screen:
a. Click SVMs > svm_blue > Volumes.
13. Verify that the Type column indicates rw for the volume labeled
svm_yellow_yellow_share_CIFS_volume_mirror.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
14. The state of the SnapMirror relationship is now broken. The SnapMirror primary
volume is offline and unavailable to read and write requests from clients. The
SnapMirror secondary volume is now writable.
15. Verify the volume settings (such as thin provisioning, deduplication, compression,
and autogrow) on the destination volume:
a. Click Edit, make any necessary changes, and then click Save and Close.
b. The settings should match the settings on the source volume.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
17. On your Windows desktop, open Windows File Explorer, and click the drive letter mapped to
the blue_root share. Notice that the mirrored volume was already mounted into the destination
SVMs namespace.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
20. Right-click in the folder, and then select Paste. This action creates a copy of the file.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. Verify that the SnapMirror relationship is broken off and the destination volume is in a
read/write state.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. When the source volume becomes available, you must resynchronize the data from
the destination volume to the source volume, update any modifications after the
resynchronization, and activate the source volume. First, you bring the original source
volume online.
8. The primary volume is again online and mounted into the svl-nau namespace.
In the next step, on rtp-nau, you check the SnapMirror status.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. The status of the SnapMirror relationship is Broken Off. The primary volume is
online. However, data is written to the secondary volume.
In the next step, you reverse the direction of the SnapMirror relationship to copy data
that was written to the secondary back to the primary volume.
The Reverse Resync operation can be run from only the SnapMirror secondary SVM.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
12. In the Reverse Resync dialog box, select the checkbox labeled OK to reverse resync the
relationship, click Reverse Resync, and then click Refresh to see the change.
The SnapMirror relationship is removed from the protection list.
13. Locate the reversed SnapMirror relationship by going to svl-nau Protection > Relationships.
14. On the svl-nau Relationships page, the original source is now the destination, and the
original destination is now the source. The SnapMirror policy is set to DPDefault.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. Verify that the original source volume is now configured as the SnapMirror destination, and the
original destination is now the SnapMirror source volume.
If the relationship stays in this configuration for long, you might need to reset the mirror policy
and update schedule until time to return the SnapMirror relationship to its original configuration
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. You start to restore the original relationship by updating the reversed SnapMirror
relationship, because clients might have written to the SnapMirror reversed
secondary.
After you update the reversed relationship, you break the relationship. Be sure that you verify
that the transfer status is idle before you break the reversed mirror.
2. On svl-nau, click Protection > Relationships, and then click Operations > Update.
3. In the Update window, leave the default configuration setting of On demand, and then click
Update.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
4. When you reverse synchronize, the schedule is not applied to the temporary reversed
relationship. The update operation is necessary to bring all data written to the
reversed secondary back to the primary volume. The On demand configuration
setting in the Update window transfers based on the newest shared Snapshot copy on
the source and destination volumes.
5. Use Windows File Explorer to check that the file copy you made on the rtp-nau SVM share has
been replicated to the svl-nau SVM share.
6. On svl-nau, click Protection > Relationships, and then click Operations > Quiesce.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
8. After you make sure that the transfer status is quiesced, click Operations > Break.
9. In the Break dialog box, select the checkbox labeled OK to break the selected relationship,
and then click Break.
11. In the next step, you reestablish the original SnapMirror relationship by again using
the Reverse Resync operation.
13. Select the checkbox labeled OK to reverse resync the relationship, and then click Reverse
Resync.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
14. Now that the SnapMirror relationship is reversed, you must log in to rtp-nau to verify
and manage the SnapMirror relationship. SnapMirror is always managed from the
SnapMirror destination.
You also must reapply the SnapMirror update schedule.
16. Verify that the original SnapMirror relationship has been restored and is healthy.
The Relationship State column should display Snapmirrored.
17. On the rtp-nau Protection page, reassign the SnapMirror policy and schedule:
a. With the SnapMirror relationship selected, click Edit.
b. Assign the original mirror policy and schedule.
c. Click OK.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
18. Manually update the SnapMirror relationship by clicking Operations > Update.
20. Verify that the original SnapMirror relationship has been reestablished.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. Verify that you have now successfully returned the SnapMirror relationship to its original
configuration.
END OF EXERCISE
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
OBJECTIVES
This exercise focuses on enabling you to do the following:
Create an unscheduled Snapshot copy on the SnapMirror source volume
Perform a SnapMirror update to replicate the unscheduled Snapshot copy to the destination volume
Use the unscheduled Snapshot copy as a base for the FlexClone volume
Offline and delete the cloned volume
1. SnapMirror replicates the Snapshot copy history from the source to the destination
volumes. If a Snapshot copy is locked because it is the base Snapshot copy of a
FlexClone volume, the SnapMirror update fails. For the SnapMirror update to
succeed, you should delete the FlexClone volume or split it to remove the Snapshot
copy dependency.
Many situations arise in which testing must be performed using the data on the SnapMirror
destination volume. For SnapMirror updates to proceed uninterrupted while the testing takes
place, it is a NetApp best practice to follow these steps:
a. You create an unscheduled Snapshot copy on the source volume.
b. You replicate that Snapshot copy to the destination volume.
c. You use the Snapshot copy as the base for the FlexClone volume.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
3. In the Create Snapshot Copy window, name the Snapshot Copy snapshot_for_DR_testing, and
then click Create.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
5. In the Update window, leave the default selection of the On demand radio button, and then click
Update.
7. If the transfer status does not change in a reasonable amount of time, click the Refresh button.
9. In the Volumes window, select the SnapMirror destination volume, and then click Clone >
Create > Volume.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. In the Create FlexClone Volume window, scroll down the list of Snapshot copies, select the one
named snapshot_for_DR_testing, and then click Clone.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
14. Double-click the folder of the mirror clone (the actual folder names might vary).
You should see the same two files that exist in the SnapMirror source and destination volumes.
15. Right-click the File_240M Copy file, and then select Copy.
16. Right-click in the folder, and then select Paste to create another copy of the file.
You should see a third copy of the original File_240M file in the folder.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
17. On rtp-nau, click the Volumes button, right-click the cloned volume, and then select Clone >
View Hierarchy.
18. Click the arrow to expand the volume selection, notice the difference in the % Used column
between the two volumes, and then click Close.
19. Click the Namespace button, select the cloned volume, and then click Unmount.
20. In the Unmount Volume window, select the checkbox labeled Force volume unmount
operation, and then click Unmount.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
21. Click the Volumes button, right-click the cloned volume, and then select Status > Offline.
22. In the Offline Volume confirmation window that appears, click the Offline button.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
24. In the Delete Volume window, select the checkbox labeled OK to delete the volume(s) and its
data, and then click Delete.
25. In this exercise you have created an unscheduled Snapshot copy on the SnapMirror
source volume. That Snapshot copy was replicated via SnapMirror software to the
destination volume and used for a FlexClone operation. Now that you have deleted
the FlexClone volume, it is a good practice to delete the original Snapshot copy from
the source volume.
26. On svl-nau, click the Volumes button, and then select the SnapMirror source volume.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
27. At the bottom of the window, click the Snapshot Copies tab.
29. In the Delete Snapshot Copy window, select the checkbox labeled OK to delete the Snapshot
copies and their associated backup data, and click Delete.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
31. Check the SnapMirror destination volume to see whether the unscheduled Snapshot copy has
been deleted.
You should not find the Snapshot copy named snapshot_for_DR_testing.
END OF EXERCISE
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
In the second part of the exercise, you use the SnapMirror SVM to run disaster-recovery failover and
recovery. You practice failing over clients to the disaster-recovery cluster. After the clients have been updated
to access the disaster-recovery SVM, you verify data access. You also modify the relationship so that the
disaster-recovery SVM becomes the source and the primary SVM becomes the destination. (A system might
need to use this reverse configuration for some time.) Finally, you recover the primary SVM and return to the
original SVM SnapMirror relationship. This flow diagram shows the major steps involved in the second part
of the activity.
OBJECTIVES
This exercise focuses on enabling you to do the following:
Configure a SnapMirror SVM disaster-recovery relationship that protects SVM-scoped resources
Verify that changes to source-side elements are replicated to the disaster-recovery cluster
Practice client failover to the SVM on the disaster-recovery cluster and verify data access
Recover and resynchronize the source SVM after a disaster
E4-1 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2. Enter the following command on svl-nau to calculate the total aggregate size of the storage
needed for the disaster-recovery cluster:
svl-nau::> volume show -vserver svm_yellow -fields used
Sample output:
vserver volume used
---------- --------------------- -------
svm_yellow exp_yellow_NFS_volume 44.21MB
svm_yellow exp_yellow_NFS_volume_clone_14072016_164416_58
9.21MB
svm_yellow svm_yellow_root 768KB
svm_yellow yellow_share_CIFS_volume
485.4MB
svm_yellow yellow_thickvol 9.88MB
svm_yellow yellow_thinvol 536KB
svm_yellow yellow_usr_001 11.00MB
svm_yellow yellow_usr_002 10.82MB
8 entries were displayed.
svl-nau::>
3. You need to determine the space required for the disaster-recovery SVM. You need
to account for the space required for the replicated volumes and the space required
for the SVM configuration data. In a production environment, the SVM configuration
data requires at least one non-root aggregate with minimum free space of 10 GB.
The best practice for the SVM configuration data is to have at least two non-root aggregates
with a minimum free space of 10 GB each.
4. By default, each of these volumes is protected (except the root volume). For this
exercise, you are going to demonstrate selective protection and the following volumes
are not protected: exp_yellow_NFS_volume_clone_14072016_164416_58 and
yellow_share_CIFS_volume. Your clone volume likely has a slightly different name
because, by default, the volume adopts a date code in its name.
You should recall that the svm_yellow_share_CIFS_volume volume has already been
configured in a SnapMirror relationship in a previous exercise.
E4-2 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
5. Enter the following command on rtp-nau to verify that the n1_aggr_main_dr aggregate can
support the size of the volumes in svm_finance:
rtp-nau::> storage aggregate show
Sample output:
Aggregate Size Available Used% State #Vols Nodes RAID Status
--------- -------- --------- ----- ------- ------ ---------------- ------------
aggr0_rtp1 16.70GB 11.51GB 31% online 1 rtp-nau-01 raid_dp,
normal
rtp01_fcal_001
28.12GB 26.04GB 7% online 4 rtp-nau-01 raid_dp,
normal
rtp01_fcal_002
28.12GB 26.81GB 5% online 2 rtp-nau-01 raid_dp,
normal
3 entries were displayed.
rtp-nau::>
Based on the output of the command in Step 2, there is plenty of space on any of the aggregates
on the rtp-nau cluster.
E4-3 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. From the clustershell on rtp-nau, enter the following command to create a disaster-recovery
SVM:
rtp-nau::> vserver create -vserver svm_yellow_dr -subtype
dp-destination
Sample output:
[Job 34] Job succeeded:
Vserver creation completed
2. Enter the following command to verify that the disaster-recovery SVM was created:
rtp-nau::> vserver show -vserver svm_yellow_dr
Sample output:
rtp-nau::> vserver show -vserver svm_yellow_dr
Vserver: svm_yellow_dr
Vserver Type: data
Vserver Subtype: dp-destination
Vserver Admin State: running
Vserver Operational State: stopped
Vserver Operational State Stopped Reason: dp-destination-not-started
Allowed Protocols: nfs, cifs, fcp, iscsi,
ndmp
Disallowed Protocols: -
Is Vserver with Infinite Volume: false
In this abbreviated output, you can see that the operational status of the SVM is stopped because
it is a disaster-recovery SVM. The SVM becomes active during failover to the disaster-recovery
cluster.
4. The SVM root volume is not mirrored. No user data should be stored in the SVM
root volume. Other than junction-paths, any data stored in the SVM root volume is
unprotected.
E4-4 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. This task requires commands to be entered on both clusters. You should be aware of
the cluster prompt (svl-nau::> and rtp-nau::>) on which each command is
entered.
2. From the clustershell on rtp-nau, enter the following command to create an SVM peer
relationship between svm_yellow (on svl-nau) and svm_yellow_dr (on rtp-nau):
rtp-nau::> vserver peer create -vserver svm_yellow_dr -peer-cluster
svl-nau -peer-vserver svm_yellow -applications snapmirror
Sample output:
Info: [Job 35] 'vserver peer create' job queued
3. Enter the following command to check the status of the peer request specific to SVM
svm_yellow_dr:
rtp-nau::> vserver peer show-all -vserver svm_yellow_dr
Sample output:
Peer Peer Peering Remote
Vserver Vserver State Peer Cluster Applications Vserver
----------- ----------- ------------ ----------------- ------------- ---------
svm_yellow_dr
svm_yellow initiated svl-nau snapmirror svm_yellow
4. From the clustershell on svl-nau, enter the following command to check the status of the peer
request specific to SVM svm_yellow:
svl-nau::> vserver peer show-all -vserver svm_yellow
Sample output:
Peer Peer Peering Remote
Vserver Vserver State Peer Cluster Applications Vserver
----------- ----------- ------------ ----------------- -------------- ---------
svm_yellow svm_blue peered rtp-nau snapmirror svm_blue
svm_yellow svm_yellow_dr
pending rtp-nau snapmirror svm_yellow_dr
5. Enter the following command to accept the peer request from rtp-nau:
svl-nau::> vserver peer accept -vserver svm_yellow -peer-vserver
svm_yellow_dr
Sample output:
Info: [Job 70] 'vserver peer accept' job queued
E4-5 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. Enter the following command to verify that the SVMs are peered:
svl-nau::> vserver peer show-all -vserver svm_yellow
Sample output:
Peer Peer Peering Remote
Vserver Vserver State Peer Cluster Applications Vserver
----------- ----------- ------------ ----------------- -------------- ---------
svm_yellow svm_blue peered rtp-nau snapmirror svm_blue
svm_yellow svm_yellow_dr
peered rtp-nau snapmirror svm_yellow_dr
7. Repeat Step 6 on rtp-nau (svm_yellow_dr) to verify that rtp-nau also sees the SVMs as peered.
E4-6 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. From the clustershell on rtp-nau, enter the following command to create the SnapMirror
relationship with the primary SVM:
rtp-nau::> snapmirror create -source-path svm_yellow: -destination-path
svm_yellow_dr: -type DP -throttle unlimited -policy DPDefault -schedule
hourly -identity-preserve true
2. The source and disaster-recovery clusters share a Layer 2 network. To preserve the
network configuration used by each client during a failover event, in Step 1, you used
the identity-preserve mode of SnapMirror SVM. In some use cases for
identity-preserve mode, the administrator might want to modify some of the
network configuration settings after cutover.
3. For a full list of configuration items that are maintained when the identity-
preserve flag is set to true, see the ONTAP 9.0: SVM Disaster Recovery
Preparation Express Guide.
4. Enter the following command to verify that the SnapMirror relationship was created and is in the
uninitialized state:
rtp-nau::> snapmirror show
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_red:red_share_CIFS_volume
XDP svm_blue:svm_red_red_share_CIFS_volume_vault
Snapmirrored
Idle - true -
svm_yellow: DP svm_yellow_dr:
Uninitialized
Idle - true -
svm_yellow:yellow_share_CIFS_volume
DP svm_blue:svm_yellow_yellow_share_CIFS_volume_mirror
Snapmirrored
Idle - true -
3 entries were displayed.
E4-7 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. From the clustershell on svl-nau, enter the following command to check the vserver-dr-
protection flag for each of the volumes associated with SVM svm_yellow:
svl-nau::> volume show -vserver svm_yellow -fields
vserver-dr-protection
Sample output:
vserver volume vserver-dr-protection
---------- --------------------- ---------------------
svm_yellow exp_yellow_NFS_volume protected
svm_yellow exp_yellow_NFS_volume_clone_14072016_164416_58
protected
svm_yellow svm_yellow_root unprotected
svm_yellow yellow_share_CIFS_volume
protected
svm_yellow yellow_thickvol protected
svm_yellow yellow_thinvol protected
svm_yellow yellow_usr_001 protected
svm_yellow yellow_usr_002 protected
8 entries were displayed.
7. As mentioned earlier, there are eight volumes in svm_yellow. Only five volumes
should be mirrored. To remove a volume from mirroring considerations, set the
vserver-dr-protection flag to unprotected.
8. From the clustershell on svl-nau, enter the following command to remove the two volumes from
mirroring consideration (your cloned volume might have a slightly different name).
svl-nau::> volume modify -vserver svm_yellow -volume
exp_yellow_NFS_volume_clone_14072016_164416_58,yellow_share_CIFS_volume
-vserver-dr-protection unprotected
Sample output:
Volume modify successful on volume
exp_yellow_NFS_volume_clone_14072016_164416_58 of Vserver svm_yellow.
Volume modify successful on volume yellow_share_CIFS_volume of Vserver
svm_yellow.
2 entries were modified.
9. From the clustershell on rtp-nau, enter the following command to initialize the SnapMirror
relationship:
Rtp-nau::> snapmirror initialize -destination-path svm_yellow_dr:
E4-8 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. Enter the following command to review the progress of the SVM SnapMirror relationship
transfer:
rtp-nau::> snapmirror show -expand
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_red:red_share_CIFS_volume
XDP svm_blue:svm_red_red_share_CIFS_volume_vault
Snapmirrored
Idle - true -
svm_yellow: DP svm_yellow_dr:
Uninitialized
Transferring - true -
svm_yellow:yellow_share_CIFS_volume
DP svm_blue:svm_yellow_yellow_share_CIFS_volume_mirror
Snapmirrored
Idle - true -
3 entries were displayed.
E4-9 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
11. Continue to check the status until the state changes to Snapmirrored:
rtp-nau::> snapmirror show -expand
Sample output:
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_red:red_share_CIFS_volume
XDP svm_blue:svm_red_red_share_CIFS_volume_vault
Snapmirrored
Idle - true -
svm_yellow: DP svm_yellow_dr:
Snapmirrored
Idle - true -
svm_yellow:exp_yellow_NFS_volume
DP svm_yellow_dr:exp_yellow_NFS_volume
Snapmirrored
Idle - true -
svm_yellow:yellow_share_CIFS_volume
DP svm_blue:svm_yellow_yellow_share_CIFS_volume_mirror
Snapmirrored
Idle - true -
svm_yellow:yellow_thickvol
DP svm_yellow_dr:yellow_thickvol
Snapmirrored
Idle - true -
svm_yellow:yellow_thinvol
DP svm_yellow_dr:yellow_thinvol
Snapmirrored
Idle - true -
svm_yellow:yellow_usr_001
DP svm_yellow_dr:yellow_usr_001
Snapmirrored
Idle - true -
svm_yellow:yellow_usr_002
DP svm_yellow_dr:yellow_usr_002
Snapmirrored
Idle - true -
8 entries were displayed.
E4-10 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
12. The SnapMirror transfer can take several minutes, so you might need to issue the
command several times before the state reaches Snapmirrored for all volumes.
13. The snapmirror show expand command shows the SnapMirror relationships
between SVMs and volumes of SVMs, but you can act on only the SnapMirror
relationship at the SVM level.
14. Enter the following command to examine the name of the Snapshot copy that was created for the
SVM SnapMirror transfer:
rtp-nau::> snapmirror show -vserver svm_yellow_dr -fields
newest-snapshot,state
Sample output:
source-path destination-path state newest-snapshot
----------- ---------------- ------------ -------------------------------------
-----------------------------
svm_yellow: svm_yellow_dr: Snapmirrored vserverdr.1.b9e09f6a-54fc-11e6-9b32-
0050560b40cd.2016-07-29_060513
15. The names of Snapshot copies for an SVM SnapMirror relationship start with
vserverdr.
16. Enter the following command to examine the namespace of the svm_finance_dr SVM:
rtp-nau::> volume show -vserver svm_yellow_dr -fields junction-path,
policy
Sample output:
vserver volume policy junction-path
------------- --------------------- ------- ----------------------
svm_yellow_dr exp_yellow_NFS_volume default /exp_yellow_NFS_volume
svm_yellow_dr svm_yellow_root default /
svm_yellow_dr yellow_thickvol default /vol_14072016_160139_42
svm_yellow_dr yellow_thinvol default /yellow_thinvol
svm_yellow_dr yellow_usr_001 default /usr001
svm_yellow_dr yellow_usr_002 default /yellow_usr_002
6 entries were displayed.
17. Notice that a new root volume is created automatically for the SVM.
E4-11 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
18. Enter the following command to examine the export-policy rules of the svm_yellow_dr SVM:
rtp-nau::> vserver export-policy rule show -vserver svm_yellow_dr
Sample output:
Policy Rule Access Client RO
Vserver Name Index Protocol Match Rule
------------ --------------- ------ -------- --------------------- ---------
svm_yellow_dr
default 1 any 0.0.0.0/0 any
19. Enter the following command to examine the SMB shares of the svm_yellow_dr SVM:
rtp-nau::> vserver cifs share show -vserver svm_yellow_dr
Sample output:
Vserver Share Path Properties Comment ACL
-------------- ------------- ----------------- ---------- -------- -----------
svm_yellow_dr admin$ / browsable - -
svm_yellow_dr c$ / oplocks -
BUILTIN\Administrators / Full Control
browsable
changenotify
show-previous-versions
svm_yellow_dr ipc$ / browsable - -
3 entries were displayed.
20. Enter the following command to examine the data logical interface (LIF) of the svm_yellow_dr
SVM:
rtp-nau::> network interface show -vserver svm_yellow_dr
Sample output:
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
svm_yellow_dr
svm_yellow_cifs_nfs_lif1
up/down 192.168.0.62/24 rtp-nau-01 e0c true
svm_yellow_cifs_nfs_lif2
up/down 192.168.0.63/24 rtp-nau-01 e0c true
2 entries were displayed.
21. The data LIF should have the same IP address and network mask as the svm_yellow
SVM on the primary cluster. However, the home port for the LIF might be different
from the home port on the source cluster and might be different from what is shown
in this guide. This difference might exist because the SnapMirror SVM feature does a
best effort at LIF placement and has its own set of rules for home-port selection of the LIF.
E4-12 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
22. From the disaster-recovery SVM, you cannot access or view the contents of the
shares and volumes because you are using identity-preserve mode. If you need
to be able to access the data in a read-only capacity while the primary cluster is
actively serving data, you must set identity-preserve mode to false.
E4-13 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. This task requires commands be entered on both svl-nau and rtp-nau. You should be
aware of the cluster prompt (svl-nau::> and rtp-nau::>) on which each
command is entered.
2. From the clustershell on rtp-nau, enter the following command to quiesce SnapMirror transfers:
rtp-nau::> snapmirror quiesce -destination-path svm_yellow_dr:
3. Enter the following command to verify that the SnapMirror software was quiesced:
cluster2::> snapmirror show
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_red:red_share_CIFS_volume
XDP svm_blue:svm_red_red_share_CIFS_volume_vault
Snapmirrored
Idle - true -
svm_yellow: DP svm_yellow_dr:
Snapmirrored
Quiesced - true -
svm_yellow:yellow_share_CIFS_volume
DP svm_blue:svm_yellow_yellow_share_CIFS_volume_mirror
Snapmirrored
Idle - true -
3 entries were displayed.
4. Enter the following command to break the SnapMirror relationship before you activate the
disaster recovery SVM:
rtp-nau::> snapmirror break -destination-path svm_yellow_dr:
E4-14 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
5. Enter the following command to verify that the SnapMirror relationship is in the Broken-off
state:
rtp-nau::> snapmirror show
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_red:red_share_CIFS_volume
XDP svm_blue:svm_red_red_share_CIFS_volume_vault
Snapmirrored
Idle - true -
svm_yellow: DP svm_yellow_dr:
Broken-off
Idle - true -
svm_yellow:yellow_share_CIFS_volume
DP svm_blue:svm_yellow_yellow_share_CIFS_volume_mirror
Snapmirrored
Idle - true -
3 entries were displayed.
7. This exercise uses the identity-preserve mode for the SnapMirror SVM
relationship, and the primary and disaster-recovery SVMs are on the same network
subnet. Therefore, you must stop the source SVM before you activate the destination
SVM.
E4-15 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
9. From the clustershell on rtp-nau, enter the following command to activate the disaster-recovery
SVM:
rtp-nau::> vserver start -vserver svm_yellow_dr
Sample output:
[Job 41] Job succeeded: DONE
10. Enter the following command to verify that the SVM started:
rtp-nau::> vserver show svm_yellow_dr -fields
admin-state,operational-state
Sample output:
vserver admin-state operational-state
------------- ----------- -----------------
svm_yellow_dr running running
11. Because the same subnet is used, no LIFs need to be updated. When the SVM is
activated, the client can access the CIFS share. You verify client access in the
following steps.
12. You must unmount and remount NFS clients to access the volumes from the disaster-
recovery SVM.
13. On the Windows Server desktop, use Windows File Explorer to map a drive letter to the CIFS
share on svm_yellow_dr on rtp-nau.
E4-16 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
14. The c$ share is the administrative hidden share of the root of the namespace.
You should see folders representing the junction paths to the other volumes involved
in the SVM DR SnapMirror relationship.
15. Enter the following command to view the svm_yellow_dr junction paths and policy:
rtp-nau::> volume show -vserver svm_yellow_dr -fields junction-path,policy
Sample output:
vserver volume policy junction-path
------------- --------------------- ------- ----------------------
svm_yellow_dr exp_yellow_NFS_volume default /exp_yellow_NFS_volume
svm_yellow_dr svm_yellow_root default /
svm_yellow_dr yellow_thickvol default /vol_14072016_160139_42
svm_yellow_dr yellow_thinvol default /yellow_thinvol
svm_yellow_dr yellow_usr_001 default /usr001
svm_yellow_dr yellow_usr_002 default /yellow_usr_002
6 entries were displayed.
16. Verify that you can write data to the volume by copying the File_240M from the CourseFiles
folder to the yellow_usr_002 folder (volume).
E4-17 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. On a live production system, you need to verify all of the items that you did when
you first created the SnapMirror SVM relationship. For example, on the primary
cluster you must verify the existence of the following:
2. Enter the following command to create a reverse SnapMirror relationship so that the primary
SVM becomes the destination and the disaster-recovery SVM becomes the source:
svl-nau::> snapmirror create -source-path svm_yellow_dr:
-destination-path svm_yellow: -type DP -throttle unlimited -policy
DPDefault -schedule hourly -identity-preserve true
3. Enter the following command to verify that the SnapMirror relationship was created (the state is
Broken-off):
svl-nau::> snapmirror show -vserver svm_yellow
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_yellow_dr:
DP svm_yellow: Broken-off
Idle - true -
4. Enter the following command to resynchronize all changes (configuration and data) that have
occurred on the disaster-recovery SVM since it became the active SVM:
svl-nau::> snapmirror resync svm_yellow:
E4-18 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
5. Enter the following command to verify that the SnapMirror resynchronization has finished:
svl-nau::> snapmirror show -vserver svm_yellow
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_yellow_dr:
DP svm_yellow: Snapmirrored
Idle - true -
6. You might need to enter this command several times for the state to reach the final
Snapmirrored state. Before reaching the Snapmirrored state, the
resynchronization is in the Transferring state.
E4-19 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. The system might need to operate in the reverse relationship for some time before
switching back to the original configuration. In that configuration, the primary SVM
again is the active SVM for the clients. You must plan this activity because there is a
short client outage during switchback. Also, during this time, an administrator might
apply SVM configuration changes based on new business requirements.
In the next steps, you switch the primary and disaster-recovery SVMs back to their original
configuration, in which the primary SVM is the active SVM.
2. From the clustershell on rtp-nau, enter the following command to stop the disaster-recovery
SVM:
rtp-nau::> vserver stop -vserver svm_yellow_dr
Sample output:
[Job 42] Job succeeded: DONE
4. From the clustershell on svl-nau, enter the following command to make one final update to
transfer all of the most recent data changes and configuration changes to the primary SVM:
svl-nau::> snapmirror update -destination-path svm_yellow:
5. Enter the following command to verify that the SnapMirror update has finished:
svl-nau::> snapmirror show -vserver svm_yellow
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_yellow_dr:
DP svm_yellow: Snapmirrored
Idle - true -
E4-20 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
7. Enter the following command to verify that the SnapMirror relationship is in the Broken-off
state:
svl-nau::> snapmirror show -vserver svm_yellow
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_yellow_dr:
DP svm_yellow: Broken-off
Idle - true -
8. Enter the following command to restore the original relationship and to delete the SnapMirror
relationship:
svl-nau::> snapmirror delete -destination-path svm_yellow:
9. Enter the following command to verify that the SnapMirror relationship was removed:
svl-nau::> snapmirror show -vserver svm_yellow
Sample output:
There are no entries matching your query.
11. On the Windows Server, verify the SMB access, open Windows File Explorer, and navigate to
the drive letter mapped to c$ (\\192.168.0.62) (V:):
E4-21 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
13. From the clustershell on rtp-nau, enter the following command to verify that the original
SnapMirror relationship exists and is in the Broken-off state:
rtp-nau::> snapmirror show
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_red:red_share_CIFS_volume
XDP svm_blue:svm_red_red_share_CIFS_volume_vault
Snapmirrored
Idle - true -
svm_yellow: DP svm_yellow_dr:
Broken-off
Idle - true -
svm_yellow:yellow_share_CIFS_volume
DP svm_blue:svm_yellow_yellow_share_CIFS_volume_mirror
Snapmirrored
Idle - true -
3 entries were displayed.
E4-22 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
15. Enter the following command to verify that the SnapMirror resynchronization has finished:
rtp-nau::> snapmirror show
Sample output:
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm_red:red_share_CIFS_volume
XDP svm_blue:svm_red_red_share_CIFS_volume_vault
Snapmirrored
Idle - true -
svm_yellow: DP svm_yellow_dr:
Snapmirrored
Idle - true -
svm_yellow:yellow_share_CIFS_volume
DP svm_blue:svm_yellow_yellow_share_CIFS_volume_mirror
Snapmirrored
Idle - true -
3 entries were displayed.
16. You might need to enter this command several times for the state to reach the final
Snapmirrored state. Before reaching the Snapmirrored state, the
resynchronization is in the Transferring state.
END OF EXERCISE
E4-23 ONTAP Data Protection Administration: Disaster Recovery for Storage Virtual Machines
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
OBJECTIVES
This exercise focuses on enabling you to do the following:
Create a schedule job to be used to automate SnapVault updates
Use an existing Snapshot policy
Create and initialize a SnapVault relationship with the SnapVault policy and schedule
Update the SnapVault secondary manually
Verify data transfer
Restore data using SnapVault
1. On svl-nau, click the SVMs button, select the svm_red link, and then click the Volumes button.
E5-1 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
E5-2 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
4. In the Destination Volume area, next to Storage Virtual Machine, click Browse.
5. The two clusters are currently in a peer relationship. The svm_red storage virtual
machine (SVM) is not in a peer relationship with any SVM on the rtp-nau cluster.
You must create the peer relationship between SVMs before a SnapVault relationship
can be created.
E5-3 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. In the Select Destination Storage Virtual Machine window, click the Authenticate link.
7. In the Authentication window, enter the admin credentials of remote cluster rtp-nau, and click
OK.
E5-4 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
9. In the Select Destination Storage Virtual Machine window, select the svm_blue SVM, and then
click the Peer and Continue button.
E5-5 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
10. In the Create Protection Relationship window, complete the configuration as follows:
Destination Volume
Select the New Volume radio button.
Volume Name: Keep the default name.
Aggregate: rtp01_fcal_002
Enable dedupe: Select the checkbox.
Configuration Details
Vault Policy: XDPDefault
Schedule: daily
Initialize Relationship: Select the checkbox.
12. ONTAP software automatically selects a schedule with a SnapMirror label and
matches that SnapMirror label for the new SnapVault policy.
To change the schedule, you can create another schedule with the same SnapMirror
label and then you edit the SnapVault policy to use the new schedule.
E5-6 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
13. In the Create Protection Relationship window, ensure that the status items have all finished or
started successfully, and then click OK.
E5-7 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
15. Ensure that the newly created SnapVault relationship is healthy and has a relationship type and
policy type of Vault.
E5-8 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. You need to test the SnapVault replication, so you open Windows File Explorer, and
you map a drive letter to the share on the svm_red SVM.
2. In Windows File Explorer, right-click Network, and then select Map network drive.
3. In the Map Network Drive window, in the Folder field, enter the path to the share.
The format for the folder path is \\<data_lif_for_smb_red>\<share_name>
4. Click Finish.
E5-9 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
5. In the CourseFiles folder on the Windows Desktop, copy the File_240M file into the red_share
folder.
6. Instead of waiting for the SnapVault update schedule, create a Snapshot copy to use for the
manual update:
a. On svl-nau, click the Volumes button.
b. Select the red_share_CIFS_volume, and then click Snapshot Copies > Create.
c. In the Create Snapshot Copy window, enter the Snapshot Copy Name: SnapVault_Update.
d. Click Create.
E5-10 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
11. Mount the volume created on the svm_blue SVM by the Vault relationship into the SVM
namespace:
a. Click the SVMs button, and then click the svm_blue link.
b. Click the Namespace button.
c. In the Namespace window, click Mount.
d. In the Mount Volume window, click the down-arrow in the Volume Name field and select
the svm_red_red_share_CIFS_volume_vault volume.
e. Accept the default settings for Junction Name and Junction Path.
f. Click Mount.
E5-11 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
12. Using Windows File Explorer, click the drive letter mapped to the blue_root share (Z:).
END OF EXERCISE
E5-12 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
1. To simulate data loss, delete the File_240M file from the red_share (X:).
2. On rtp-nau, on the Protection > Relationships window, select the vault relationship, and click
Operations > Restore.
E5-13 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
4. Because the policy assigned to this SnapVault relationship has a job schedule
configured for daily updates, it is necessary to restore from the Snapshot copy taken
more recently.
E5-14 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
6. With Windows File Explorer, return to the red_share folder, and ensure that the file deleted in
Step 1 has been restored.
END OF EXERCISE
E5-15 ONTAP Data Protection Administration: Disk-to-Disk Backup with SnapVault Software
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.