Create a disk

Contributors netapp-manini ciarm netapp-reenu dmp-netapp

This section describes how to create a new disk by directly specifying the disk details. For instructions on how to create a disk based on a snapshot of an existing disk, see Create a disk from a snapshot.

Before you begin
  • If block storage is available but not initialized, you will be asked to initialize it before you can create the disk. To initialize the block store, you need:

    • The subnet for the block store. If you are not familiar with your network environment, please check with you IT department for the relevant values.

    • The protocol to be used. By default, block stores have the iSCSI service enabled. Ensure that the subnet has already been created to initialize block storage services (iSCSI) for the subtenant in the specified zone. You can optionally enable the FCP service if the infrastructure allows it.

    • The disaster recovery region, zone, and schedule if you want to enable asynchronous disaster recovery DP for the disk. For more information, see Disaster recovery.

  • Identify or define the host groups to be mapped to the disk. You can also create a host group as part of the disk creation.

  • To enable asynchronous disaster recovery DP options for the disk, you must create the disk on a block store that is asynchronous disaster recovery enabled. For more information, see Disaster recovery.

  • To enable synchronous disaster recovery for a disk, create the disk in a zone that is MetroCluster-enabled.

  • You can define a backup policy to capture backups of the disk on a scheduled basis. For more information, see Backups.

  1. View the Disks list.

  2. Click Create Disk.

  3. In the Create Disk dialog box, select Create New Disk.

    Error: Missing Graphic Image

    The Create Disk page is displayed.

  4. Select the protocol for accessing the disk: iSCSI or FCP.

  5. Select the subtenant, region, and zone, and subtenant for the new disk. The block store details for the selected region, zone, and subtenant display.

  6. If block storage is not enabled in the selected zone for the selected subtenant, a message displays to initialize it.

    Error: Missing Graphic Image

  7. Click Initialize Block Storage.

  8. In the Initialize Block Storage dialog box:

    1. In the iSCSI panel, mandatorily specify the subnet.
      The iSCSI service is enabled for all disks by default.

    2. If required, enable the FCP protocol (only available if the underlying infrastructure supports it).

    3. If required, enable the Asynchronous Disaster Recovery options (enable and select Region, Zone, and Schedule).

    4. If the zone selected is MCC-enabled, the Synchronous Disaster Recovery toggle is enabled and cannot be disabled. Disks created in this block store synchronously replicate to the zone displayed in the Synchronous Disaster Recovery panel.

    5. Click Create to initialize the block store. Wait until the block store initializes. The display returns to Create Disk page.

  9. Complete the following fields:

    Field Description


    Enter the disk name.

    Disk Path

    Enter the path for the disk.

    OS Type

    Select an operating system for the disk.

    Host Groups

    This list displays existing host groups that match the protocol, OS type, subtenant and zone selected for the disk.
    Select one or more host groups.
    To define a new host group, see the next step.

  10. If required, create a new host group:

    1. Click Create Host Group. The Create Host Group dialog is displayed.

    2. Specify the Name of the host group.

    3. Add the Initiators for the group. For each initiator, specify the alias and the initiator.

    4. If required, add tags (key-value pairs) to the host group in the Tags section.

    5. Click Create. The system creates the host group and displays a message when it is successfully created.

    6. To map the newly created host group to the disk, go to the Host Groups field and select it.

  11. Select a service level.

    Note Select an option to view the performance details for that service level (as peak/expected IOPS/throughput). Select the service level that best matches your needs.
  12. Specify the capacity of the disk.

  13. If snapshots are required for this disk:

    1. Toggle to enable the Snapshot Policy to view the Snapshot Policy fields.

    2. Specify when to create the snapshots:

      • Hourly. Specify which minute (of the hour) to take snapshot (check) and the number of hourly snapshots to retain.

      • Daily. Specify when (hour and minute) to take the snapshot (check) and the number of hourly snapshots to retain. If you want to specify multiple hours when the snapshot has to be taken daily, you can add the values of the hours in a comma-separated list, for example, 5, 10, 15, and so forth.

      • Weekly. Specify when (day of the week, hour and minute) to take snapshot (check) and the number of weekly snapshots to retain.

      • Monthly. Specify when (day of the month, hour, and minute) to take snapshot and the number of monthly snapshots to retain.

  14. If asynchronous disaster recovery is enabled on the underlying block store, asynchronous disaster recovery replication is automatically enabled for the new disk. If you wish to exclude the disk from asynchronous disaster recovery replications, toggle the Asynchronous Disaster Recovery toggle so that asynchronous disaster recovery is disabled.

  15. If the disk is being created in a zone that is MetroCluster-enabled, the Synchronous Disaster Recovery button is enabled and cannot be disabled. The disk will be replicated to the zone displayed in the Synchronous Disaster Recovery panel.

  16. To enable backups for this disk:

    1. Toggle to enable the Backup Policy to view the Backup Policy fields.

    2. Specify the backup zone.

    3. Specify how many of each type of backup to keep: daily, weekly, and/or monthly.

  17. If you want to add tags (key-value pairs) to the disk, specify them in the Tags section.

  18. Click Create. This creates a job to create the disk.

After you finish

Create disk is run as an asynchronous job. You can:

  • Check the status of the job in the jobs list.

  • After the job is finished, check the status of the disk in the Disks list.