96465514 22 npsa snapvault dm

NetApp Protection Software Administration: SnapVault®

NGS New Hire Technical Training

Section 5: NetApp Protection Software Administration

© 2009 NetApp. All rights reserved. 2

Module Objectives

By the end of this module, you should be able to:Describe SnapVault components and benefitsConfigure and administer SnapVault Perform advanced SnapVault operations


Module Overview

Back up multiple storage systems to a central secondary system

Minimize media consumption and system overhead through incremental backup

Allow users to browse backed-up files online to perform restoration upon request

PrimaryStorage Systems

SecondaryStorage System

SnapVault

Data Center Central Repository

SnapVault

SnapVault

FAS1

FAS2

FAS3


Theory of Operation

The qtree is the basic unit of SnapVault backup and restore

You can back up a primary qtree, non-qtree data, and volume data to a qtree on the secondary system

If necessary, data is restored from the secondary qtrees back to their associated primary qtrees

SnapVault

qtree_aqtree_b

vol1

FAS1

/vol/vol2/-

FAS2

/vol/vol3/

FAS3

Primary Storage Systems

qtree_a

qtree_b

qtree_vol2

qtree_vol3

VOL1

Secondary Storage System


Initial Transfer and Backup

The initial transfer establishes the relationship between the primary and the secondary qtrees

Incremental backup– The primary creates scheduled SnapVault

Snapshot copies of the volume containing the qtrees to be backed up

– The secondary carries out scheduled updatesChanges blocks are retrieved from the Snapshot

copy of each primary qtreeWhen all transfers are completed, the secondary

takes a Snapshot copy of its own volume containing the update of all qtrees


SnapVault Versus SnapMirror®

SnapMirror SnapVault

Deployment Data migration and replication

Data archiving

Disaster recovery

Integrated failover capability

SnapMirror/SnapVault bundle is required for failover

Cascading Supports cascading volume in a series

Cascading SnapVault qtrees replica is not supported

Snapshot copy

Does not create Snapshot copy for archiving

Provides Snapshot copy scheduling and retention on the secondary

Scheduled update frequency

Up to per minute async updates or sync

Per day or per hour updates

© 2009 NetApp. All rights reserved.

SnapVault Deployment


Prerequisites

A separate license for the primary, sv_ontap_pri, and for the secondary, sv_ontap_sec, is required– In Data ONTAP 7.3, you can install both licenses on

the same storage systemYou can increase the number of concurrent

transfers by installing the nearstore_option license

TCP port 10566 must be open on both sidesOptionally, for management tools using NDMP

(example: Protection Manager) open the NDMP port: 10000


Configuration Process

1. Install the SnapVault license

2. Set SnapVault access

3. Perform the initial baseline transfer

4. Schedule Snapshot copy creation on the primary system

5. Schedule Snapshot copy creation and incremental updates on the secondary system


snapvault snap sched

The following is an example of the snapvault snap sched command issued on the secondary system

snapvault snap sched -x vol1 sv_hourly 11@mon-fri@7-18

Secondary volume name

SnapVault Snapshot copy basename

SnapVault Snapshot copy retention count

Updates from Monday through Friday

Schedule

Used only on the Secondary-x mean update

Updates hourly from 7 a.m. to 6 p.m.


Monitoring Transfer

Use the snapvault status command to monitor transfer progress, check relationship status, and control the lagNY1> snapvault status

Snapvault secondary is ON.

Source Destination State Lag Status

Dallas:/vol/vol1/q1 NY1:/vol/vol1/q1 Snapvaulted 00:09:53 Quiescing

Dallas:/vol/vol1/q2 NY1:/vol/vol1/q2 Snapvaulted 00:15:20 (Transferring 12288 MB done)

Use the -c option to display the SnapVault qtree configuration parametersNY1> snapvault status –c

/vol/vol1/q1 source=Dallas:/vol/vol1/q1 kbs=unlimited tries=2

/vol/vol1/q2 source=Dallas:/vol/vol1/q2 kbs=10000 tries=10


