Skip to main content

storage aggregate create

Contributors
Suggest changes
PDFs

Create an aggregate

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The storage aggregate create command creates an aggregate. An aggregate consists of disks. You must specify the number of disks or provide a list of disks to be added to the new aggregate. If you specify the number of disks without providing a list of disks, the system selects the disks.

When creating an aggregate, you can optionally specify the aggregate's home node, the RAID type for RAID groups on the aggregate, and the maximum number of disks that can be included in a RAID group.

Parameters

-aggregate <aggregate name> - Aggregate

This parameter specifies the name of the aggregate that is to be created.

[-chksumstyle <aggrChecksumStyle>] - Checksum Style

This parameter specifies the checksum style for the aggregate. The values are block for Block Checksum and advanced_zoned for Advanced Zoned Checksum (AZCS).

-diskcount <integer> - Number Of Disks

This parameter specifies the number of disks that are to be included in the aggregate, including the parity disks. The disks in this newly created aggregate come from the pool of spare disks. The smallest disks in this pool are added to the aggregate first, unless you specify the -disksize parameter.

[-R, -diskrpm <integer>] - Disk RPM

This parameter specifies the RPM of the disks on which the aggregate is to be created. The possible values include 5400, 7200, 10000, and 15000.

[-disksize <integer>] - Disk Size(GB)

This parameter specifies the size, in GB, of the disks on which the aggregate is to be created. Disks with a usable size between 90% and 105% of the specified size are selected.

