Block Storage(BM)

• 1: Overview
• 1.1: Monitoring Metrics
• 2: How-to Guides
• 2.1: Connecting to a Server
• 2.2: Using Snapshots
• 2.3: Using Replication
• 2.4: Using Volume Group
• 3: API Reference
• 4: CLI Reference
• 5: Release Note

1 - Overview

Service Overview

Block Storage is a high-performance storage that stores data in block units with a certain size and arrangement.
It is suitable for large-capacity, high-performance requirements such as databases, mail servers, etc. and users can directly assign volumes to the server for use.

Key Features

• High-capacity volume provision: you can create volumes of up to 16TB in size.
• Full SSD-based high-performance delivery: Dualized Controller and Disk Array Raid-based, providing high durability and availability. Since the full SSD disk is provided by default, it is suitable for high-speed data processing tasks such as database workloads.
• Snapshot Backup: Through the image snapshot function, it is possible to recover data that has been changed or deleted. The user selects a snapshot created at the desired recovery point from the list and performs the recovery.
• Replication: creates identical replica volumes in different locations, and users can set the data replication cycle, in case the original volume is unavailable due to a disaster or failure, services can be provided through the replica volume.

Composition Diagram

Provided Function

Block Storage provides the following functions.

• Volume Name: The user can set or modify the name by volume.
• Capacity: Volume creation is possible with a capacity of at least 1GB and up to 16TB.
• Connection Server : Bare Metal Server, Multi Node GPU Cluster can be selected to connect or disconnect.
• Multi Attach: connect up to 5 servers, no limit on the number of volumes that can be attached to a Bare Metal Server
• Encryption: Regardless of the disk type, all volumes have AES-256 algorithm encryption enabled by default.
• Snapshot: You can create a snapshot at a specific point in time using the image snapshot feature or generate snapshots at regular intervals.
• Capacity: The capacity of snapshot storage space
• Schedule: snapshot automatic creation cycle
• Recovery: Restore the original volume to the latest snapshot, select a snapshot at a specific point in time to create a recovery volume
• Recovery volume a separate volume created with the same capacity as the original (incurring additional costs)
• Replication: replicates the volume to a different location, and users can set the replication cycle.
• The replica volume can also serve as the original role in the event of a disaster through the snapshot function
• Volume Group: Sets a group of up to 16 Block Storage volumes, allowing for snapshot and replication settings at the group level.
• Monitoring: You can check performance information such as IOPS, Latency, Throughput through the Cloud Monitoring service.

Components

You can create a volume by entering the capacity based on the user’s service size and performance requirements and selecting the disk type.
When using the snapshot function, you can restore the data to the point you want to restore.

Volume

Volume is the basic creation unit of the Block Storage service and is used as a data storage space. The user creates a volume by setting the name, capacity, disk type, snapshot, etc., and then connects and uses it to the Bare Metal Server.
The volume name creation rule is as follows.

• It starts with English and can be set within 3-28 characters using English, numbers, and special characters (-).

Snapshot

Snapshot is an image backup of a volume at a specific point in time. The user can select the snapshot to be recovered by checking the snapshot name and creation time in the snapshot list, and can recover the data changed or deleted through the snapshot.
The notes to refer to when using snapshots are as follows.

Volume Group

Volume Group is a group unit management function that allows users who have configured databases and applications with two or more volumes to create snapshots and replicas at a consistent point in time, users can create a Volume Group by selecting a name and target Block Storage.

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

1.1 - Monitoring Metrics

Block Storage BM Monitoring Metrics

The following table shows the monitoring metrics of Block Storage BM that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, please refer to the Cloud Monitoring guide.

2 - 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.

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 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

4. 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.

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

