Associating a data protection, disaster recovery, or provisioning policy with a dataset lets storage administrators automate tasks, such as assigning consistent policies to primary data, propagating policy changes, and provisioning new volumes, qtrees, or LUNS on primary and secondary dataset nodes. The licenses that you have installed determine which policies are available.
Configuring a dataset combines the following objects:
- Dataset
- For protection purposes, a dataset is a collection of physical resources on a primary node, such as volumes, flexible volumes, and qtrees, and the physical resources for copies of backed-up data on secondary and tertiary nodes.
For provisioning purposes, a dataset is a collection of physical resources, such as volumes, flexible volumes, qtrees, and LUNs, that are assigned to a dataset node. If the protection license is installed and the protection policy establishes a primary and one or more nonprimary nodes, each node of the dataset is a collection of physical resources that might or might not be provisioned from the same resource pool.
- Resource pool
- A collection of physical resources from which secondary storage is provisioned. Resource pools can be used to group storage systems and aggregates by attributes, such as performance, cost, physical location, or availability.
- Data protection policy
- A data protection policy defines how to protect the primary, secondary, and tertiary storage, as well as when to create copies of data and how many copies to keep.
- Storage service
- A storage service is a single dataset configuration package that consists of a protection policy, provisioning policies, resource pools, and an optional vFiler template (for vFiler unit creation). You can assign a single uniform storage service to datasets with common configuration requirements as an alternative to separately assigning the same protection policy, provisioning policies, resource pools, and setting up similar vFiler unit attachments to each of them.
