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. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).

  2. Click the Block Storage(BM) Create button on the Service Home page. You will be taken to the Block Storage(BM) Create page.

  3. Block Storage(BM) Creation page, input the information needed to create the service, and choose detailed options.

    Category
    Required status
    		Detailed description
    Volume nameRequiredVolume name
    • must start with an English letter and be 3~28 characters using English letters, numbers, and special characters (-)
    • cannot be modified after service creation
    Disk typeRequiredSelect Disk Type
    • SSD: High-performance general volume
    • HDD: General volume
    • Cannot be modified after service creation
    capacityRequiredCapacity setting
    • Enter a number between 1~16,384 GB
    • Cannot be modified after service creation
    Max IOPSRequiredEnter IOPS value
    • Enter a number between 5,000~20,000
    • HDD type does not provide performance metric setting function
    Max ThroughputRequiredEnter the throughput speed (MB/s)
    • Enter a number between 250~1,000
    • HDD type does not provide performance metric configuration functionality
    Connection serverRequiredConnect Bare Metal Server selection
    • Provides 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. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.

    • Once creation is complete, check the created resources on the Block Storage(BM) List page.
Reference
  • 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 original volumes that do not use the snapshot feature. For volumes that use snapshots, add the volume to the attached server to secure additional capacity.

Configure iSCSI

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

After checking the IP provided in the iSCSI Information on the Block Storage(BM) Details page, follow the iSCSI configuration steps for each OS.

Linux operating system

information

The iSCSI information (Storage Target IP) was written assuming 10.40.40.41, 10.40.40.42.

  • Check the iSCSI information on the Block Storage (BM) detail page.
  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken 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. You will be taken to the Block Storage(BM) Details page.
  4. Connection Server item, verify the server and then connect.
  5. Proceed with iSCSI configuration by referring to the steps below.
    • Discover the connection information for the Storage (target IP).
      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 verify the additional disk.
      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
    • Configure Auto Login to log 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 configuration using the following command.
      Color mode
      [root@localhost ~]# lsblk
      [root@localhost ~]# lsblk
      Code block. Verify configuration.

Windows operating system

guide

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

  • Check the iSCSI information on the Block Storage (BM) detail page.
  1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken 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. You will be taken to the Block Storage(BM) Details page.
  4. After checking the server in the Connection Server item, 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. powershell execution
    • 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 displayed 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 only needs to be modified when you are an Active Directory member.
      • iqn is generated based on the hostname, but when joined to Active Directory, it is changed to DNS format.
        Since it is registered in 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 Storage (target Portal) address 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 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. Storage (target) information Refresh
    • Register the Multipath I/O DSM and create an MPIO Disk.
      When creating an MPIO disk, a prompt appears if a reboot is required. 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. Multipath I/O DSM registration, MPIO Disk creation
    • Check the list and path of Multipath I/O disks.
      You can check MPIO disk information using the mpclaim.exe command. Enter the generated MPIO disk number to view 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.

View detailed information of Block Storage (BM)

Block Storage(BM) service allows you to view and edit the full 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. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource to view detailed information. You will be taken to the Block Storage(BM) Details page.
    • 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 completed, server connection possible
      • 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 while deleting
      • Error: Abnormal state while creating
      Clone creationCreate a replica in a different location
      Create snapshotCreate a snapshot at a specific point in time
      Service terminationCancel service button
      Table. Status information and additional features
Reference
For recovery copies, the Snapshot List and Replication tabs are not displayed.

Detailed information

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

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/TimeService creation timestamp
EditorUser who modified the service
Modification dateDate and time the service was modified
Volume nameVolume Name
  • If you need to modify the volume name, click the Edit button
  • For detailed information on modifying the volume name, refer to Modify Volume Name reference
CategoryDistinguish original status regarding duplication
Storage volume nameVolume name within the storage device
  • Information distinguishing the volume used for analysis when failures or issues occur
capacityVolume size
  • 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 this 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 the volume belongs to
iSCSI informationStorage Target IP information for server connection
Snapshot capacitySnapshot storage capacity
  • Charges are incurred based on the configured capacity
  • If you need to set the snapshot capacity, click the Edit button
Snapshot scheduleSnapshot auto-creation interval
  • Schedule can be registered after setting snapshot size
  • Click the edit button if you need 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’s OS image
  • Status: Server status
  • To add a Bare Metal Server connection, click the Add button
  • To remove 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

Block Storage(BM) List page lets you view the snapshot of the selected resource.

CategoryDetailed description
Snapshot usageTotal size of stored snapshots
Snapshot nameSnapshot name
capacitySnapshot capacity
Creation Date/TimeSnapshot creation time
Additional features > MoreSnapshot management button
  • Restore: Restore volume from snapshot
  • Create restore copy: Generate a restore copy from a snapshot
  • Delete: Delete snapshot
DeleteSelect the snapshots to delete from the snapshot list and delete them all at once.
Table. Snapshot list tab detailed 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 created 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 restored volume can be used after it is reconnected (Mount, Disk Online).
  • A recovery copy can only be created once, and it is a separate volume that incurs charges identical to the original.