1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
3. 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 Check the server in the item and then connect.
5. Follow the procedure below to configure iSCSI.
   • Storage (target IP) Discover the connection information.
     Sample Code Download

     Copy Code

     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

   • Connect to Storage (target IP). If already connected, proceed to the next step.
     Sample Code Download

     Copy Code

     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.

   • To minimize search time, delete all unused Storage (target IP).
     Sample Code Download

     Copy Code

     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

   • Please rescan to check additional Disk.
     Sample Code Download

     Copy Code

     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]

   • Set Auto Login so that it automatically logs in even after reboot.
     Sample Code Download

     Copy Code

     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

   • Please confirm the final settings using the following command.
     Sample Code Download

     Copy Code

     Color mode

     [root@localhost ~]# lsblk

     [root@localhost ~]# lsblk

Windows Operating System

1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
2. Service Home page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
3. 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.
4. After checking the server in the Connection Server item, connect.
5. Follow the procedure below to configure iSCSI.
   • Open Command Prompt (Admin) and run PowerShell.
     Sample Code Download

     Copy Code

     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:\>

   • Start the volume service.
     Sample Code Download

     Copy Code

     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

   • Please install Multipath I/O. If the Restart Needed item is displayed as Yes, a restart is required.
     Sample Code Download

     Copy Code

     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}

   • 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.
       Sample Code Download

       Copy Code

       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

   • Storage (target Portal) Set the address as a variable.
     Sample Code Download

     Copy Code

     Color mode

     PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")

     PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")

   • Discover the Storage (target Portal).
     Sample Code Download

     Copy Code

     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          :

   • Connect the disk (target).
     Sample Code Download

     Copy Code

     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          :

   • Refresh Storage (target) information.
     Sample Code Download

     Copy Code

     Color mode

     PS C:\> Update-IscsiTarget

     PS C:\> Update-IscsiTarget

   • 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.
     Sample Code Download

     Copy Code

     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

   • 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.
     Sample Code Download

     Copy Code

     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

   • 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.

1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
3. 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

Detailed Information

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

Snapshot List

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

Replication

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

Tag

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

Work History

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

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.

1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
3. Block Storage(BM) List Click the resource to edit the volume name. Block Storage(BM) Details page will be opened.
4. Click the Edit button of Volume Name. Volume Name Edit popup opens.
5. Enter the volume name and click the Confirm button.

Modify Snapshot Capacity

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

1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
2. Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) list page.
3. Block Storage(BM) List page, click the resource to modify the snapshot capacity. Block Storage(BM) Details page will be opened.
4. Click the Edit button of the Snapshot Capacity item. The Snapshot Capacity Edit popup window opens.
5. 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.

Edit Snapshot Schedule

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

1. All Services > Storage > Block Storage(BM) menu, click it. Navigate to the Service Home page of Block Storage(BM).
2. Service Home page에서 Block Storage(BM) 메뉴를 클릭하세요. Block Storage(BM) 목록 페이지로 이동합니다.
3. Block Storage(BM) List on the page, click the resource to edit the snapshot schedule. Block Storage(BM) Details page will be opened.
4. Click the Snapshot Schedule Edit button. The Snapshot Schedule Edit popup opens.
5. 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.

Modify IOPS

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

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

Throughput Edit

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

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

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.

1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
2. Service Home page, click the Block Storage(BM) menu. Go 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. 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.
5. After selecting the server you want to connect to, click the Confirm button.
6. 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.

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.

To cancel Block Storage, follow the steps below.

1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
2. Click the Block Storage(BM) menu on the Service Home page. 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. When termination is complete, check whether the resource has been terminated on the Block Storage(BM) List page.

2.1 - Connecting to a Server

When using a volume on a server, a connection or disconnection operation is required.
When using a volume on a server, you need to perform a connection or disconnection operation. After adding a connection server on the Block Storage(BM) details page, access the server and perform Multi Path settings and connection operations (Mount, Disk Online). After completing the use, perform disconnection operations (Umount, Disk Offline) and remove the connection server.

Configuring Multi Path

Before using a volume on a connection server, you need to configure Multi Path. Follow the procedure below.

