The page has been translated by Gen AI.

How-to Guides

Users can create the service by entering the required information for Block Storage (BM) and selecting detailed options through the Samsung Cloud Platform Console.

Block Storage(BM) Create

You can create and use the Block Storage (BM) service in the Samsung Cloud Platform Console.

To create Block Storage (BM), follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).

  2. From the Service Home page, click the Create Block Storage (BM) button. 2. Go to the Block Storage(BM) Creation page.

  3. On the Block Storage(BM) Creation page, enter the information required to create the service and select detailed options.

    Category
    Required
    		Detailed description
    Volume namerequiredVolume name
    • must start with an English letter and use English letters, numbers, and special characters (-) to enter 3~28 characters
    • cannot be modified after service creation
    Disk typerequiredSelect disk type
    • SSD: high‑performance standard volume
    • HDD: standard volume
    • Cannot be modified after service creation
    capacityrequiredCapacity setting
    • Enter a number between 1~16,384GB
    • Cannot be modified after service creation
    Max IOPSrequiredEnter the IOPS value
    • Enter a number between 5,000~20,000
    • HDD type does not provide performance metric configuration functionality
    Max ThroughputrequiredEnter the throughput speed (MB/s)
    • Enter a number between 250~1,000
    • HDD type does not provide performance metric configuration
    Availability ZonerequiredSelect the Availability Zone to create resources within the region
    • If you change the Availability Zone while a connection server has been added, the selected connection server will be reset
    • For users who have Private or Dedicated resources, the Availability Zone information can be viewed
    Connection serverrequiredSelect a connected Bare Metal Server
    • Provide up to 8 Bare Metal Server connections
    • No limit on the number of volumes that can be attached to a Bare Metal Server
    Table. Block Storage (BM) Service Information Input Items

  4. Check the detailed information and estimated charges generated in the Summary panel, and click the Create button.

  5. When the popup indicating creation opens, click the Confirm button.

    • When creation is complete, check the created resources on the Block Storage(BM) List page.
Reference
  • Volumes can only be attached to Bare Metal Servers within the same Availability Zone.
  • Regardless of disk type, all volumes have server-side encryption based on the AES-256 algorithm applied by default.
  • The snapshot schedule can be set on the detail page.
  • The performance metrics (IOPS, Throughput) of the configured storage are based on maximum values and do not guarantee consistent values.
Caution
Capacity can be expanded only for the original volume that does not use the snapshot feature. For volumes that use snapshots, add the volume to the attached server to increase capacity.

Configure iSCSI

Volumes created by the user in addition to the OS’s default volume must be configured with iSCSI.

After verifying the IP provided in the Block Storage(BM) Details page’s iSCSI Information, proceed according to the iSCSI setup instructions for each operating system.

Linux operating system

Info

The iSCSI information (Storage Target IP) is assumed to be 10.40.40.41, 10.40.40.42.

  • Check the iSCSI information on the Block Storage (BM) detail page.
  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List page.
  3. On the Block Storage (BM) List page, click the resource to be used on the connected server. 3. Block Storage(BM) Details Navigate to the page.
  4. Connection Server item, check the server and then connect.
  5. Proceed with iSCSI configuration by referring to the steps below.
    • Discover the storage (target IP) connection information.
      Color mode
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169

