The page has been translated by Gen AI.

How-to Guides

The user can enter the required information for Block Storage (BM) and select detailed options through the Samsung Cloud Platform Console to create the service.

Block Storage(BM) Create

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

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

Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) Create button on the Service Home page. You will be taken to the Block Storage(BM) Create page.

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

Category	Required	Detailed description
Volume Name	Required	Volume Name Must start with an English letter and use English letters, numbers, and the special character (-) to input 3~28 characters Cannot be modified after service creation
Disk Type	Required	Select Disk Type SSD: High-performance general volume HDD: General volume Cannot be modified after service creation
Capacity	Required	Capacity Setting Enter a number between 1~16,384GB Cannot be modified after service creation
IOPS	Required	Enter IOPS value Enter a number between 3,000~16,000 HDD type does not provide performance metric setting function
Throughput	Required	Enter Throughput speed (MB/s) Enter a number between 125~1,000 HDD type does not provide performance metric setting function
Connection Server	Required	Select Connected Bare Metal Server Provide up to 8 Bare Metal Server connections No limit on the number of volumes that can be connected to a Bare Metal Server

Table. Block Storage(BM) Service Information Input Items

Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, check the created resources on the Block Storage (BM) List page.

Note

All volumes are encrypted by default with server-side encryption based on the AES-256 algorithm, regardless of disk type.
Snapshot schedule can be set on the detail page.
The performance metrics (IOPS, Throughput) of the configured storage are based on the maximum values and do not guarantee consistent values.

Caution

Capacity cannot be modified after service creation. If needed, add a volume to the same server.

iSCSI Setting up

Volumes created by the user in addition to the OS default volume require iSCSI configuration.

Block Storage(BM) Details page’s iSCSI information after checking the IP provided, follow the iSCSI configuration method for each OS.

Linux Operating System

Notice

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

Block Storage(BM) Check iSCSI information on the detail page.

All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
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.
Connection Server Check the server in the item and then connect.

Follow the procedure below to configure iSCSI.

Storage (target IP) Discover the 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 Storage (target IP). If 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 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

Set Auto Login so that it automatically logs in even after 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

Please confirm the final settings using the following command.
Color mode
[root@localhost ~]# lsblk
[root@localhost ~]# lsblk
Code block. Check configuration content

Windows Operating System

Notice

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

Block Storage(BM) Check iSCSI information on the detail page.

All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
Service Home page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
Click the resource to be used on the connected server on the Block Storage(BM) List page. It moves to the Block Storage(BM) Details page.
After checking the server in the Connection Server item, connect.

Follow the procedure below to configure iSCSI.

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. Volume service start

Please 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

Please 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 you are an Active Directory Member.

iqn is generated based on the Hostname, but when joined to Active Dicrectory it changes to DNS format.
Based on the basic hostname, it is registered in Storage, so for iqn.1991-05.com.microsoft:iqn01.scp.com, iqn01 is the Hostname. Remove 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. Initiator Port Address Edit

Storage (target Portal) Set the 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 Storage (target Portal) address as 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 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 query occurs if a reboot is required. Reboot by entering Y or the Enter Key.

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

Multipath I/O Disk Check the list and path.
mpclaim.exe can be used to check MPIO disk information. 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. Multipath I/O Disk list and path verification

Please check in Disk Management.

Block Storage(BM) Check Detailed Information

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

To view detailed information of the Block Storage (BM) service, follow the steps below.

All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.

Click the resource to view detailed information on the Block Storage(BM) List page. 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.

Category	Detailed description
Volume Status	Status of the volume Creating: Creating 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 during creation
Create Replication	Create a replica at another location For detailed information about replication creation, see Create Replication
Snapshot Creation	Create a snapshot at a specific point in time For detailed information on snapshot creation, see Create Snapshot
Service termination	Button to cancel the service

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 allows you to view detailed information of the selected resource and, if necessary, edit the information.