Linux Operating System

1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

3. On the Block Storage(BM) list page, click the resource you want to set up Multi Path for. The Block Storage(BM) details page will be displayed.

4. In the Connected Server section, check the server and access it. Follow the guide below to configure Multi Path.

   • Device confirmation

     1. The created volume can be confirmed using the fdisk -l command.

   • DM-Multipath application confirmation

     1. The Linux system automatically applies Multi Path during the volume recognition process, and you can confirm it using the multipath –ll command.
     2. The volume with Multi Path applied uses a Multipath device name in the format /dev/mapper/#####, not /dev/sd#, and can be confirmed using the fdisk –l command.

   • iSCSI replacement timeout value setting

     1. Set the replacement timeout when connecting to iSCSI.

     # vi /etc/iscsi/iscsid.conf
     node.session.timeo.replacement_timeout = 5
     (change the default value of 120 to 5)
     

     2. After changing the above content, restart the iSCSI service

     # systemctl restart iscsid
     

Windows Operating System

1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

3. On the Block Storage(BM) list page, click the resource you want to set up Multi Path for. The Block Storage(BM) details page will be displayed.

4. In the Connected Server section, check the server and access it. Follow the guide below to configure Multi Path.

   • Device confirmation

     1. Click the Start > Server Manager menu to run Server Manager.
     2. Click Server Manager > File and Storage Services > Volumes > Disks to confirm the iscsi device.
     3. Before setting up Multi Path, one device appears as multiple devices for each path.

   • MPIO installation (Reboot required)

     1. Click Server Manager > Dashboard > Add roles and features.

     2. The Add Roles and Features Wizard popup window will open. Click the Next button.

     3. On the Select installation type page, select Role-based or feature-based installation and click the Next button.

     4. On the Select destination server page, the current server will be automatically searched. Confirm the content and click the Next button.

     5. On the Select features page, select Features on the left menu and check Multipath I/O. Then, click the Next button.

        

     6. On the Confirm installation selections page, check Restart the destination server automatically if required. If a popup window opens, click Yes and then click the Install button.

     7. The installation will start, and the server will automatically reboot.

     8. After reconnecting to the server, the installation will be complete. Click the Close button to close the Wizard popup window.

     9. Click Server Manager > Dashboard > Tools > MPIO.

        

     10. On the Discover Multi-Paths tab, check Add support for iSCSI devices and click the Add button.

         • If a message is displayed, reboot the server again.

     11. After the reboot is complete, you can confirm NETAPP Devices in MPIO devices.

         

     12. Run diskmgmt.msc in the Windows execution window (command prompt) to open the Disk Management popup window.

         • You can confirm that MPIO is applied through the properties of the volume created in the Block Storage(BM) service.
           

Connecting to a Server (Mount, Disk Online)

To use a volume added to a connection server, you need to access the server and perform connection operations (Mount, Disk Online). Follow the procedure below.

Linux Operating System

1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

3. On the Block Storage(BM) list page, click the resource you want to connect to the server. The Block Storage(BM) details page will be displayed.

