Create, map and protect LUNs with SnapVault

 

Goal

This workflow will automate the creation of up to 20 LUNs.  This workflow performs the following:

·         Creates a new volume on the selected storage controller

·         Create a new qtree to host each LUN

·         Create the number of LUNs selected of the appropriate type

·         Map the LUNs to an existing iGroup, or create a new iGroup if not currently existing.

·         Protect the LUNs by establishing new SnapVault relationships

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) Array

The 7-mode storage controller where you would like to create the LUNs. The aggregate chosen will be have the largest available capacity, and a storage efficiency over-commitment percentage less than 300. 

The list of available storage systems will show the name, IP Address and OS Version of the storage controller

NOTE: Only storage systems with a “SnapVaultPrimary” license enabled will be shown

2) Volume Name

The name you would like to use for the 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.

3) Number of LUNs

Number of LUNs to create.  The range is currently set at 1 – 20 LUNs

4) 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:  LUN Prefix name: NewLUN, Number of LUNs: 5

Results: LUN Names = NewLUN_1 …. newLUN_5

5) LUN Size (GB)

The size in GB for each LUN

6) Snapshot Size (GB)

The size in GB to set aside for snapshots

 

 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 or iSCSI 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)

Please 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 controller, or you can identify a new iGroup to be created

4) List of Initiators

List of comma separated initiators that need visibility to the LUNs.  These initiators will be added to the iGroup if it is being created. This is an optional input.

Exampe: iSCSI initiator names like “iqn.1991-05.com.microsoft:abc.company.com” or HBA world wide port names(WWPNs) like 20:00:00:00:c9:2b:8e:4f or 200c0050a57367fc.

5) LUN ID

The 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.

 

 Protection Details Input parameters:

The Protection Details input section identifies the secondary system and volume to use as the SnapVault destination.  All inputs in this section are required.

1) Secondary Array

The aggregate chosen will be have the largest available capacity, and a storage efficiency over-commitment percentage less than 300. 

The list of available storage systems will show the name, IP Address and OS Version of the storage controller

NOTE: Only storage systems with a “SnapVaultSecondary” license enabled will be shown

 

2) Secondary Volume.

The name of the destination volume for the SnapVault relationship

 SnapVault Schedule Details Input parameters:

The SnapVault Schedule Details input section identifies the SnapVault schedule name to be used in addition to the retention periods.

1) Schedule Name for Primary and Secondary (required)

The SnapVault schedule name that uniquely identifies the SnapVault schedule between the Primary and Secondary storage controllers

2) Retention Count for Primary and Secondary

Denotes the maximum number of most recent snapshots that will be retained by this schedule.

3) Schedule of Days for Primary and Secondary

Days of the week for which this schedule should initiate the SnapVault replication

3) Schedule of Hours for Primary and Secondary

Hours of the day for which this schedule should initiate the SnapVault replication

 

Result

The workflow will result in creating the LUNs with SnapVault protection based on the selection criteria specified.

 

Error Handling

1)       An error message is displayed if there is no storage controller or aggregate with enough capacity to fulfill the storage-provisioning and/or storage-protection request.