Category	Detailed description
service	service name
Resource Type	Resource Type
SRN	Unique resource ID in Samsung Cloud Platform In the Block Storage (BM) service, it refers to the volume SRN
Resource Name	Resource Name In Block Storage(BM) service, it refers to the volume name
Resource ID	Unique resource ID of the service
Creator	User who created the service
Creation time	Date/time the service was created
Editor	User who modified the service
Modification Date/Time	Date/Time when the service was modified
Volume Name	Volume Name If you need to edit the volume name, click the Edit button For detailed information on editing the volume name, see Edit Volume Name
Category	Original status regarding duplication
Storage Volume Name	Volume name within storage device Information distinguishing the volume used for analysis when failures and issues occur
capacity	volume capacity
IOPS	IOPS value set when creating service HDD type does not provide this metric
Throughput	Throughput speed (MB/s) set when creating the service HDD type does not provide this metric
Disk type	Disk type
Encryption	Encryption status Encryption provided by default regardless of disk type
Volume Group	Name of the Volume Group that the volume belongs to
iSCSI information	Storage Target IP information for server connection
Snapshot Capacity	Capacity of snapshot storage space Charges incurred according to the set capacity Click the edit button if you need to set snapshot capacity For detailed information on snapshot capacity, refer to Edit Snapshot Capacity
Snapshot Schedule	Snapshot automatic creation cycle After setting snapshot capacity, schedule can be registered Click the edit button when snapshot schedule setting is needed For detailed information on snapshot schedule, refer to Edit Snapshot Schedule
Snapshot	Name of the snapshot Display when a snapshot exists Click the name to go to the snapshot’s detail page For details on creating a snapshot, see Create Snapshot
Connected Server	Connected Bare Metal Server Server Name: Server Name Image: Server’s 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 For more details about the connected server, see Edit Connected Server

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 allows you to view the snapshot of the selected resource.

Category	Detailed description
Snapshot Usage	Total Capacity of Stored Snapshots
Snapshot name	Snapshot name
Capacity	Snapshot Capacity
Creation Time	Snapshot Creation Time
Additional features > More	Snapshot management button Restore: Restore volume from snapshot For detailed information on snapshot restore, see Snapshot restore Create restore point: Create restore point from snapshot For detailed information on creating restore point, see Create restore point Delete: Delete snapshot For detailed information on snapshot deletion, see Delete snapshot

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 will be deleted.
If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
Snapshots can be created up to a maximum of 1,023 (the automatic creation count via schedule is up to 128), and if the maximum creation count is exceeded, no more 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 being 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

Snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
Snapmirror files cannot be deleted when using replication.
When using 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.

Replication

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

Category	Detailed description
Replication Policy	Replication policy set by the user For detailed information on modifying the replication policy, see Modify Replication Policy
Replication Cycle	Replication cycle of the original set by the user For detailed information on modifying the replication cycle, see Modify Replication Cycle
Replication Status	Replication progress status according to policy settings
Volume Information	Volume information of original and replica Classification: Distinguish whether original related to replication Volume Name: Volume name of original or replica Location: Location where the volume was created Permissions: User permissions of the volume set according to replication policy

Table. Replication Tab Detailed Information Items

Caution

If the snapshot capacity usage rate is high (around 90%), replication may be stopped.

Reference

When creating a clone, a replica with the same disk type is created.
After setting the snapshot capacity, you can create a replica.
If using Volume Group, check the replication information on the Volume Group (BM) list page.
A replica can modify the connected server if the replication policy is stopped or deleted.
The 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.

Category	Detailed description
Tag List	Tag List You can check the Key and Value information of tags Up to 50 tags can be added per resource When entering tags, search and select from the previously created Key and Value list

Work History

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

Category	Detailed description
Work History List	Resource Change History Work date and time, resource type, resource ID, resource name, work details, event topic, work result, verify worker information Click the detailed search button to perform a detailed search

Block Storage(BM) Resource Management

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

Edit Volume Name

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

All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
Block Storage(BM) List Click the resource to edit the volume name. Block Storage(BM) Details page will be opened.
Click the Edit button of Volume Name. Volume Name Edit popup opens.
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 the special character (-) within 3 to 28 characters.

Modify Snapshot Capacity

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

All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) list page.
Block Storage(BM) List page, click the resource to modify the snapshot capacity. Block Storage(BM) Details page will be opened.
Click the Edit button of the Snapshot Capacity item. The Snapshot Capacity Edit popup window opens.
Set the Usage status and Generation Capacity (%), and click the Confirm button.
- Generation capacity(%) can be selected in units of 50 between 100 and 500.

Caution