4. In the Connected Server section, check the server and access it. Follow the guide below to connect (Mount) the volume.

   • Switch to root privileges

     $ sudo -i
     

   • Confirm the disk

     # lsblk
     NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
     vda       252:0   0    24G  0 disk
     ├─vda1    252:1   0  23.9G  0 part [SWAP]
     └─vda14   252:14  0     4M  0 part /
     └─vda15   252:15  0   106M  0 part /boot/efi
     vdb       252:16  0    24G  0 disk
     

   • Create a partition

     # fdisk /dev/vdb
     Command (m for help): n
     
     Partition type:
        p   primary (0 primary, 0 extended, 4 free)
        e   extended
     Select (default p): p
     Partition number (1-4, default 1): 1
     First sector (2048-50331646, default 2048):
     Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-50331646, default 50331646):
     
     Created a new partition 1 of type 'Linux' and of size 24 GiB.
     
     Command (m for help): w
     The partition table has been altered!
     Calling ioctl() to re-read partition table.
     Syncing disks.
     

   • Set the partition format (e.g., ext4)

     # lsblk
     NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
     vda       252:0   0    24G  0 disk
     ├─vda1    252:1   0  23.9G  0 part [SWAP]
     └─vda14   252:14  0     4M  0 part /
     └─vda15   252:15  0   106M  0 part /boot/efi
     vdb       252:16  0    24G  0 disk
     └─vdb1    252:17  0    24G  0 part
     
     # mkfs.ext4 /dev/vdb1
     mke2fs 1.46.5 (30-Dec-2021)
     ...
     Writing superblocks and filesystem accounting information: done
     

   • Mount the volume

     # mkdir /data
     
     # mount /dev/vdb1 /data
     
     # lsblk
     NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
     vda       252:0   0    24G  0 disk
     ├─vda1    252:1   0  23.9G  0 part [SWAP]
     └─vda14   252:14  0     4M  0 part /
     └─vda15   252:15  0   106M  0 part /boot/efi
     vdb       252:16  0    24G  0 disk
     └─vdb1    252:17  0    24G  0 part /data
     
     # vi /etc/fstab
     (add) /dev/vdb1     /data       ext4     defaults   0 0
     

Windows Operating System

1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

3. On the Block Storage(BM) list page, click the resource you want to connect to the server. The Block Storage(BM) details page will be displayed.

4. In the Connected Server section, check the server and access it. Follow the guide below to connect (Disk Online) the volume.

   • Right-click the Windows Start icon and run Computer Management.

   • In the Computer Management tree structure, select Storage > Disk Management.

   • Confirm the disk

   

   • Set the disk to Online

   

   • Initialize the disk

   

   

   • Format the partition

   

   

   

   • Confirm the volume

   

Disconnecting from the Server (Umount, Disk Offline)

After disconnecting from the server (Umount, Disk Offline) and performing the disconnection work, you must disconnect the connected server from the Console. Follow the procedure below.

Linux Operating System

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

2. Click the Block Storage (BM) menu on the Service Home page. Move to the Block Storage (BM) list page.

3. Click the resource to be disconnected from the server on the Block Storage (BM) list page. Move to the Block Storage (BM) details page.

4. Check the server in the Connected Server item and access it. Follow the guide below to disconnect the volume (Umount).

   • Volume Umount

     # umount /dev/vdb1 /data
     
     # lsblk
     NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
     vda       252:0   0    24G  0 disk
     ├─vda1    252:1   0  23.9G  0 part [SWAP]
     └─vda14   252:14  0     4M  0 part /
     └─vda15   252:15  0   106M  0 part /boot/efi
     vdb       252:16  0    24G  0 disk
     └─vdb1    252:17  0    24G  0 part
     
     # vi /etc/fstab
     (delete) /dev/vdb1     /data       ext4     defaults   0 0
     

Windows Operating System

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

2. Click the Block Storage (BM) menu on the Service Home page. Move to the Block Storage (BM) list page.

3. Click the resource to be disconnected from the server on the Block Storage (BM) list page. Move to the Block Storage (BM) details page.

4. Check the server in the Connected Server item and access it. Follow the guide below to disconnect the volume (Disk Offline).

   • Right-click the Windows Start icon and run Computer Management

   • Select Storage > Disk Management in the Computer Management tree structure

   • Right-click the disk to be removed and run Offline

   

   • Check the disk status

   

2.2 - Using Snapshots

You can create, delete, or recover snapshots of the generated Block Storage (BM). You can perform actions on the Block Storage (BM) Details page and the Snapshot List page.

Create Snapshot

You can create a snapshot at the point in time you want. To create a snapshot, follow the steps below.

