Cloning a datastore

The NetApp Element Plug-in for vCenter Server provides the functionality to clone datastores, which includes mounting the new datastore to the desired ESXi server or cluster. You can name the datastore clone and configure its QoSSIOC, volume, host, and authorization type settings.

1. Select NetApp Element Management > Management.
   Note: If two or more clusters are added, ensure that the cluster you intend to use for the task is selected in the navigation bar.
2. From the Datastores page, select the check box for the datastore you want to clone.
3. Click Actions.
4. In the resulting menu, click Clone.
   Note: If you attempt to clone a datastore that contains virtual machines with attached disks not located on the selected datastore, copies of the virtual machines on the cloned datastore will not be added to the virtual machine inventory.
5. Enter a datastore name.
   Tip: Use a unique name for each datastore in a data center. For multiple cluster or vCenter Server environments, use descriptive naming best practices.
6. Click Next.
7. Select one or more required hosts for the datastore.
   Note: You need at least one connected host before you can create a new datastore. If your host has multiple initiators, select an initiator or the host to select all initiators. If you are using vCenter Linked Mode, only hosts available to the vCenter Server to which the cluster is assigned are available to select.
8. Click Next.
9. In the Configure Volume pane, do the following:
   Note: Volume size for the clone datastore matches the size of the volume backing the source datastore. By default, 512 byte emulation is set to ON for all the new volumes.
   1. Enter a name for the new NetApp Element volume that backs the clone datastore.
   2. Select a user account from the account drop-down list.
      Note: You need at least one existing user account before you can create a new volume.
   3. In the Quality of Service area, do one of the following:
      • Under Policy, select an existing QoS policy, if available.
      • Under Custom Settings, set customized minimum, maximum, and burst values for IOPS or use the default QoS values.

      Attention: QoS policies are best for service environments, for example, with database, application, or infrastructure servers that rarely reboot and need constant equal access to storage. Custom QoSSIOC automation is best for light use VMs, such as virtual desktops or specialized kiosk-type VMs, that may be rebooted, powered on, or powered off daily or several times a day. QoSSIOC automation and QoS policies should not be used together.

      Attention: Volumes that have a Max or Burst IOPS value greater than 20,000 IOPS might require high queue depth or multiple sessions to achieve this level of IOPS on a single volume.
10. Click Next.
11. Configure authorization type for host access by selecting one of the following options:
    • Use Volume Access Group
    • Use CHAP

    Note: Use the volume access group authorization type to explicitly limit which initiators can see volumes. Use CHAP for secure secret-based access with no limits on initiators.
12. Click Next.
13. If you selected Use Volume Access Group, configure the volume access groups for the selected hosts.
    The volume access groups listed in Required by Selected Initiators are already associated with one or more of the host initiators you selected in an earlier step.
    1. Select additional volume access groups or create new ones to associate with available initiators:
       • Available: Other volume access group options in the cluster.
       • Create New Access Group: Enter the name of the new access group and click Add.
    2. Click Next.
    3. In the Configure Hosts' Access pane, associate available host initiators (IQN or WWPN) with the volume access groups you selected in the previous pane.
       If a host initiator is already associated with a volume access group, the field is read-only for that initiator. If a host initiator does not have a volume access group association, select an option from the drop-down list next to the initiator.
    4. Click Next.
14. If you want to enable QoSSIOC automation, click the Enable QoS & SIOC check box to select it and then configure the QoSSIOC settings.
    Attention: If you are using QoS policies, do not enable QoSSIOC. QoSSIOC will override and adjust QoS values for volume QoS settings.

    Note: If the QoSSIOC service is not available, you must first configure settings on the QoSSIOC Settings page from the NetApp Element Configuration extension point.
    1. Select Enable QoS & SIOC.
    2. Configure the Burst Factor.
       Note: The burst factor is a multiple of the IOPS limit (SIOC) setting for the VMDK. If you change the default, make sure to use a burst factor value that will not exceed the maximum burst limit for a NetApp Element volume when the burst factor value is multiplied by the IOPS limit for any VMDK.
    3. Optional: Select Override Default QoS and configure the settings.
       Note: If the Override Default QoS setting is disabled for the datastore, the Shares and Limit IOPS values are automatically set based on the default SIOC settings of each VM.

       Tip: Do not customize the SIOC share limit without also customizing the SIOC IOPS limit.

       Tip: By default, the maximum SIOC disk shares are set to Unlimited. In a large VM environment such as VDI, this can lead to overcommitting maximum IOPS on the cluster. When you enable QoSSIOC, always check the Override Default QoS and set the Limit IOPS option to something reasonable.
15. Click Next.
16. Confirm the selections and click Finish.
17. Refresh the view if the datastore clone does not appear in the list.