Setup data protection for an Infinite Volume

 Goal

This workflow sets up a data protection mirror relationship for an Infinite Volume. This workflow will –

·         Associate a specific snapshot policy with the Infinite Volume. Enables tape backup by enabling the SnapDiff option. This creates a namespace mirror constituent on every node of the cluster.

·         Setup a SnapMirror relationship for the provided Infinite Volume and secondary (dp) Infinite Volume by performing the following steps:

a. Create a peering relationship between source and destination clusters using the existing intercluster LIFs. If a cluster peer relationship is already established, this step is skipped.

b. Create a peering relationship between the source and destination Storage Virtual Machines.

c. Establish a SnapMirror relationship between the primary and secondary Infinite Volumes.

d. Wait for SnapMirror initialization to complete.

 

Input Parameters:        

·        Primary Cluster* [Mandatory]: The Clustered ONTAP storage system hosting primary volume. Note that Infinite Volume feature is available from ONTAP 8.2.0 and above, so only those applicable clusters will be shortlisted and shown in the drop down list. This list would be a tabular resource selection showing Cluster Name, Primary Address and ONTAP version.

 

 

·         Primary Storage Virtual Machine *[Mandatory]: Storage Virtual Machine hosting the primary Infinite Volume. The query will display a tabular list having Storage Virtual Machine name, Infinite Volume name, Infinite Volume Size (TB), Infinite Volume type (without storage class/with storage class) and Tape backup Enabled (true/false). Query also ensures that only repository Storage Virtual Machines of type “data” and only those Storage Virtual Machines that contain volumes of style “infinivol”, state “online” and type “rw” are selected.

 

 

·        Snapshot Policy * [Mandatory]: Snapshot policy to be assigned to the primary volume. This policy determines the schedules, retention counts, and naming for the local snapshots. If not specified (value = NO CHANGE), the existing snapshot policy assigned to the volume is left unchanged.

 

 

·         Enable tape backups: This is a Boolean input value and when enabled, this option will create a namespace mirror constituent on every node of the cluster where a data constituent resides, unchecked by default

·         Create SnapMirror relationship: This is a Boolean input value and this option when enabled will create a SnapMirror relationship between primary and secondary Infinite Volumes. Note this option is checked by default and if unchecked, the entire SnapMirror Relationship Settings group is disabled.

 

SnapMirror Relationship Settings user input

 

 

·        Secondary Cluster *[Mandatory]: The Clustered ONTAP storage system hosting destination Storage Virtual Machine and Infinite Volume of the SnapMirror relationship. Note that Infinite Volume feature is available from ONTAP 8.2.0 and above, so only those applicable clusters will be shortlisted and shown in the drop down list. This list would be a tabular resource selection showing Cluster Name, Primary Address and ONTAP version.

·         Secondary Storage Virtual Machine * [Mandatory]: Storage Virtual Machine hosting the SnapMirror destination Infinite Volume. The query will display a tabular list having Storage Virtual Machine name, Infinite Volume name and Infinite Volume Size (TB). Query also ensures that only repository Storage Virtual Machines of type “data” and only those Storage Virtual Machines that contain volumes of style “infinivol”, state “online” and type “dp” are selected

·        Policy *[Mandatory]: The protection policy to be attached to the new SnapMirror relationship. The query will result in a tabular list showing Policy Name, Comment and Transfer Priority to the user for selection.

 

 

Transfer Schedule*[Mandatory]: Schedule for transferring snapshots to the SnapMirror destination. The tabular list will show schedule and description to the user for selection.

Result

These workflows will set-up a Data protection for an Infinite Volume. The workflow would result in creating a SnapMirror relationship between source Infinite Volume and “dp” Infinite Volume.