1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
3. Block Storage(BM) List page, click the resource to create a snapshot. Navigate to the Block Storage(BM) Details page.
4. Snapshot Capacity Check the setting status of the item.
   • Snapshots can only be created when storage space is secured by setting the snapshot capacity.
   • For more details, please refer to Modify Snapshot Capacity.
5. Click the Create Snapshot button. Create Snapshot popup window opens.
6. Confirm Click the button. Creates a snapshot of the current point in time.
7. Click the Snapshot List page. Go to the Block Storage(BM) Snapshot list page.
8. Check the generated snapshot.

Recover Snapshot

Block Storage(BM) volumes can be restored from a snapshot. To perform snapshot recovery, 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. Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) list page.
3. Block Storage(BM) List On the page, click the resource to restore from the snapshot. Block Storage(BM) Details Navigate to the page.
4. If there is a server added in the Connection Server item, after connecting to the server, perform the disconnect operation (Umount, Disk Offline).
   • For more details, please refer to Disconnect Server.
5. Snapshot List Click the page. Block Storage(BM) Snapshot List Go to the page.
6. After checking the Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to restore.
7. Recovery Click the button. The snapshot recovery popup window opens.
8. Snapshot Name and Creation Date and Time after checking, click the Confirm button. Recover the Block Storage volume as a snapshot.
9. Click the Details button. You will be taken to the Block Storage (BM) Details page.
10. Connection Server If there is a server added in the item, after connecting to the server, perform the connection tasks (Mount, Disk Online).
    • For more details, please refer to Connect to Server.

Create a recovery copy

Block Storage(BM) volume’s snapshot can be used to create a recovery copy. To create a snapshot recovery copy, follow the steps below.

1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
2. Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to restore from a snapshot. You will be taken to the Block Storage(BM) Details page.
4. Connection Server If there is a server added in the item, after connecting to the server, perform the disconnect operation (Umount, Disk Offline).
   • For more details, see Disconnect Server.
5. Snapshot List page, click it. Block Storage(BM) Snapshot List page, go to it.
6. After confirming the Snapshot name and Creation date/time, click the More button of the snapshot you want to create a recovery copy for.
7. Click the Create Recovery button. The snapshot recovery creation popup opens.
8. After entering the Recovery volume name, click the Confirm button. A popup notifying the creation of the recovery copy opens.
9. Click the Confirm button. The recovery copy creation request is completed.

Delete Snapshot

You can select a snapshot to delete. To delete a snapshot, follow the steps below.

1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
2. Service Home on the page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
3. Block Storage(BM) List page, click the resource to delete the snapshot. Block Storage(BM) Details page will be opened.
4. Click Snapshot List. Go to the Block Storage (BM) Snapshot List page.
5. After checking the Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to delete.
6. Click the Delete button. The snapshot will be removed from the Snapshot List page.

2.3 - Using Replication

You can create a replica in a different location of the created Block Storage(BM) and synchronize it periodically, and you can perform tasks on the Block Storage(BM) details page and the replication page.

Create a copy

You can create a replica volume in a different location. To create a replica volume, follow these steps.

1. All Services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
3. Block Storage(BM) list page, click on the resource to create a replica. It moves to the Block Storage(BM) details page.
4. Snapshot capacity item’s setting status should be checked.

• Replication creation is only possible when storage space is secured through snapshot capacity setting.
• For more detailed information, please refer to Modifying snapshot capacity.

5. Replicate Create button will be clicked. Replicate Create popup window will be opened.
6. Replication location and replication volume name, replication cycle should be entered and the confirm button should be clicked. It creates a replica with the same disk type.

• Replication location: Select a location different from the original Block Storage(BM) volume.
• Replica Volume Name: It should start with English and use English, numbers, and special characters(-) to input 3-28 characters.
• Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the selected cycle.
• Daily: every day 23:59:00
• Every week: every Sunday 23:59:00
• Every month: every month 1st 23:59:00

7. Replication page will be clicked. It moves to the Replication page.
8. Check the replication information.

