Create SnapVault
Goal
This workflow
automates the creation of SnapVault relationship for a specific volume. The
workflow will select a suitable aggregate for provisioning the destination
volume from a resource pool, which is an optional parameter as part of the user
input. If resource pool is not specified (value = "NONE") then, all
available aggregates on the specified destination cluster are considered for
provisioning. This workflow will perform the following –
§ node.priority,
ascending (returned by Get all aggregates by node priority and volume count) –
This is for fault domain separation across nodes
§ node.volume_count,
ascending (returned by Get all aggregates by node priority and volume count) –
This is for load balancing across the nodes of the cluster
§ available_capacity,
descending, (returned by Filter aggregates by available capacity) – This is for
capacity balancing across aggregates
Create SnapVault
User Inputs:
As
part of the “Create SnapVault” workflow, the following mandatory and optional
user inputs are supplied,
This
is the cluster where primary volume resides. It’s mandatory that it must be
running Clustered Data ONTAP 8.2 or later. The lists of available clusters are
displayed in the drop-down list showing cluster name, primary address and ONTAP
version.
§ Storage Virtual
Machine*: Storage Virtual Machine Name [Mandatory]
Select
the primary Storage Virtual Machine name to which volume belongs. The list of
available Storage Virtual Machine is displayed in the drop-down list for
selection.
This
is the primary volume to be protected. As part of the cluster and selected
primary Storage Virtual Machine only, the list of volume is populated in the
drop-down list for selection. This list will have Volume name, aggregate, used
size, total size, and space guarantee information.
Provide the snapshot policy to be assigned to the
primary volume. Policy describes the schedules and retention counts for the
local Snapshot copies. Available snapshot policy list that can be used from the
specified primary Storage Virtual Machine only is displayed with a drop-down
list showing policy name, snapshot schedules, snapshot counts and Snapmirror
labels (comma separated list). It’s important to note that the list includes
cluster-scoped policies and the policies scoped to the primary Storage Virtual
Machine as well.
Note: This is an optional input and an empty policy
named “NO CHANGE” is provided to allow keeping the existing policy.
Resource Pool*:
SnapVaultDestinationResourcePool [Mandatory]
Provide the resource
pool for provisioning the SnapVault destination volume. If specified, the
destination aggregate is selected from this resource pool. If value
"NONE" is specified, all available aggregates in the cluster will be
considered for the resource selection. The list of available resource pools is
displayed in the drop-down list and will show resource pool name, number of
aggregates, % used total capacity. There is an included value “NONE” which will
facilitate a way to specify no selection.
Cluster*: SnapVaultDestinationClusterName
[Mandatory]
Select the
Cluster to be used for provisioning the SnapVault destination volume. If a
resource pool is specified, this input will be automatically selected based on
the aggregates in the specified pool. If no resource pool is specified (value =
"NONE"), any available cluster can be selected. As part of the
selection, a drop-down list with cluster name, primary address and ONTAP
version is listed. All selected resources result will be ONTAP 8.2 and later
clusters only.
Storage Virtual
Machine*: SnapVaultDestination Storage Virtual Machine Name, 8.2 only
[Mandatory]
Select the
Storage Virtual Machine for the SnapVault destination volume. For selection, a
list of available Storage Virtual Machine on the destination cluster is
displayed. It’s important to note that only ‘data’ Storage Virtual Machines are
shown only.
Policy: Schedule
to be attached to the relationship [Optional].
Select
the Policy to be attached to the new SnapVault relationship. The policy has
rules that specify which snapshots are transferred from the source to the
SnapVault destination and also the retention count for the transferred
snapshots. The policy must have at least one rule. For selection, a drop-down
list showing policy name, snapshot labels, and snapshot counts for that policy
(comma separated list) is listed. It’s important to note that –
o Only the
policies that can be used from the specified destination Storage Virtual
Machine
o Only the
policies that have at least one rule (SnapVault Restriction)
o A policy by name
“NONE” is provided to omit any policy selection.
Transfer
Schedule: SnapVaultSchedule to
be attached to the relationship [Optional].
Select the
Schedule for transferring snapshots to the SnapVault destination. For
selection, a drop-down list showing schedule name and description is displayed
(as generated by ONTAP). It’s important to note that-
o Only the
schedules on the destination cluster are selected.
o A schedule by
name “NONE” is provided to omit any schedule selection.
Result
This workflow
when executed will protect the selected primary volume by provisioning the
SnapVault destination volume and will apply the chosen SnapVault relationship
policy and transfer schedule.
Potential
Workflow Extensions
This workflow is
provided just as a sample. The possible customization would be –
·
For
customizing the available set of schedules and policies, you can do so as
described in Create Schedules and Policies workflow.
·
You
can clone the certified workflow and assign fixed schedules, policies and/or
resource pools to the workflow.
·
This
workflow can be a reference workflow for creating a Fan-out mirror. Note that
this will be a separate workflow.
·
One
should be able to clone the topology workflow to create custom topologies like
Mirror to four destinations.