The charges change depending on whether snapshots are used and their size. (Example: If the volume size is 10GB and the snapshot creation size is 100%, a total of 20GB charges occur.)
If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
If the size after modification is smaller than the original, older snapshots will be deleted first.
When edited as unused, all snapshots will be deleted.
Replication can be created after setting snapshot capacity.
After setting the snapshot capacity, it can be added to the Volume Group.
If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
The replica can use the snapshot feature after the replication policy is deleted.

Edit Snapshot Schedule

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

All Services > Storage > Block Storage(BM) menu, click it. Navigate to the Service Home page of Block Storage(BM).
Service Home page에서 Block Storage(BM) 메뉴를 클릭하세요. Block Storage(BM) 목록 페이지로 이동합니다.
Block Storage(BM) List on the page, click the resource to edit the snapshot schedule. Block Storage(BM) Details page will be opened.
Click the Snapshot Schedule Edit button. The Snapshot Schedule Edit popup opens.
Set the snapshot auto generation status and generation interval, and click the Confirm button.
- Creation Cycle based, if you want to automatically create snapshots, select Auto Creation as Enabled.
- Generation cycle can be selected daily, hourly, or weekly, day of week, hourly.

Caution

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 more snapshots can be created.

Note

The snapshot schedule is based on Asia/Seoul (GMT +09:00).
After setting snapshot capacity, schedule registration is possible.
When setting a snapshot schedule, it cannot be added to the Volume Group.

Modify IOPS

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

All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) list page.
Click the resource to modify the IOPS value on the Block Storage(BM) List page. It moves to the Block Storage(BM) Details page.
Click the Edit button of IOPS. The IOPS Edit popup opens.
After entering the IOPS value to change, click the Confirm button.
- IOPS value can be entered between 3,000 and 16,000.

Reference

The IOPS value can be modified after the initial server attach.
In the case of a recovery copy, the IOPS value cannot be modified.

Throughput Edit

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

All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) List page.
Click the resource to modify the Throughput speed on the Block Storage(BM) List page. Block Storage(BM) Details page will be opened.
Click the Edit button of Throughput. Throughput Edit popup window opens.
After entering the Throughput speed to change, click the Confirm button.
- Throughput speed can be set to a value between 125 and 1,000.

Reference

Throughput speed can be modified after the initial server attach.
In the case of a recovery copy, the Throughput speed cannot be modified.

Edit Connection Server

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

All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
Service Home page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
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.
If you want to add a connection server, click the Add button in the Connection Server item. The Add Connection Server popup window will open.
After selecting the server you want to connect to, click the Confirm button.
If you want to disconnect the server, click the Disconnect button in the Connection Server item.
- Be sure to connect to the server and perform the disconnect operation (Umount, Disk Offline) before disconnecting.

Caution

Connect to the server and be sure to perform disconnect operations (Umount, Disk Offline) before releasing the connected server. If you release without OS operations, a status error (Hang) may occur on the connected server. For detailed information on server disconnect, see Disconnect Server.

Reference

You can connect up to 8 Bare Metal Servers created in the same location as Block Storage.
There is no limit on the number of volume connections for Bare Metal Server.
When adding a connected server, you can use it after performing connection tasks (Mount, Disk Online) on the server. For detailed information about server connection, refer to Server Connection.
Please connect to the server and be sure to perform disconnect operations (Umount, Disk Offline) before releasing the connected server. If you release without OS operations, a status error (Hang) may occur on the connected server. For detailed information on server disconnect, refer to Disconnect Server.
If the replica’s replication policy is stopped or deleted, the connected server can be modified.

Block Storage(BM) Cancel

You can reduce operating costs by terminating unused Block Storage (BM). However, if you terminate the service, the running service may be immediately stopped, so you should consider the impact of service interruption sufficiently before proceeding with the termination.

Caution

After termination, you cannot recover data, so be careful.
If there is a connected server, you can cancel after removing all connected resources.
The volume can be terminated only when it is in Available or Error state.
If you are using a replication policy, you can cancel it after deleting the replication policy from the connected replica.
If a Volume Group is being used, you can cancel it after disconnecting the connected Volume Group.
If there is a backup of the original, you can delete the backup and then cancel.

To cancel Block Storage, follow the steps below.

All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) List page.
On the Block Storage(BM) List page, select the resource to terminate, and click the Terminate Service button.
When termination is complete, check whether the resource has been terminated on the Block Storage(BM) List page.

Monitoring Metrics

Connecting to a Server