• When selecting the volume name of the original or replica, it moves to the Block Storage(BM) details page of the volume.

Modify replication policy

You can change the replication status through replication policy modification.

To modify the replication policy, follow the following procedure.

1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
3. Block Storage(BM) list page, click the resource to modify the replication policy. It moves to the Block Storage(BM) details page.
4. Replication page is clicked. It moves to the Block Storage(BM) replication page.
5. Replication Policy’s Edit button should be clicked. Replication Policy Edit popup window will be opened.

• Usage: performs replication. Paused can be modified to Usage.
• Temporary suspension: temporarily suspends replication. If in use, it can be modified to temporary suspension.
• Delete: It deletes the replication. In case of pause, it can be modified to delete, and after deletion, replication cannot be used again.

6. Block Storage(BM) replication page, check the modified replication policy.

Modify replication cycle

You can change the synchronization cycle between the original and the copy through replication cycle modification.

To modify the replication cycle, follow the following procedure.

1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
3. Block Storage(BM) list page, click the resource to modify the replication cycle. It moves to the Block Storage(BM) details page.
4. Replication page will be clicked. It moves to the Block Storage(BM) replication page.
5. Replication Cycle’s Edit button should be clicked. Replication Cycle Edit popup window will be opened.

• Replication cycle: Select from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the selected cycle.
• Daily: every day 23:59:00
• Every week: every Sunday 23:59:00
• Every month: every month 1st 23:59:00

6. Block Storage(BM) replication page where you can check the modified replication cycle.

2.4 - Using Volume Group

Volume Group(BM) service allows you to create a group of up to 16 Block Storage(BM) volumes to create snapshots and replicas at a consistent point in time.
The user can enter the necessary information of the Volume Group (BM) through the Samsung Cloud Platform Console and select detailed options to create the corresponding service.

Creating Volume Group (BM)

You can create and use the Volume Group(BM) service on the Samsung Cloud Platform Console.

To create Block Storage, follow the next procedure.

1. All services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
2. Volume Group(BM) menu should be clicked. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) page, click the Volume Group(BM) creation button. It moves to the Volume Group(BM) creation page.

   Classification	Mandatory	Detailed Description
   Volume Group name	Required	Volume Group name Starts with English and uses English, numbers, and special characters (-) to input 3-28 characters Cannot be modified after service creation
   Target Volume	Required	Add target volume to Volume Group Add button is clicked, and then select the target volume in the target add popup Target volume basis Snapshot capacity: Setting Snapshot automatic creation, creation cycle: Not used Replication: Not used Up to 16 can be added

   Table. Volume Group(BM) Service Information Input Items
4. Complete button을 클릭하세요 -> 4. Complete button should be translated as: 4. Click the Complete button. So the final translation is: 4. Click the Complete button.

• Once creation is complete, check the created resource from the Volume Group(BM) list page.

Volume Group(BM) detailed information check

Volume Group(BM) service allows you to check and modify the entire resource list and detailed information. The Volume Group(BM) details page consists of detailed information, snapshot list, replication, job history tabs.

Volume Group(BM) service’s detailed information can be checked by following the next procedure.

1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click on the resource to check the detailed information. It moves to the Volume Group(BM) details page.

• Volume Group(BM) details page displays status information and additional feature information, and consists of details, snapshot list, replication, tags, job history tabs.

  Classification	Detailed Description
  Volume Group status	Volume Group’s status Creating: being created Available: creation completed, server connection available Deleting: service termination in progress Editing: settings being changed Error Deleting: abnormal state during deletion Error: abnormal state during creation
  Replication creation	Create a replica in a different location For more information on replication creation, see Replication Creation
  Creating a snapshot	Create a snapshot at a specific point in time For more information on creating a snapshot, see Creating a Snapshot
  Service Cancellation	Button to cancel the service

  Table. Status Information and Additional Functions

Detailed Information

Volume Group(BM) list page where you can check the detailed information of the selected resource and modify the information if necessary.

