When configuring an Open Systems SnapVault (OSSV) backup policy in Protection Manager for a UNIX client, the dataset defines the source data to be protected. The OSSV agent installed on the UNIX host can identify and back up data at several levels of granularity. This includes specifying individual files, entire directory trees, or a high-level object representing the entire client's designated backup set. These options allow administrators to create flexible and precise backup policies tailored to specific protection requirements, from a single critical file to the whole server.

B. A qtree: A qtree is a logical partition within a NetApp volume. It is a construct of the destination NetApp storage system running ONTAP, not a native object on the source UNIX client's filesystem.

1. NetApp Protection Manager 3.1 Data Protection for Open Systems Administration Guide: In the chapter on "Creating datasets for Open Systems SnapVault

" the guide specifies the types of resources that can be added to a dataset. It explicitly lists the host (entire client)

directories

and files as valid members for UNIX clients. It makes no mention of qtrees as a source-side object.

2. NetApp TR-3487: Open Systems SnapVault (OSSV) 3.0 Best Practices Guide: This technical report details the configuration of OSSV. In the section "Configuring the OSSV Agent

" it describes the snapvault.conf file on the UNIX client

where backup paths are defined. These paths can point to a file or a directory

and Protection Manager uses this underlying mechanism to manage backups for the "entire client" by aggregating these paths.

3. NetApp OnCommand Unified Manager (Successor to Protection Manager) Documentation: While a newer product

the documentation for managing legacy OSSV relationships reiterates the same principles. The source of an OSSV backup is always a file or directory path on the open systems host. The concept of a qtree only applies to the destination volume on the NetApp controller.