You can add drives to increase the capacity of storage pools.
To add storage pool capacity, you need to add more drives to all storage nodes. The amount of drive space required depends on the configuration. See Capacity design when adding storage nodes to prepare the required capacity.
-
Existing data for the drives you are adding will be lost. Be careful.
-
After drives are added, user data might be automatically moved to the added drives. While user data is being moved, host I/O performance might decrease.
-
When spare nodes have already been registered, also add drives for the spare nodes.
Requirements for addition of drives (Bare metal)
|
Item |
Requirement |
Remarks |
|---|---|---|
|
Status of the storage node where drives are to be added |
"Ready" or "RemovalFailed" |
|
|
Maximum number of user data drives (per storage node) |
24 |
It differs depending on the server used as a storage node. |
|
Drive type |
SSD (SAS or NVMe) |
|
|
Drive capacity |
The required capacity per drive must be satisfied. In HPEC 4D+1P: 249 [GiB] or more In HPEC 4D+2P: 298 [GiB] or more In Mirroring Duplication: 201 [GiB] or more |
Even if drive capacity in excess of the following capacity is installed, it is not used by the system. In HPEC 4D+1P: 124 [TiB] In HPEC 4D+2P: 148 [TiB] In Mirroring Duplication: 198 [TiB] |
Requirements for addition of drives (Cloud)
Requirements for addition of drives in the cloud model are as follows.
(Cloud) When the Floating base license is applied, adding drives might cause the licensed capacity of the AWS License Manager license to be exceeded. To calculate the storage pool capacity after drive addition, see Estimating the storage pool capacity to confirm the consumed amount of a license (Cloud). Then, before adding drives, verify whether the storage pool logical capacity is within the licensed capacity of the AWS License Manager license. Also, when estimating the required licensed capacity, round up the storage pool logical capacity to the unit of TiB.
When multiple storage clusters share the AWS License Manager license, round up the storage pool logical capacity of each storage cluster to the unit of TiB first, and then sum the total to verify that the total logical capacity is within the licensed capacity of the AWS License Manager license.
Example: If there are two storage clusters, one of which has 31.3 [TiB] and the other one has 47.7 [TiB] as storage pool logical capacity, round up those values to integers 32 [TiB] and 48 [TiB] respectively, and then sum the total as 80 [TiB].
If the licensed capacity is insufficient, renew the license contract in AWS Marketplace.
|
Item |
Requirement |
Remarks |
|---|---|---|
|
Status of the storage node where drives are to be added |
"Ready" or "RemovalFailed" |
|
|
Maximum number of user data drives (per storage node) |
24 |
|
| Number of user data drives per storage node | The number of user data drives must be the same for all storage nodes*. | *The tiebreaker node in Multi-AZ configuration is excluded. |
|
Drive type |
SSD (gp3) |
|
|
Drive performance and capacity |
Drive performance and capacity must remain the same as those at the time of initial configuration. | Drive performance and capacity in the initial configuration cannot be changed. |
Procedure for adding drives
The following explains the order of steps for adding drives and their reference sections.
(Bare metal) If you are adding drives to multiple storage nodes, repeat the procedure in Inserting drives (Bare metal) for the number of storage nodes, verify the information for all the added drives, and then perform Expanding storage pools.
|
Model |
Sequence of steps and references |
|---|---|
|
Bare metal |
|
|
Cloud |