Listing Snapshot Copies

Use the snap list –q command to display all Snapshot copies retained on volume and details of the qtrees contained in those Snapshot copiesNY1> snap list -q vol1

Volume vol1 working...

qtree contents date source

-------- --------- -------- -------

sv_hourly.0 (Jan 22 15:00)

q1 Replica Jan 22 15:00 Dallas:/vol/vol1/q1


sv_hourly.1 (Jan 22 16:00)




Log Files

SnapVault logs are stored on the root volume, in the /etc/log/snapmirror file

E.g. on the primarysrc Wed Jan 22 08:55:52 PDT Dallas:/vol/vol1/q1 NY1:/vol/vol1/q1 Request

(192.168.30.6)

slk Wed Jan 22 08:55:53 PDT state.qtree_softlock.vol1.000000ca.013.q1.src-

qt.NY1:/vol/vol1/q1.00000000.-01.1 Softlock_add (Transfer)

src Wed Jan 22 08:55:53 PDT Dallas:/vol/vol1/q1 NY1:/vol/vol1/q1 Start

src Wed Jan 22 08:57:31 PDT Dallas:/vol/vol1/q1 NY1:/vol/vol1/q1 End (36900 KB)

E.g. on the secondarydst Wed Jan 22 08:56:28 PDT Dallas:/vol/vol1/q1 NY1:/vol/vol1/q1 Request

(Initialize)

dst Wed Jan 22 08:56:30 PDT Dallas:/vol/vol1/q1 NY1:/vol/vol1/q1 Start

dst Wed Jan 22 08:58:08 PDT Dallas:/vol/vol1/q1 NY1:/vol/vol1/q1 End (36084 KB)


Advanced Features


Single File Restore

To restore a single file, you can copy file from a Snapshot copy using CIFS® or NFS®

Or issue the Data ONTAP ndmpcopy command from the primary system

Or use NetApp Protection Manager


Qtree Restore

To restore a backed-up qtree, use the snapvault restore command

Starting with the Data ONTAP 7.3 release, you can restore the data to an existing qtree on the primary system using:

– Baseline restore

– Incremental restore Restores data in a nondisruptive way for datasets

containing LUNs


Baseline Restore

Baseline restore can be to an existing qtree or to a non-existing qtree– For an existing qtree, the restore operation

overwrites the qtree dataprimary> snapvault restore –S

sec:/vol/volname/sec_qtree /vol/volname/pri_qtree

Restore will overwrite existing data in

/vol/volname/pri_tree.

Are you sure you want to continue (yes/no)? Yes

Transfer started.

Monitor progress with 'snapvault status' or the

snapmirror log.


Incremental Restore

Transfers only incremental changes from the secondary qtree to the specified primary qtree

Primary> snapvault restore -r –S sec:/vol/volname/sec_qtree /vol/volname/pri_qtree

Restore will overwrite existing data in /vol/volname/pri_qtree

Are you sure you want to continue (yes/no) ? Yes

Transfer started.

Monitor progress with 'snapvault status' or the

snapmirror log.

If the incremental restore fails due to lack of common Snapshot copies, attempt an in-place baseline restore


Nondisruptive Restore

SCSI connectivity to the LUNs is maintained throughout the baseline and incremental restores

– The LUNs’ attributes in the primary qtree are reserved in a temporary staging areaPrimary> lun show staging

/vol/san_vol1/Staging_19e45590-8948-11dc-bb15-00a09802437a_199999999999999999/LUN1 100m (104857600) (r/w, online, mapped)

– When the restore completed, the LUNs’ attributes are applied to the restored LUNs


Resuming SnapVault

To resume backup operations after a snapvault restore, resynchronize the relationship with the snapvault start –r command

– To cancel any further backups of the restored qtree, release the relationship

The Snapshot copy created on the primary for the restore is not deleted automatically

– Do not delete this Snapshot copy, as it is needed to resume SnapVault update transfers


LUN Clone Backup

