Disk array

Edit online

A disk array (an aggregate) is a data storage system made up of multiple disk drives. For example, a RAID is an aggregate that implements redundancy and other data management features. A disk array provides storage volumes to serve the storage requirements of physical machines. It uses the resources of one storage controller, which manages the disk array operation.

Turbonomic discovers disk arrays through storage controller targets.

Disk Array in the Supply Chain

Monitored resources

Turbonomic monitors the following resources:

Note:

Not all targets of the same type provide all possible commodities. For example, some storage controllers do not expose CPU activity. When a metric is not collected, the corresponding chart in the user interface will not display data.

  • Storage amount

    Storage amount is the measurement of storage capacity that is in use.

  • Storage provisioned

    Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

  • IOPS

    IOPS is the per-second measurement of read and write access operations on a storage entity.

  • Latency

    Latency is the measurement of storage latency.

Disk array actions

Turbonomic supports the following actions:

  • Provision

    For high utilization of the disk array’s storage, provision a new disk array. This action can only be executed outside Turbonomic.

  • Start

    For high utilization of disk array, start a suspended disk array. This action can only be executed outside Turbonomic.

  • Suspend

    For low utilization of the disk array’s storage, move VMs to other datastores and suspend volumes on the disk array. This action can only be executed outside Turbonomic.

  • Move

    (Only for NetApp Cluster-Mode) For high utilization of Storage Controller resources, Turbonomic can move an aggregate to another storage controller. The storage controllers must be running.

    For high IOPS or latency, a move is always off of the current disk array. All the volumes on a given disk array show the same IOPS and Latency, so moving to a volume on the same array would not fix these issues.

  • Move VM

    For high utilization of Storage on a volume, Turbonomic can move a VM to another volume. The new volume can be on the current disk array, on some other disk array, or on any other datastore.

    For high IOPS or latency, a move is always off of the current disk array. All the volumes on a given disk array show the same IOPS and Latency, so moving to a volume on the same array would not fix these issues.

  • Move datastore

    To balance utilization of disk array resources, Turbonomic can move a datastore to another array.