Limit Type | Description |
Enhanced SSD usage | Currently, Enhanced SSD is only available in certain AZs and will be supported in more AZs in the future. You can check the information on the purchase page. The performance of Enhanced SSD is only guaranteed when it's attached to S5, M5, and SA2 models created after August 1, 2020, and all later generation models, for example, Standard S5, S6, and later. Enhanced SSD cannot be used as the system disk. Enhanced SSD cloud disks cannot be encrypted. Enhanced SSD cannot be upgraded from other disk types. |
ulTra SSD usage | Currently, ulTra SSD is only available in certain AZs and will be supported in more AZs in the future. You can check the information on the purchase page. ulTra SSD can only be purchased together with Standard Storage Optimized S5se instances. ulTra SSD cannot be purchased independently. ulTra SSD cannot be used as the system disk. ulTra SSD cannot be encrypted. ulTra SSD cannot be upgraded from other disk types. |
Elastic cloud disk capability | Starting from May 2018, all data disks purchased upon creation of CVMs are elastic cloud disks. You can detach them from and re-attach them to CVMs. This feature is supported in all availability zones. |
Cloud disk performances | I/O specification applies to both input and output performance at the same time. For example, if a 1-TB SSD has a maximum random IOPS of 26,000, it means that both its read and write performance can reach this value. Due to performance limits, if the block size in this example is 4 KB or 8 KB, the maximum IOPS can be reached. If the block size is 16 KB, the maximum IOPS cannot be reached (throughput has already reached the limit of 260 MB/s). |
Max attachable elastic cloud disks per CVM | Up to 20. |
Number of cloud disks created at a time | Up to 50. |
Limits on the number of instances to which a cloud disk can be attached | Cloud disks and instances (CVM or Lighthouse instances) to which they are attached must be in the same AZ. Cloud disks of CVM instances are independent of cloud disks of Lighthouse instances. Cloud disks of CVM instances cannot be attached to Lighthouse instances, and vice versa. |
Repossession of cloud disks in arrears | When a monthly-subscribed cloud disk expires and you do not renew it within 7 days after the expiry, it will be forcibly unmounted from the CVM (if any), and moved to the recycle bin. For details about the repossession mechanism, see Arrears. Currently, when you mount a monthly-subscribed cloud disk to monthly-subscribed CVM, the following renewal method are available: Renew the cloud disk when the associated CVM expires Renew the cloud disk automatically on a monthly basis after it expires. Mount directly without a renewal policy. |
Limit Type | Description |
Supported disk type | You can only use the data disk snapshot to create elastic cloud disks, while using the system disk snapshot to create a custom image. |
Capacity of cloud disk created using a snapshot | The capacity of the cloud disk created using a snapshot should be greater than or equal to that of the snapshot. |
Snapshot rollback | Snapshot data can only be rolled back to the source cloud disk from which the snapshot was created. If you want to create a cloud disk with data in an existing snapshot, see Creating Cloud Disks Using Snapshots. |
Total snapshot size | No limit. |
Snapshot quota in one region | 64 + the number of cloud disks in the region * 64. |
Limit Type | Description |
Scheduled snapshot policy quota in one region | A single Tencent Cloud account can set a maximum of 30 scheduled snapshot policies in each region. |
Number of scheduled snapshot policies being associated with one cloud disk | A cloud disk can associate with a maximum of 10 scheduled snapshot policies in the same region. |
Number of cloud disks associated with one scheduled snapshot policy | A scheduled snapshot policy can be associated with a maximum of 200 cloud disks in the same region. |
Was this page helpful?