With Data ONTAP 7.3, SnapVault is able to backup LUN clones in optimized mode using SnapDrive® for Windows® (SDW)– LUN clones are transferred as clones– Space savings with the parent LUN are preserved– Once the SnapVault relationship is handed off to

SDW, update transfers must not be run from the CLI– The backing Snapshot copy is locked on the

secondary after backup Snapshot copy is transferred


SnapVault and SnapMirror


Overview

SnapVault and SnapMirror bundle provide a consolidated data protection and DR solution– Fast and space-efficient disk-based backup

– Recover from system disaster by making any online backup copy writable

– Rapid disaster recovery from hourly, nightly, or weekly backup

– Offsite disaster recovery by replicating backups to remote sites


Integrated Backup-DR Solution

Failover: primary system fails, and clients fail over to SnapVault incremental (SnapMirror)

Failback: data is resynced, and clients fail back

Failover

Failback

SnapVault1

SnapVault executes up to hourly backups

Read-Write(with SnapMirror

License)

SV/SM Bundle

SV Primary

2

3

1 2 3


Protecting SnapVault with SnapMirror

This solution consists of replicating SnapVault based backup copies through SnapMirror to a DR site to provide:– Backup and standby service for SnapVault– Backup and restore protection for SnapVault

Data Center DR site

VolumeSnapMirror

SnapVault

SnapVault

SV/SM Bundle

Windows

SV/SM Bundle

SV/SM BundleSV/SM Bundle

SV Primary

SV Primary


Considerations

Ongoing VSM update transfer will abort if a SnapVault update is triggered before the VSM transfer has completed

Transfers fail when the storage system reaches the maximum simultaneous transfers supported

In both cases, ensure that SnapMirror and SnapVault schedules do not overlap and do not stretch


SnapMirror and SnapVault for DR

Data Center Standby DR site

In this solution, data at the production center is replicated at the volume level to a SnapMirror destination system

Then the SnapMirror replicas are protected at the qtree level to a tertiary appliance at the DR site using SnapVault

Nearby site

VolumeSnapMirror

SnapVault



SnapMirror Source

SnapMirror Source


Recover from Site and Regional Disasters

In the event of a site disaster, you can failover SnapMirror to the nearby destination system and failback without requiring a complete data transfer

If a regional disaster occurs, you can fail over SnapVault to the tertiary device and then resume vault operations after recovery

Data Center Standby DR siteNearby site

VolumeSnapMirror

SnapVault



SnapMirror Source

SnapMirror Source


Documents and References

Data ONTAP Data Protection Online Backup and Recovery Guide

SnapVault Deployment and Configuration http://www.netapp.com/library/tr/3240.pdf

SnapVault Best Practices Guide

http://www.netapp.com/library/tr/3487.pdfSnapVault Design and Implementation Guide

http://www.netapp.com/library/tr/3488.pdf SnapVault for NetBackup Deployment and

Implementation Guide

http://www.netapp.com/library/tr/3465.pdf


Module Summary


Module Summary

In this module, you should have learned:How to implement and administer SnapVaultHow SnapVault in-place and incremental restores

workHow SnapVault backs up LUN cloneHow to deploy SnapVault and SnapMirror for

disaster recovery

Exercise


Module 22: SnapVault

Estimated Time: 45 minutes


Check Your Understanding

What is the basic unit for a SnapVault backup and restore?

In Data ONTAP 7.3, you can install both the sv_ontap_pri and the sv_ontap_sec licenses on the same storage system (true or false?)

Which snapvault command and option would you use to perform an incremental restore?

Answers


Module 22: SnapVault


Check Your Understanding (Cont.)

What is the basic unit for a SnapVault backup and restore?– The qtree

In Data ONTAP 7.3, you can install both the sv_ontap_pri and the sv_ontap_sec licenses on the same storage system (true or false?)– True

Which snapvault command and option would you use to perform an incremental restore? – Primary> snapvault restore -r -S sec:/vol/volname/sec_qtree /vol/volname/pri_qtree