You can expand the amount of storage after a Teradata Database single-node or MPP instance is launched without increasing the AMP count or reconfiguring the system. Expanding storage increases each EBS volume on the system, but does not increase the parallelism of the system.
If you want to increase the CPU, memory, and storage bandwidth of the nodes, you should change the instance type instead of expanding EBS storage.
If you want to keep the vproc count and instance type the same, but change the node count, CPU count, memory size, and network and storage bandwidth of the system, you should unfold or fold instead of expanding EBS storage. See Teradata Database Fold and Unfold.
The following table describes the storage expansion requirements.
|Unfold state||The system cannot be in an unfolded state when you expand the EBS storage.|
|Instance type||The system must have been launched with EBS storage and with an m4.4xlarge, m4.10xlarge, or m4.16xlarge instance type.|
|Volume count per node||The system must have 20 Teradata pdisk EBS volumes per node before expanding storage.|
|Maximum storage size||The total storage on the system can only be expanded up to 60 TB per node (up to 3 TB per EBS volume).|
The following table describes some limitations you should consider before expanding storage.
|Cool down period||After storage is expanded successfully once, you must wait 6 hours before expanding again.|
|Size increase||Expanding storage only increases the storage capacity of the EBS volumes. It does not decrease the storage capacity of the system.|