Check storage information

Prev Next

The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.

Available in VPC

In addition to the default storage, you can connect additional storage to the server. The available additional storage depends on the hypervisor type and the server type.

For more information on the additional storage specifications, see the following guides:

Caution

Data accidentally deleted by your carelessness cannot be restored. To prevent data loss and protect important information, backup the storage data regularly.

Storage page

To view the Storage page, click Console > i_menu > Services > Compute > Server > Storage in order on the NAVER Cloud Platform portal.

The Storage page is laid out as follows:

server-storage-vpc_screen_ko

Area Description
① Menu name Name of the menu currently being checked and the number of created storages
② Basic features Features provided upon initial entry to the Storage menu
  • [Create storage] button: click to create storage
  • [View storage information] button: click to view storage types and capacities by hypervisor
  • [Learn more about the product] button: click to go to the Block Storage introduction page
  • [Download] button: click to download the storage list as an Excel file
  • [Refresh] button: click to refresh the snapshot list
③ Post-creation features Features provided after storage creation
④ Search bar Searches the created storage by server name, storage name, and connection information conditions
⑤ Filter Filters the storage to be displayed
⑥ Storage list List of created storages
  • Storage name (Instance ID): name of the default storage automatically entered or name of the added storage you entered yourself. Instance ID is an automatically assigned unique ID.
  • Hypervisor: hypervisor type of storage
  • Size: storage size. Click i-storage_sizeto change storage size.
  • IOPS: processing speed of the storage. The rules provided vary depending on the Storage specifications.
  • Status: current status of the storage
    • Creating: status in which the storage is being created with the information you enter
    • Available: status in which the created storage can be connected to the server
    • In use: status in which the server connected to the server is in use
    • Removing: status in which the connection between the storage and the server is being removed
    • Returning: status in which the storage is being returned
    • Replicating: status in which the storage is currently being replicated by running Create snapshot
  • Removable: whether the storage can be removed from the server. Only the additional storage connected to a server is displayed as Applicable.
  • Storage encryption applied: whether storage is encrypted
  • Storage return protection: return protection setting status. Storage with return protection applied is not returned.
  • Creation date and time: date and time when the storage was created
  • Connection information: name of server and disk to which the storage is connected
  • Type/storage type: specification type of storage
  • ZONE: zone where the storage is deployed
  • Resizability: whether the storage capacity can be changed. Default storage is displayed as Not applicable.
  • Redhat only: whether the storage is exclusive to Redhat
    • Storage marked with Y can only be connected to Redhat servers
    • Storage marked with N can be connected to servers other than Redhat servers

FB1/2, CB1/2 performance details

The performance indicators for FB1/2 and CB1/2 storage is based on the maximum value and it does not guarantee consistent values. The performance and throughput of the volumes are determined by the lower value among the following two values:

  • Storage volume performance/throughput
  • Server instance performance/throughput
Note

For server instance performance and throughput, see KVM-based server characteristics.

FB1/2 performance

The following describes the throughput, burst throughput and credits, and throughput variations of FB1/2 storage.

FB1/2 throughput and burst throughput

The throughput of FB1/2 storage is provided variably between 4 and 500 MB/s depending on the storage volume size.

  • Throughput calculation: storage volume size (GB) x 0.039 MB/s
    • Round off at the first decimal point.
    • <Example>: 1 TB x 0.039 MB/s = 39.936 => 40.0 MB/s

The burst throughput of FB1/2 storage is provided variably between 25 and 500 MB/s.

  • Burst throughput calculation: storage volume size (GB) x 0.244 MB/s
    • Round off at the first decimal point.
    • <Example>: 100 GB x 0.244 MB/s = 24.4 => 25 MB/s

The throughput and the burst throughput of FB1/2 storage are determined by the size of the volume.
For some examples, see the following:

  • 100 GB volume: provides a maximum burst performance of 25 MB/s. If using continuously, maintains performance for about 41,943 seconds.
  • 1 TB volume: provides a maximum burst performance of 250 MB/s. If using continuously, maintains performance for about 4,194 seconds.

FB1/2 burst throughput credit

The burst credit of FB1/2 storage is 1 TB. The recovery performance of burst credits is the standard throughput of the volume. For a 100 GB volume, it recovers burst credits at a performance of 4 MB/s, and for a 1 TB volume, it recovers burst credits at a performance of 40 MB/s. If I/O of the volume does not exist, the maximum time required to fully recover burst credits is 262,144 seconds. However, the recovery time may change depending on the remaining credits and performance usage amount of the volume.

FB1/2 throughput variation

The throughput variations based on volume size are as follows:

Volume size Standard throughput (MB/s) Burst throughput (MB/s) Note
100 GB 4 25 -
1 TB 40 250 -
2 TB 80 500 Burst throughput reaches its maximum at 2 TB
12 TB 500 Not provided Standard throughput reaches its maximum at 12 TB
16 TB 500 Not provided -

CB1/2 performance

The following describes the IOPS and IOPS burst, IOPS burst credits, and performance variations of CB1/2 storage.

CB1/2 IOPS and IOPS burst

The IOPS performance of CB1/2 storage is provided variably between 100 and 16,000 IOPS depending on the storage volume size.

  • IOPS calculation: storage volume size (GB) x 3 IOPS
  • For a volume size of 33 GB, 100 IOPS are provided
  • When the storage volume size is 5333 GB (5340 GB), reaches the maximum IOPS value of 16,000 IOPS

IOPS burst is a feature that enables you to use the volume at a higher value than the standard performance value for a certain amount of time.
The IOPS burst of CB1/2 storage is provided with a fixed 3000 IOPS.

  • Applies to volumes smaller than 100 GB that do not reach the standard IOPS performance value of 3000
  • For volumes of 1000 GB and higher, the standard IOPS performance value reaches 3000, so the IOPS burst is not provided

CB1/2 burst IOPS credit

The following describes the logic to calculate the hold time of maintaining IOPS burst of CB1/2 storage.
You can calculate the burst hold time based on the performance usage, bucket size, and standard performance value.

storage-screen_cb1_burstcredit

  • A: performance usage of the storage volume
  • B: bucket size (5,400,000)
  • C: standard performance depending on the volume size
  • The calculation for burst hold time is "B / (A - C)"
    • <Example>: when using the burst to its maximum (3000 IOPS) continuously for 100 GB of volume, the burst hold time is 2000 seconds
    • <Example>: when using the burst to its maximum (2000 IOPS) continuously for 400 GB of volume, the burst hold time is 6750 seconds
    • When the bucket is full, the performance of a volume returns to its standard performance.
  • Recovery time for burst credit
    • The recovery time depends on the speed of the standard performance (C).
    • When a 400 GB volume spends all remaining credits and there is no I/O, the maximum time required to recover all burst credits is 4500 seconds. If the recovery is made while consistently using 500 IOPS, it takes 7715 seconds.
    • The recovery time depends on the remaining credits of a volume and the performance usage amount.

CB1/2 performance variation

The performance variations based on volume size are as follows:

Volume size Standard IOPS Burst IOPS Standard throughput (MB/s) Burst throughput (MB/s) Note
10 GB 100 3,000 100 - -
40 GB 120 3,000 100 - -
150 GB 450 3,000 100 - -
160 GB 480 3,000 110 - -
200 GB 600 3,000 150 - -
300 GB 900 3,000 250 - Standard throughput reaches its maximum
1,000 GB 3,000 - 250 - Standard IOPS reaches its burst
5,340 GB 16,000 - 250 - Standard IOPS reaches its maximum