[root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169

[root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      Code block. Storage (target IP) connection information discovery
    • Connect to the Storage (target IP). * If it is already connected, proceed to the next step.
      Color mode
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful

[root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful

[root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      Code block. Storage (target IP) connection
    • To minimize search time, delete all unused Storage (target IP).
      Color mode
      [root@localhost ~]# iscsiadm -m node show
100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169

[root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
      [root@localhost ~]# iscsiadm -m node show
100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169

[root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
      Code block. Delete unused Storage (target IP)
    • Please rescan to check for additional disks.
      Color mode
      [root@localhost ~]# iscsiadm -m session --rescan
Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      [root@localhost ~]# iscsiadm -m session --rescan
Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      code block. Rescan
    • Set Auto Login so that you are logged in automatically even after a reboot.
      Color mode
      [root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
[root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
      [root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
[root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
      code block. Auto Login setting
    • Verify the final configuration using the following command.
      Color mode
      [root@localhost ~]# lsblk
      [root@localhost ~]# lsblk
      Code block. Check configuration settings

Windows operating system

Notice

iSCSI information (Storage Target IP) is assumed to be 10.40.40.41, 10.40.40.42.

  • Block Storage(BM) View the iSCSI information on the detail page.
  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Navigate to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Go to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource to be used on the connected server. 3. Block Storage(BM) Details Go to the page.
  4. In the Connection Server item, verify the server and then connect.
  5. Proceed with iSCSI configuration by referring to the steps below.
    • Open Command Prompt (Admin) and run PowerShell.
      Color mode
      Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users> cd ..
PS C:\>
      Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users> cd ..
PS C:\>
      Code block. Run PowerShell
    • Start the volume service.
      Color mode
      PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
PS C:\> Start-Service -Name MSiSCSI
PS C:\> get-service -Name MSiSCSI |  select -Property Name, DisplayName, Status, StartType

Name       DisplayName                           Status    StartType
-------    --------------                        -------   -----------
MSiSCSI    Microsoft iSCSI Initiator Service     Running   Automatic
      PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
PS C:\> Start-Service -Name MSiSCSI
PS C:\> get-service -Name MSiSCSI |  select -Property Name, DisplayName, Status, StartType

Name       DisplayName                           Status    StartType
-------    --------------                        -------   -----------
MSiSCSI    Microsoft iSCSI Initiator Service     Running   Automatic
      Code block. Start volume service
    • Install Multipath I/O. * If the Restart Needed item is marked as Yes, a restart is required.
      Color mode
      PS C:\> Install-WindowsFeature -name Multipath-IO

Success   Restart Needed   Exit Code   Feature Result
-------   --------------   ---------   -----------------
True      No               Success     {Multipath I/O}
      PS C:\> Install-WindowsFeature -name Multipath-IO

Success   Restart Needed   Exit Code   Feature Result
-------   --------------   ---------   -----------------
True      No               Success     {Multipath I/O}
      Code block. Multipath I/O installation
    • Modify the Initiator Port Address. *
      If you are not an Active Directory member, skip this procedure. The Initiator Port Address needs to be modified only if it is an Active Directory member.
      • The iqn is generated based on the hostname, but when joined to Active Directory, it is converted to DNS format.
        Since it is registered to the storage based on the default hostname, for iqn.1991-05.com.microsoft:iqn01.scp.com, iqn01 is the hostname. Remove the DNS information and change it to the name registered when creating the OS in the user Console, such as iqn.1991-05.com.microsoft:iqn01.
      • If you are not an AD member, no changes are required.
        Color mode
        PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
PS C:\> echo $address
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01.scp.com

PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
PS C:\> Get-InitiatorPort | select NodeAddress
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01
        PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
PS C:\> echo $address
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01.scp.com

PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
PS C:\> Get-InitiatorPort | select NodeAddress
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01
        Code block. Modify Initiator Port Address
    • Set the address of Storage (target Portal) as a variable.
      Color mode
      PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
      PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
      Code block. Set the Storage (target Portal) address as a variable
    • Discover the Storage (target Portal).
      Color mode
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
    New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
}
InitiatorInstanceName   :
InitiatorPortalAddress  :
IsDataDigest            : False
IsHeaderDigest          : False
TargetPortalAddress     : 10.40.40.41
TargetPortalPortNumber  : 3260
PSComputerName          :

InitiatorInstanceName   :
InitiatorPortalAddress  :
IsDataDigest            : False
IsHeaderDigest          : False
TargetPortalAddress     : 10.40.40.42
TargetPortalPortNumber  : 3260
PSComputerName          :
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
    New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
}
InitiatorInstanceName   :
InitiatorPortalAddress  :
IsDataDigest            : False
IsHeaderDigest          : False
TargetPortalAddress     : 10.40.40.41
TargetPortalPortNumber  : 3260
PSComputerName          :

InitiatorInstanceName   :
InitiatorPortalAddress  :
IsDataDigest            : False
IsHeaderDigest          : False
TargetPortalAddress     : 10.40.40.42
TargetPortalPortNumber  : 3260
PSComputerName          :
      code block. Storage (target Portal) Discovery
    • Connect the disk (target).
      Color mode
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
    Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
}
AuthenticationType      : NONE
InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress  : 0.0.0.0
InitiatorSideIdentifier : 400001370000
IsConnected             : True
IsDataDigest            : False
IsDiscovered            : True
IsHeaderDigest          : False
IsPersistent            : True
NumberOfConnections     : 1
SessionIdentifier       : ffffcd0b7ba58010-4000013700000006
TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier    : 1100
PSComputerName          :

AuthenticationType      : NONE
InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress  : 0.0.0.0
InitiatorSideIdentifier : 400001370002
IsConnected             : True
IsDataDigest            : False
IsDiscovered            : True
IsHeaderDigest          : False
IsPersistent            : True
NumberOfConnections     : 1
SessionIdentifier       : ffffcd0b7ba58010-4000013700000007
TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier    : 1000
PSComputerName          :
IsHeaderDigest          : False
TargetPortalAddress     : 10.40.40.42
TargetPortalPortNumber  : 3260
PSComputerName          :
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
    Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
}
AuthenticationType      : NONE
InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress  : 0.0.0.0
InitiatorSideIdentifier : 400001370000
IsConnected             : True
IsDataDigest            : False
IsDiscovered            : True
IsHeaderDigest          : False
IsPersistent            : True
NumberOfConnections     : 1
SessionIdentifier       : ffffcd0b7ba58010-4000013700000006
TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier    : 1100
PSComputerName          :

AuthenticationType      : NONE
InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress  : 0.0.0.0
InitiatorSideIdentifier : 400001370002
IsConnected             : True
IsDataDigest            : False
IsDiscovered            : True
IsHeaderDigest          : False
IsPersistent            : True
NumberOfConnections     : 1
SessionIdentifier       : ffffcd0b7ba58010-4000013700000007
TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier    : 1000
PSComputerName          :
IsHeaderDigest          : False
TargetPortalAddress     : 10.40.40.42
TargetPortalPortNumber  : 3260
PSComputerName          :
      Code block. Disk (target) connection
    • Refresh the Storage (target) information.
      Color mode
      PS C:\> Update-IscsiTarget
      PS C:\> Update-IscsiTarget
      Code block. Refresh Storage (target) information
    • Register the Multipath I/O DSM and create an MPIO Disk. *
      Inquiries arise when a reboot is required during MPIO disk creation. Press Y or the Enter key to reboot.
      Color mode
      PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
PS C:\> Update-MPIOClaimedHW

Confirm
Are you sure you want to perform this action?
The operation may require a system restart.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
False
      PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
PS C:\> Update-MPIOClaimedHW

Confirm
Are you sure you want to perform this action?
The operation may require a system restart.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
False
      Code block. Register Multipath I/O DSM, create MPIO Disk
    • Check the Multipath I/O Disk list and path. *
      You can view MPIO disk information using the mpclaim.exe command. Enter the generated MPIO disk number to check the disk path and status.
      Color mode
      PS C:\> mpclaim.exe -s -d
For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.

MPIO Disk    System Disk  LB Policy    DSM Name
-------------------------------------------------------------------------------
MPIO Disk3   Disk 1       RR           Microsoft DSM

PS C:\> mpclaim.exe -s -d 3
MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
    Controlling DSM: Microsoft DSM
    SN: 600A098038314853475D543544614131
    Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077040001 Active/Optimized   004|000|001|000   0
        TPG_State : Active/Optimized  , TPG_Id: 1000, : 25

    0000000077040000 Active/Optimized   004|000|000|000   0
        TPG_State : Active/Optimized  , TPG_Id: 1001, : 26
      PS C:\> mpclaim.exe -s -d
For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.

MPIO Disk    System Disk  LB Policy    DSM Name
-------------------------------------------------------------------------------
MPIO Disk3   Disk 1       RR           Microsoft DSM

PS C:\> mpclaim.exe -s -d 3
MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
    Controlling DSM: Microsoft DSM
    SN: 600A098038314853475D543544614131
    Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077040001 Active/Optimized   004|000|001|000   0
        TPG_State : Active/Optimized  , TPG_Id: 1000, : 25

    0000000077040000 Active/Optimized   004|000|000|000   0
        TPG_State : Active/Optimized  , TPG_Id: 1001, : 26
      Code block. Check Multipath I/O Disk list and path
    • Check in Disk Management.

Block Storage(BM) Check detailed information

Block Storage(BM) service can view and edit the complete resource list and detailed information. Block Storage(BM) Details page consists of Details, Snapshot List, Replication, Operation History tabs.

To view detailed information about the Block Storage(BM) service, follow these steps.

  1. All Services > Storage > Block Storage (BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List Navigate to the page.
  3. Block Storage(BM) list On the page, click the resource to view detailed information. 3. Navigate to the Block Storage(BM) Details page.
    • The Block Storage(BM) Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Tags, Operation History tabs.
      CategoryDetailed description
      Volume statusVolume status
      • Creating: In progress
      • Available: Creation complete, server connection available
      • Attaching: Connecting to server
      • Detaching: Disconnecting from server
      • In Use: Server connection established
      • Deleting: Service termination in progress
      • Editing: Changing settings
      • Error Deleting: Abnormal state during deletion
      • Error: Abnormal state during creation
      Clone creationCreate a replica in another location
      Create snapshotCreate a snapshot at a specific point in time
      Service cancellationCancel service button
      Table. Status information and additional functions
Reference
In the case of a recovery copy, snapshot list, replication tabs are not displayed.

Detailed Information

Block Storage(BM) List page lets you view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the Block Storage(BM) service, it refers to the volume SRN
Resource nameResource name
  • In the Block Storage(BM) service, it refers to the volume name
Resource IDService’s unique resource ID
ConstructorUser who created the service
Creation date and timeService creation timestamp
EditorUser who modified the service
Modification date and timeService modification date and time
Volume nameVolume Name
  • If you need to modify the volume name, click the Edit button
CategoryDistinguish original status related to duplication
Availability ZoneAvailability Zone information
Storage volume nameVolume name within the storage device
  • Information distinguishing volumes used for analysis when failures or issues occur
capacityVolume capacity
  • If you need to edit the volume name, click the Edit button
Max IOPSThe IOPS value set when creating the service
  • HDD type does not provide that metric
  • Click the Edit button to change the maximum IOPS value
Max ThroughputThroughput speed (MB/s) set when creating the service
  • HDD type does not provide this metric
  • Click the Edit button to change the maximum Throughput value
Disk typeDisk type
EncryptionEncryption status
  • Encryption is provided by default regardless of disk type
Volume GroupName of the Volume Group that the volume belongs to
iSCSI informationStorage target IP information for server connection
Snapshot capacitySnapshot storage capacity
  • Charges are incurred based on the configured capacity
  • Click the edit button if you need to set the snapshot capacity
Snapshot scheduleSnapshot automatic creation interval
  • You can register a schedule after setting the snapshot capacity
  • Click the edit button to set a snapshot schedule
Recovery copySnapshot name
  • Displayed when a snapshot exists
  • Click the name to go to the snapshot’s detail page
Connection serverConnected Bare Metal Server
  • Server Name: Server name
  • Image: Server OS image
  • Status: Server status
  • When adding a Bare Metal Server connection, click the Add button
  • When removing a Bare Metal Server connection, click the Disconnect button
Table. Block Storage (BM) Detailed Information Items
Reference
For volumes created before December 18, 2025, IOPS and Throughput information is not displayed.

Snapshot List

On the Block Storage(BM) List page, you can view the snapshot of the selected resource.

CategoryDetailed description
Snapshot usageTotal size of stored snapshots
Snapshot nameSnapshot name
capacitySnapshot capacity
Creation date and timeSnapshot creation time
Additional features > MoreSnapshot management button
  • Create restore copy: Create a restore copy from a snapshot
DeleteSelect the snapshots to delete from the snapshot list and delete them all at once.
Table. Snapshot list tab detail information items
Caution
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots are deleted first.
  • If the snapshot capacity usage is high (around 90%), replication may be stopped.
  • Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically generated via schedule), and if the maximum number is exceeded, no further snapshots can be created.
  • Snapshot recovery must be performed while all connected servers are disconnected (Umount, Disk Offline), and the recovered volume can be used after it is reconnected (Mount, Disk Online).
  • Only one recovery copy can be created, and it is a separate volume that incurs the same charges as the original.
Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00).
  • When using replication, snapmirror files cannot be deleted.
  • When using a Volume Group, set the snapshot schedule on the Volume Group (BM) details screen. * The generated snapshot can be viewed in the Block Storage (BM) snapshot list.

Replication

On the Block Storage(BM) List page, you can view the replication information of the selected resource.

CategoryDetailed description
Replication PolicyUser-defined replication policy
Replication cycleUser-configured source replication interval
Replication statusReplication progress status based on policy settings
Lag TimeTime elapsed since the last successful replication
  • Available after creating the replica
Volume informationVolume information for the source and replica
  • Classification: Distinguish whether it is the source for replication
  • Volume Name: Name of the source or replica volume
  • Region: Region information when creating cross-region replication
  • Availability Zone: Information about the Availability Zone where the replica is created
  • Permissions: User permissions for the volume as set by the replication policy
Table. Clone tab detailed information items
Caution
If the snapshot capacity usage is high (around 90%), replication may be stopped.
Reference
  • When a replica is created, a copy with the same disk type is generated.
  • You can create a replica after setting the snapshot capacity.
  • If you are using a Volume Group, check the replication information on the Volume Group (BM) list page.
  • A replica can modify the connected server when the replication policy is stopped or deleted.
  • Replicas can use the snapshot feature after the replication policy is deleted.
  • If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule on the replica.

Tag

On the Block Storage(BM) List page, you can view the tag information of the selected resource and add, modify, or delete it.

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the previously created Key and Value list
Table. Block Storage (BM) Tag Tab Items

Operation History

Block Storage(BM) List You can view the operation history of the selected resource on the page.

CategoryDetailed description
Task History ListResource Change History
  • Operation Time, Resource Type, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Operator Information
  • Click the Advanced Search button to perform a detailed search
Table. Detailed information items for the Work History tab

Block Storage(BM) Managing Resources

If you need to modify the settings of a created Block Storage (BM) or add or remove connected servers, you can perform the operation on the Block Storage (BM) Details page.

Edit Volume Name

You can edit the volume name. To modify the volume name, follow these steps.

  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Navigate to the Block Storage (BM) List page.
  3. Click the resource to edit the volume name on the Block Storage(BM) List page. 3. Block Storage(BM) Details Navigate to the page.
  4. Click the Edit button of Volume Name. 4. Edit Volume Name The popup window opens.
  5. Enter the volume name and click the Confirm button.
Reference
It must start with an English letter and can be set using English letters, numbers, and special characters (-) within 3 to 28 characters.

Expand Capacity

You can expand the volume capacity. To expand capacity, follow these steps.

  1. Click the All Services > Storage > Block Storage(BM) menu. 1. Navigate to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List Go to the page.
  3. On the Block Storage(BM) List page, click the resource to expand the capacity. 3. Navigate to the Block Storage(BM) Details page.
  4. Click the Edit button of Capacity. 4. Modify Capacity The popup window opens.
  5. After adding the capacity you wish to expand (1 ~ 16,384 GB) to the current capacity and entering the total capacity, click the Confirm button.
Caution
  • Capacity can be expanded only for the original volume that does not use the snapshot feature.
  • Size reduction is not provided.

Modify snapshot size

You can modify the capacity of the snapshot storage space. To modify the snapshot size, follow these steps.

  1. Click the All Services > Storage > Block Storage(BM) menu. 1. Go to the Service Home page of Block Storage (BM).
  2. Click the Block Storage(BM) menu on the Service Home page. 2. Block Storage(BM) List Navigate to the page.
  3. Block Storage(BM) List page, click the resource to modify the snapshot capacity. 3. Block Storage(BM) Details Navigate to the page.
  4. Click the Edit button of the Snapshot Capacity item. 4. Snapshot Capacity Edit The popup window opens.
  5. Set the Use status and Generation Capacity (%), then click the Confirm button.
    • Generation Capacity(%) can be selected in increments of 50 between 100 ~ 500.
Caution
  • Charges vary based on snapshot usage and capacity. * (Example: when the volume size is 10 GB and the snapshot creation size is 100%, a total of 20 GB charge occurs)
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots are deleted first.
  • If the size after modification is smaller than the original, older snapshots will be deleted first.
  • If you change it to unused, all snapshots will be deleted.
  • You can create a replica after setting the snapshot capacity.
  • After setting the snapshot size, you can add it to the Volume Group.
  • If the snapshot capacity usage is high (around 90%), replication may be stopped.
  • Replicas can use the snapshot feature after the replication policy has been deleted.

Edit Snapshot Schedule

You can modify the snapshot auto-creation interval. To modify the snapshot schedule, follow these steps.

  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
  2. From the Service Home page, click the Block Storage(BM) menu. 2. Block Storage (BM) List Go to the page.
  3. Block Storage(BM) List page, click the resource to modify the snapshot schedule. 3. Block Storage(BM) Details Go to the page.
  4. Click the Edit button for the Snapshot Schedule item. 4. Edit Snapshot Schedule The popup window opens.
  5. Configure the snapshot auto creation setting and creation interval, then click the Confirm button.
    • If you want to automatically create snapshots based on the Creation interval, select Automatic creation as Enabled.
    • Generation cycle can be selected as daily, hourly, or as weekly, day of week, hourly.
Caution
Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically generated through scheduling), and if the maximum number is exceeded, no further snapshots can be created.
Reference
  • The snapshot schedule is based on Asia/Seoul (GMT +09:00).
  • You can register a schedule after setting the snapshot capacity.
  • When configuring a snapshot schedule, it cannot be added to a Volume Group.

Update Max IOPS

You can modify the Max IOPS value. To modify the Max IOPS value, follow these steps.

  1. Click the All Services > Storage > Block Storage(BM) menu. 1. Navigate to the Service Home page of Block Storage (BM).
  2. Click the Block Storage(BM) menu on the Service Home page. 2. Go to the Block Storage(BM) List page.
  3. Block Storage(BM) list On the page, click the resource to modify the IOPS value. 3. Block Storage(BM) Details Navigate to the page.
  4. Click the Edit button of Max IOPS. 4. Edit Max IOPS The popup window opens.
  5. After entering the Max IOPS value to change, click the Confirm button.
    • The Max IOPS value can be set to a value between 5,000 and 20,000.
Reference
  • The Max IOPS value can be modified after the server is initially attached.
  • For a recovery copy, the Max IOPS value cannot be modified.

Edit Max Throughput

You can modify the Max Throughput speed. To modify the Max Throughput speed, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List Navigate to the page.
  3. On the Block Storage(BM) List page, click the resource whose Throughput speed you want to modify. 3. Block Storage(BM) Details Navigate to the page.
  4. Click the Edit button of Max Throughput. 4. Max Throughput edit The popup window opens.
  5. After entering the Max Throughput speed to change, click the Confirm button.
    • The Max Throughput speed can be set to a value between 250 and 1,000.
Reference
  • The Max Throughput speed can be modified after the initial server attach.
  • For recovery copies, the Max Throughput speed cannot be modified.

Edit connection server

You can connect or disconnect the Bare Metal Server, Multi Node GPU Cluster. To modify the connection server, follow these steps.

  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List page.
  3. Block Storage(BM) List page, click the resource to edit the connected server. 3. Block Storage(BM) Details Go to the page.
  4. If you are adding a connection server, click the Add button in the Connection Server item. 4. Add Connection Server popup window opens.
  5. After selecting the server you want to connect to, click the Confirm button.
  6. When disconnecting the server, click the Connection Server Disconnect button.
    • Be sure to log into the server, perform the disconnect operations (Umount, Disk Offline), and then disconnect.
Caution
  • Connect to the server, perform the disconnect operations (Umount, Disk Offline), and then release the connected server. * If you release the connection without performing OS operations, a status error (Hang) may occur on the connected server. * For detailed information about server disconnection, refer to 서버 연결 해제하기.
Reference
  • You can connect up to 8 Bare Metal Servers created in the same location as the Block Storage.
  • There is no limit on the number of volume connections for a Bare Metal Server.
  • When adding a connected server, you can use it after performing the connection tasks (Mount, Disk Online) on the server. * For detailed information about server connections, please refer to 서버 연결하기.
  • Please connect to the server, perform the disconnect operations (Umount, Disk Offline), and then disconnect from the server.
  • If you release without OS operations, a status error (Hang) may occur on the connected server.
  • For detailed information on server disconnection, refer to 서버 연결 해제하기.
  • A replica can modify the connected server when the replication policy is stopped or deleted.

Block Storage(BM) Cancel

You can reduce operating costs by terminating unused Block Storage (BM). However, if you terminate the service, the currently operating service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may arise from the service interruption.

Caution
  • Be careful, as data cannot be recovered after termination.
  • If a connected server exists, you can terminate it after removing all associated resources.
  • A volume can be deleted only when it is in the Available or Error state.
  • If a replication policy is in use, you can cancel it after removing the policy from the connected replica.
  • If a Volume Group is in use, you can disconnect the associated Volume Group before terminating it.
  • If a recovery copy of the original exists, you can delete the recovery copy and then cancel.

To cancel Block Storage, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. 1. Navigate to the Service Home page of Block Storage (BM).
  2. On the Service Home page, click the Block Storage(BM) menu. 2. Navigate to the Block Storage (BM) List page.
  3. Block Storage(BM) List On the page, select the resource to terminate, and click the Terminate Service button.
    • After navigating to the detailed page of the resource to be terminated, you can also terminate it individually by clicking the Service Termination button.
  4. When the pop-up notifying service termination opens, enter Delete and then click the Confirm button.
  5. Once termination is complete, verify on the Block Storage(BM) List page that the resource has been terminated.
ServiceWatch metric
Connect to server