Snapshot list

Volume Group(BM) Resource List page where you can check the snapshot of the selected resource.

Replication

Volume Group(BM) Resource List page where you can check the replication information of the selected resource.

Tag

Volume Group(BM) list page where you can check the tag information of the selected resource, and add, change or delete it.

Work History

Volume Group(BM) Resource List page where you can check the work history of the selected resource.

Volume Group(BM) Resource Management

If you need to modify the settings of the created Volume Group(BM) or add or remove target volumes, you can perform the task on the Volume Group(BM) details page.

Modifying the Snapshot Schedule

You can modify the snapshot automatic creation cycle. To modify the snapshot schedule, follow the following procedure.

1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click the resource to modify the snapshot schedule. It moves to the Volume Group(BM) details page.
4. Snapshot Schedule item’s Edit button should be clicked. Snapshot Schedule Edit popup window will be opened.
5. Set the snapshot automatic creation and creation cycle, and click the confirm button.

• Creation Cycle basis to automatically create a snapshot, in the case of Auto Creation select Yes.
• Creation cycle can be selected as daily, hourly, or weekly, day of the week, hourly.

Modifying the target volume

You can add or detach the target volume. To modify the target volume, follow these procedures.

1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click the resource to modify the target volume. It moves to the Volume Group(BM) detail page.
4. If you add a target volume, click the Add button in the Target Volume item. The Add Volume popup window opens.

• If you want to disconnect the volume, click the Disconnect button in the Target Volume section.

5. Select the volume you want to add and then click the Confirm button.

Volume Group(BM) snapshot usage

You can create, delete a snapshot of the created Volume Group(BM), or restore it using a snapshot. You can perform tasks on the Volume Group(BM) details page and the Snapshot list page.

Creating a snapshot

The user can create a snapshot of the desired point in time. To create a snapshot, follow the following procedure.

1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click on the resource to create a snapshot. It moves to the Volume Group(BM) details page.
4. Create Snapshot button is clicked. Create Snapshot popup window is opened.
5. Confirm button, click. It creates a snapshot of the current point in time.
6. Snapshot List page, click. It moves to the Volume Group(BM) Snapshot list page.
7. Check the generated snapshot.

Restoring a snapshot

Volume Group(BM)’s target volumes can all be restored as snapshots. To restore as a snapshot, follow the following procedure.

1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click the resource to be restored with a snapshot. It moves to the Volume Group(BM) detail page.
4. Target Volume에 추가된 볼륨의 Volume Name을 클릭하세요. Block Storage(BM) Detail 페이지로 이동합니다. -> 4. Click the Volume Name of the volume added to the Target Volume. It moves to the Block Storage(BM) Detail page.
5. connected server item has a server added, after server connection, perform disconnect work (Umount, Disk Offline) please.

• Please refer to Server Connection Release for more detailed information.

6. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
7. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to restore.
8. Restore button, click. Snapshot restore popup window opens.
9. Snapshot name and Creation time are confirmed after clicking the Confirm button. The target volumes are restored as snapshots.
10. Detailed Information button will be clicked. It will move to the Volume Group(BM) Detail page.
11. Target Volume에 추가된 볼륨의 Volume Name을 클릭하세요. Block Storage(BM) Detail 페이지로 이동합니다.
12. connected server items have been added, after server connection, perform connection work (Mount, Disk Online)

• For more detailed information, please refer to 서버 연결하기 becomes * For more detailed information, please refer to Connect to Server

Creating a recovery version

You can create a replica from a snapshot of the target volume. To create a snapshot replica, follow these steps.

