SnapVault is a disk-to-disk backup technology that operates at the qtree level. A SnapVault relationship is established between a source qtree on a primary storage system and a destination volume on a secondary system. The backed-up data is stored within a destination qtree on the secondary system. This qtree-based operation allows for granular, policy-based backups of specific data sets within a volume, making the qtree the fundamental unit for SnapVault backup and restore operations.

A. The file is the basic unit for SnapVault backup destination.

Incorrect. While individual files are contained within the backup, the SnapVault relationship and policy are managed at the qtree level, not the file level.

C. The volume is the basic unit of SnapVault backup destination.

Incorrect. Volume-level replication is the primary function of SnapMirror. SnapVault provides more granular, qtree-level backup capabilities within a volume.

D. The directory is the basic unit for SnapVault backup destination.

Incorrect. While a qtree is a special type of directory, "qtree" is the specific and correct NetApp term for the managed unit. This option is too generic.

1. NetApp ONTAP 9.7 Data Protection Guide

Page 13

"How SnapVault backups work". The guide states

"You can back up data from a specific qtree or from an entire volume... When you back up a volume

ONTAP creates a qtree for the volume on the destination." This confirms the qtree as the fundamental container on the destination.

2. NetApp Technical Report TR-4015: SnapMirror Configuration and Best Practices Guide for ONTAP 9.1

9.2

Page 11

Section 2.2 "SnapVault". It describes

"SnapVault is a backup technology that creates a Snapshot copy of a specified qtree or volume on the primary system and copies it to a qtree on the secondary system." This explicitly identifies the qtree as the operational unit.

3. NetApp ONTAP 9 Documentation Center

"Create a SnapVault relationship"

Command reference for snapmirror create. The syntax requires specifying a source path that can be a volume or qtree

and a destination path that is a qtree. For example: -source-path SVM:volume/qtree -destination-path SVM:volume/qtree. This demonstrates the qtree as the core component in the relationship definition.