Reference
  • The snapshot creation date and 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) detail information screen. The created snapshots can be viewed in the Block Storage (BM) snapshot list.

Clone

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

CategoryDetailed description
Replication PolicyUser-configured replication policy
Replication cycleReplication interval of the source set by the user
Replication statusReplication progress status according to policy settings
Lag TimeTime elapsed since the last successful replication
  • Available after the replica is created
Volume informationVolume information for original and replica
  • Classification: Indicates whether it is the original in replication
  • Volume Name: The volume name of the original or replica
  • Location: The location where the volume was created
  • Permissions: User permissions of the volume set according to the replication policy
Table. Replication 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.
  • Replication can be created after configuring the snapshot size.
  • 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.
  • A replica 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 in 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 list of previously created Keys and Values
Table. Block Storage (BM) tag tab item

Work History

Block Storage(BM) List page allows you to view the operation history of the selected resource.

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

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 tasks on the Block Storage(BM) Details page.

Edit volume name

You can modify the name of a volume. To rename a volume, follow these steps.

  1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource whose volume name you want to edit. You will be taken to the Block Storage(BM) Details page.
  4. Click the Edit button for Volume name. The Edit Volume Name popup opens.
  5. Enter the volume name and click the Confirm button.
Reference
Must start with a letter and can be set using letters, numbers, and special characters (-) within 3 to 28 characters.

Increase capacity

You can increase the volume size. To increase the size, follow the steps below.

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource to expand its capacity. You will be taken to the Block Storage(BM) Details page.
  4. Click the capacity edit button. The Capacity Edit popup opens.
  5. After adding the capacity you want to expand (1/~16,384 GB) to the current capacity and entering the total, 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. To modify the snapshot capacity, follow these steps.

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List page: click the resource to modify the snapshot capacity. You will be taken to the Block Storage(BM) Details page.
  4. Click the Edit button of the Snapshot Capacity item. The Snapshot Capacity Edit 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 and ~500.
Caution
  • Charges vary depending on snapshot usage and size. (Example: with a volume size of 10 GB and snapshot creation size of 100%, a total of 20 GB is billed.)
  • 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.
  • When changed to unused, all snapshots will be deleted.
  • Replication can be created after setting the snapshot capacity.
  • After configuring the snapshot size, it can be added 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 automatic snapshot creation interval. To modify the snapshot schedule, follow these steps.

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource to edit the snapshot schedule. You will be taken to the Block Storage(BM) Details page.
  4. Click the Edit button for the Snapshot Schedule item. The Snapshot Schedule Edit popup opens.
  5. Set the snapshot auto creation status and creation interval, then click the Confirm button.
    • If you want to automatically create snapshots based on the creation cycle, select automatic creation as enabled.
    • Select the generation cycle 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 via schedule), 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 configuring the snapshot capacity.
  • You cannot add it to a Volume Group when configuring a snapshot schedule.

Edit Max IOPS

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

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List page, click the resource whose IOPS value you want to modify. You will be taken to the Block Storage(BM) Details page.
  4. Click the Edit button of Max IOPS. The Max IOPS Edit popup 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. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. From the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List on the page, click the resource to modify the Throughput speed. You will be taken to the Block Storage(BM) Details page.
  4. Click the Edit button of Max Throughput. The Max Throughput Edit popup 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 adjusted.

Edit Connection Server

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

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource to edit the connected server. You will be taken to the Block Storage(BM) Details page.
  4. When adding a connection server, click the Add button in the Connection Server item. The Add Connection Server popup opens.
  5. After selecting the server you want to connect to, click the Confirm button.
  6. If you need to disconnect the server, click the Disconnect button in the Connection Server field.
    • Be sure to log into the server, perform the disconnect operations (Umount, Disk Offline), and then disconnect.
Caution
  • Connect to the server and be sure to perform the disconnect operations (Umount, Disk Offline) before detaching the connected server. Detaching without OS operations may cause a status error (Hang) on the connected server. For detailed information on detaching the server, refer to Detaching the Server.
Reference
  • You can connect up to eight 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, refer to Server Connection Guide.
  • Connect to the server and be sure to perform the disconnect operations (Umount, Disk Offline) before detaching the connected server. Detaching without OS operations may cause a status error (Hang) on the connected server. For detailed information on detaching the server, refer to Detach Server.
  • A replica can modify the connected server when the replication policy is stopped or deleted.

Cancel Block Storage(BM)

You can reduce operating costs by terminating unused Block Storage(BM). However, terminating the service may cause the running service to stop immediately, so you should carefully consider the impact of service interruption before proceeding with the termination.

Caution
  • Please note that data cannot be recovered after termination.
  • If a connected server exists, you can terminate it after removing all associated resources.
  • You can only delete the volume 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 associated replica.
  • If a Volume Group is being used, you can cancel after disconnecting the associated Volume Group.
  • If a recovery copy of the original exists, you can delete the recovery copy before terminating.

To cancel Block Storage, follow the steps below.

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, select the resource to terminate and click the Terminate Service button.
  4. After termination is complete, verify on the Block Storage(BM) List page that the resource has been terminated.
Monitoring Metrics
Connect to Server