1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click on the resource to create a backup. It moves to the Volume Group(BM) details page.
4. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
5. Snapshot name and Creation time are confirmed, then click the More button of the snapshot you want to create a restore from.
6. Restore Point Creation button should be clicked. Snapshot restore point creation popup window will be opened.
7. Prefix를 입력한 후, 확인 버튼을 클릭하세요. becomes 9. Enter the Prefix and then click the Confirm button. 복구본 생성을 알리는 팝업창이 열립니다. becomes A pop-up window announcing the creation of a backup will open. So the translation is: 9. Enter the Prefix and then click the Confirm button. A pop-up window announcing the creation of a backup will open.

• The name of the backup is created with the input prefix value + original Block Storage name entered.

10. Confirm button will be clicked. The application for creating a backup copy will be completed.

Deleting a snapshot

You can select a snapshot to delete it. To delete a snapshot, follow these steps.

1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click the resource to delete the snapshot. It moves to the Volume Group(BM) details page.
4. Snapshot list을 클릭하세요. Volume Group (BM) snapshot list 페이지로 이동합니다.
5. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to delete.
6. Delete button will be clicked. Snapshot list page will remove the snapshot.

Volume Group(BM) replication usage

The created Volume Group(BM) can be synchronized periodically and consistently after creating replicas in other locations, and work can be done on the Volume Group(BM) details page and the replication page.

Create a copy

You can create a replica of the Volume Group and volume in a different location. To create a copy, follow the following procedure.

1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click the resource to create a replica. It moves to the Volume Group(BM) details page.
4. Replicate Create button should be clicked. Replicate Create popup window will be opened.
5. Replication Location and Replication Volume Group, Replication Block Storage Name Prefix, Replication Cycle should be entered and the Confirm button should be clicked. It creates a replica Volume Group and a replica Block Storage volume with the same disk type.

• Replication location: Select a location different from the original Volume Group (BM).
• Replica Volume Group name: It should start with English and use English, numbers, and special characters (-) to input 3-28 characters.
• Replica Block Storage Name Prefix: It should start with English and use English, numbers, and special characters (-) to input 3-28 characters.
• The replica Block Storage(BM) is created with a volume name of ‘replica Block Storage name prefix + original Block Storage volume name’.
• Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the cycle below.
• Daily: every day 23:59:00
• Every week: every Sunday 23:59:00
• Every month: every month 1st 23:59:00

6. Replication page will be clicked. It moves to the Replication page.
7. Check the replication information.

• When the original or replica Volume Group name is selected, it moves to the Volume Group(BM) details page.

Modify replication policy

You can change the replication status through replication policy modification.

To modify the replication policy, follow the following procedure.

1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click the resource to modify the replication policy. It moves to the Volume Group(BM) details page.
4. Replication page will be clicked. It moves to the Volume Group(BM) Replication page.
5. Replication Policy’s Edit button is clicked. Replication Policy Edit popup window is opened.

• Usage: performs replication. Pause can be modified to Usage.
• Temporary Suspension: temporarily suspends replication. If in use, it can be modified to temporary suspension.
• Delete: It deletes the replication. In case of pause, it can be modified to delete, and after deletion, replication cannot be used again.

6. Volume Group(BM) replication page where you can check the modified replication policy.

Modify Replication Cycle

You can change the synchronization cycle between the original and the replica through replication cycle modification.

To modify the replication cycle, follow the following procedure.

1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
3. Volume Group(BM) list page, click the resource to modify the replication cycle. It moves to the Volume Group(BM) details page.
4. Replication page is clicked. It moves to the Volume Group(BM) replication page.
5. Replication Cycle’s Edit button should be clicked. Replication Cycle Edit popup window will be opened.

• Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the cycle below.
• Daily: every day 23:59:00
• Every week: every Sunday 23:59:00
• Every month: every month 1st 23:59:00

6. Volume Group(BM) replication page where you can check the modified replication cycle.

Volume Group(BM) cancellation

You can cancel the unused Volume Group(BM).
Volume Group(BM) has no separate cancellation procedure, and it is automatically deleted when all volumes are disconnected from the target volume item.

3 - API Reference

4 - CLI Reference

5 - Release Note

Block Storage(BM)