Create, map and protect Clustered Data ONTAP LUNs with
SnapMirror
Goal
This
workflow will automate the creation of up to 20 LUNs. This workflow
performs the following:
·
Creates
a new primary volume on the selected Clustered ONTAP cluster and Storage Virtual
Machine
·
Create
up to 20 LUN of the same size in the new primary volume
·
Map
the LUNs to an existing or a newly created iGroup as selected by the user.
·
Create
a secondary volume of the same size as the primary on the selected secondary
Clustered ONTAP cluster and Storage Virtual Machine
·
Establish
a Volume SnapMirror relationship between the primary and secondary volume
·
Initiate
the baseline transfer for the new VSM relationship
Pre-requisites:
·
Cluster
peer is required in case the SnapMirror secondary cluster is a different
cluster than primary. Cluster peering between primary and secondary clusters
can be established using "Establish Cluster Peering" sample workflow.
·
Storage
Virtual Machine peer is required in case SnapMirror secondary Storage Virtual
Machine is a different Storage Virtual Machine than primary, and both primary
and secondary clusters are running ONTAP version 8.2.0 or above. Storage
Virtual Machine peering between primary and secondary Storage Virtual Machines
can be established using "Create Storage Virtual Machine peer"
command in a custom workflow.
LUN
Details Input parameters:
The
LUN Details input section identifies all of the inputs required for the Volume,
LUNs, and expected sizes. All user inputs in this section are required.
1)
Primary Cluster
Clustered ONTAP storage system where the
LUNs will be created. The aggregate chosen will have the largest
available capacity, and under an over commitment percentage of 300.
List of available clusters are provided
in the drop-down list and will show the Names of the clusters and their Primary
IP Addresses
NOTE: Only clusters with a
“SnapMirrorDP” license enabled will be shown
2)
Primary Storage Virtual Machine – The Storage Virtual Machine where the new
volume will be created. The list of Primary Storage Virtual Machines for
the selected Primary Cluster are provided in the drop-down list
3)
Primary Volume Name
The name you would like to use for the
Primary Volume that will be created. The size of the volume is calculated
from the number of LUNs selected, along with the capacity selected for LUN size
and Snapshot size.
4)
Number of LUNs
Number of LUNs to be provisioned. The
range is currently set at 1 – 20 LUNs
5)
LUN Prefix Name
This is the naming prefix you would like
to use for the LUNs. The LUN Name will be appended with the incrementing
number of LUNs selected to create
Example: The LUN
Prefix is given as lunP, and Number of LUNs to be created is 3
Results: The names of
LUNs created will be lunP_1, lunP_2, lunP_3
6)
LUN Size (GB)
The size in GB for each LUN.
7)
LUN Snapshot Size (GB)
The size in GB to set aside for
snapshots for each LUN
Protocol
Details Input parameters:
The
Protocol Details input section identifies all of the inputs required in regards
to the protocol, LUN and iGroup configuration
1)
Protocol (required)
This is where you specify if you would
like FCP, iSCSI, or Mixed for the access protocol to the LUNs
2)
LUN OS Type (required)
Specify the LUN Type you would like to
create. The drop-down list provides all of the valid LUN Types
3)
IGroup Name (required)
Identify the Initiator Group (iGroup)
where the LUNs will be mapped. You can either chose an iGroup from the
list available for the selected Storage Virtual Machine, or you can identify a
new iGroup that will be created for the selected Storage Virtual Machine. If a
new iGroup is created, it will be of the protocol and OS type selected by the
previous user inputs.
4)
List of Initiators
List of initiators that need visibility
to the LUNs. These initiators will be added to the iGroup if it is being
created only. This input is optional if an existing iGroup is selected in the
previous user input.
Example: iSCSI initiator names like
“iqn.1991-05.com.microsoft:abc.company.com” or HBA worldwide port names (WWPNs)
like 20:00:00:00:c9:2b:8e:4f or 200c0050a57367fc.
5)
LUN ID
Starting LUN id of the range of IDs to
be used for LUN mapping. If not provided, ONTAP will assign the next highest
number as the LUN Id.
6)
Portset Name
Name of the Portset for the selected
Storage Virtual Machine to which a newly created iGroup will be bound. This
input is considered, only when a new iGroup is created. This input is optional
and if not provided, the newly created iGroup will not be bound to any portset.
Protection
Details Input parameters:
The
Protection Details input section identifies the secondary cluster, Storage
Virtual Machine, and volume to use as the Volume SnapMirror destination.
All inputs in this section are required.
1)
Secondary Cluster
Clustered ONTAP storage system where the
primary volume and LUNs will be replicated. The aggregate chosen will
have the largest available capacity, and a storage efficiency over-commitment
percentage less than 300.
List of available clusters are provided
in the drop-down list and will show the Names of the clusters and their Primary
IP Addresses
NOTE: Only clusters with a
“SnapMirrorDP” license enabled will be shown
2)
Secondary Storage Virtual Machine
The Storage Virtual Machine that will
host the destination volume for the Volume SnapMirror relationship. The
list of Secondary Storage Virtual Machines for the selected Secondary Cluster
are provided in the drop-down list
3)
Secondary Volume Name
The name of the destination volume for
the Volume SnapMirror relationship
4)
Schedule for SnapMirror
The replication schedule to use for the
SnapMirror relationship. The list of default SnapMirror schedules is
provided via the dropdown list. It is possible to provide an alternate
SnapMirror schedule that is available to the Storage Virtual Machine
Result
The
workflow will result in creating the requested number of LUNs in the desired
Clustered ONTAP cluster and Storage Virtual Machine. The LUNs will be
mapped per the user input criteria, and a SnapMirror relationship will be
applied and a baseline transfer is initiated to protect the newly provisioned
LUNs.
Error
Handling
1)
An
error message is displayed if there is no aggregate on the specified cluster(s)
with sufficient capacity to fulfill the storage-provisioning and/or
storage-protection request.