{ [-T, -disktype {ATA | BSAS | FCAL | FSAS | LUN | MSATA | SAS | SSD | VMDISK | SSD-NVM | SSD-CAP | SSD-ZNS | VMLUN | VMLUN-SSD}] - Disk Type

This parameter specifies the type of disk on which the aggregate is to be created.

Note When this parameter is used, disk selection is not influenced by RAID options raid.mix.hdd.disktype.capacity , raid.mix.hdd.disktype.performance , or raid.mix.disktype.solid_state . Only disks of the specified type are considered eligible for selection.
| [-C, -diskclass {capacity | performance | archive | solid-state | array | virtual}] - Disk Class

This parameter specifies the class of disks on which the aggregate is to be created. All disks that belong to the specified class are considered eligible for selection. The possible values are:

  • capacity = Capacity-oriented, near-line disk types. Includes disk types FSAS, BSAS and ATA.

  • performance = Performance-oriented, enterprise class disk types. Includes disk types FCAL and SAS.

  • archive = Archive class SATA disks in multi-disk carrier storage shelves. Includes disk type MSATA.

  • solid-state = Solid-state drives. Includes disk type SSD, SSD-CAP and SSD-NVM.

  • array = Logical storage devices backed by storage arrays and used by ONTAP as disks. Includes disk type LUN.

  • virtual = Virtual disks that are formatted and managed by the hypervisor. Includes disk type VMDISK.

Note When this parameter is used, disk selection is not influenced by RAID options raid.mix.hdd.disktype.capacity , raid.mix.hdd.disktype.performance , or raid.mix.disktype.solid_state .
[-m, -mirror <true>] - Is Mirrored

This parameter specifies that the new aggregate be mirrored (have two plexes). If this parameter is set to true , the specified disks are split between the two plexes. By default, the new aggregate will not be mirrored. You cannot use the -mirror parameter when supplying a specific list of disks with either the -disklist or -mirror-disklist parameters.

[-pool <aggrSparePool>] - Spare Pool

This parameter specifies the SyncMirror pool to be used to supply the disks for the aggregate. Valid values are Pool0 or Pool1.

| -d, -disklist <disk path name>,…​ - Disks for First Plex

This parameter specifies a list of disks to be added to the new aggregate. If you specify the -disklist parameter, you cannot further qualify the list of disks to be added by count, checksum style, type, size, or RPM. You cannot use the -disklist parameter when the -mirror parameter is set to true .

[-mirror-disklist <disk path name>,…​] - Disks for Mirrored Plex

This parameter specifies a list of mirror disks to be added to the new mirrored aggregate. It must contain the same number of disks specified in -disklist parameter. If you specify the -mirror-disklist parameter, you cannot further qualify the list of disks to be added by count, checksum style, type, size, or RPM. You cannot use the -mirror-disklist parameter when the -mirror parameter is set to true .

[-ignore-pool-checks <true>] - Don't Enforce Plex Pool Best Practices

The disks in a plex are normally required to come from the same SyncMirror pool. This behavior can be overridden with this parameter when it is set to true . This option cannot be used when the -mirror option is set to true

[-f, -allow-mixed-rpm <true>] - Allow Disks With Different RPM Values

This parameter specifies whether the aggregate can contain disks that have different RPM values. For example, SAS disks can rotate at 10,000 or 15,000 RPM. If this parameter is set to true and a list of disks are provided by using the -disklist parameter, the aggregate will be created even if the SAS disks you specify have different RPM values. This parameter works similarly for ATA disks, which can rotate at 5,400 or 7,200 RPM.

[-allow-same-carrier <true>] - Allow Same RAID Group Within Carrier

This parameter can be used to allow two disks housed in the same carrier to be in the same RAID group when you add disks to an aggregate.

Having disks in the same carrier in the same RAID group is not desirable because a carrier failure can cause a simultaneous outage for two disks in the same RAID group. You create an aggregate with this characteristic, but when an alternate disk becomes available, ONTAP automatically initiates a series of disk copy operations to put the disks into different RAID groups. For this reason, you should use this parameter only when necessary. When possible, allow ONTAP to choose the disks from which to create the aggregate.

This parameter affects only the aggregate creation operation. It is not a persistent attribute of the aggregate.

[-node {<nodename>|local}] - Node

This parameter specifies the home node for the aggregate. If this parameter is not specified, ONTAP selects the node where the aggregate is created.

-ha-policy {sfo|cfo} - HA Policy

This parameter specifies the high-availability policy of the aggregate.

[-s, -maxraidsize <integer>] - Max RAID Size

This parameter specifies the maximum number of disks that can be included in a RAID group.

[-t, -raidtype {raid_tec|raid_dp|raid4|raid_ep}] - RAID Type

This parameter specifies the type for RAID groups on the aggregate. The values are raid4 for RAID4, raid_dp for RAID Double Parity, and raid_tec for RAID Triple-Erasure-Code. The default setting is raid_dp unless the disks are HDDs with a capacity larger than 4 TB, in which case the default will be raid_tec . This parameter is not needed for array LUNs because they are always created with the raid0 raidtype. raid4 is not compatible with shared disks unless the shared disks belong to a storage pool.

[-simulate <true>] - Simulate Aggregate Provisioning Operation

This option simulates the aggregate creation and prints the layout of the new aggregate.

[-force-small-aggregate <true>] - Force the Creation of a Small Aggregate (privilege: advanced)

This parameter can be used to force the creation of a 2-disk RAID4 aggregates, or a 3-disk or 4-disk RAID-DP aggregate.

[-is-autobalance-eligible {true|false}] - Is Eligible for Auto Balance Aggregate (privilege: advanced)

This specifies whether the aggregate will be considered by the Auto Balance Aggregate feature. If the Auto Balance Aggregate feature is not used, this field is not used. When this parameter is set to true the Auto Balance Aggregate feature might recommend moving volumes to or from this aggregate in order to balance system workload. When this parameter is set to false the aggregate will not be considered as a destination for the Auto Balance Aggregate feature allowing for predictability in data placement. The default value is false .

[-L, -snaplock-type {non-snaplock|compliance|enterprise}] - SnapLock Type

This parameter specifies the type of SnapLock aggregate to be created. In order to create a SnapLock Compliance aggregate, specify compliance . To create a SnapLock Enterprise aggregate, specify enterprise .

[-autobalance-unbalanced-threshold-percent <integer>] - Threshold When Aggregate Is Considered Unbalanced (%) (privilege: advanced)

This parameter specifies the space used threshold percentage that will cause the Auto Balance Aggregate feature to consider an aggregate as unbalanced.

[-autobalance-available-threshold-percent <integer>] - Threshold When Aggregate Is Considered Balanced (%) (privilege: advanced)

This parameter specifies the threshold percentage which will determine if an aggregate is a target destination for a move. The Auto Balance Aggregate feature will attempt to move volumes from an unbalanced aggregate until it is under this percentage.

[-encrypt-with-aggr-key {true|false}] - Enable Aggregate level Encryption

This parameter specifies the data encryption policy for the contained volumes. If this parameter is set to true , then by default, the volumes created in this aggregate will be encrypted, using the aggregate level encryption keys.

Examples

The following example creates an aggregate named aggr0 on a home node named node0. The aggregate contains 20 disks and uses RAID-DP. The aggregate contains regular FlexVol volumes:

cluster1::> storage aggregate create -aggregate aggr0 -node node0
-diskcount 20 -raidtype raid_dp -volume-style flex

The following example creates an aggregate named aggr0 on a home node named node0. The aggregate contains the disks specified and uses RAID-DP

cluster1::> storage aggregate create -aggregate aggr0 -node node0
-disklist 1.0.15,1.0.16,1.0.17,1.0.18,1.0.19 -raidtype raid_dp

The following example creates an aggregate named aggr0 on a home node named node0. The aggregate contains 20 disks of size 6 TB and of type FSAS and uses RAID-TEC:

cluster1::> storage aggregate create -aggregate aggr0 -node node0
-diskcount 20 -raidtype raid_tec -disksize 6000 -disktype FSAS

The following example creates a mirrored aggregate named aggr0 on the local node. The aggregate contains 10 disks in each plex:

cluster1::> storage aggregate create -aggregate aggr0 -mirror
-diskcount 20