This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

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 NameRequiredVolume 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 TypeRequiredSelect Disk Type
    • SSD: High-performance general volume
    • HDD: General volume
    • Cannot be modified after service creation
    CapacityRequiredCapacity Setting
    • Enter a number between 1~16,384GB
    • Cannot be modified after service creation
    IOPSRequiredEnter IOPS value
    • Enter a number between 3,000~16,000
    • HDD type does not provide performance metric setting function
    ThroughputRequiredEnter Throughput speed (MB/s)
    • Enter a number between 125~1,000
    • HDD type does not provide performance metric setting function
    Connection ServerRequiredSelect 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.
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.
  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.
      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.
  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.
      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.

  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.
      CategoryDetailed description
      Volume StatusStatus 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 ReplicationCreate a replica at another location
      Snapshot CreationCreate a snapshot at a specific point in time
      Service terminationButton 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.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the Block Storage (BM) service, it refers to the volume SRN
Resource NameResource Name
  • In Block Storage(BM) service, it refers to the volume name
Resource IDUnique resource ID of the service
CreatorUser who created the service
Creation timeDate/time the service was created
EditorUser who modified the service
Modification Date/TimeDate/Time when the service was modified
Volume NameVolume Name
  • If you need to edit the volume name, click the Edit button
CategoryOriginal status regarding duplication
Storage Volume NameVolume name within storage device
  • Information distinguishing the volume used for analysis when failures and issues occur
capacityvolume capacity
IOPSIOPS value set when creating service
  • HDD type does not provide this metric
ThroughputThroughput speed (MB/s) set when creating the service
  • HDD type does not provide this metric
Disk typeDisk type
EncryptionEncryption status
  • Encryption provided by default regardless of disk type
Volume GroupName of the Volume Group that the volume belongs to
iSCSI informationStorage Target IP information for server connection
Snapshot CapacityCapacity of snapshot storage space
  • Charges incurred according to the set capacity
  • Click the edit button if you need to set snapshot capacity
Snapshot ScheduleSnapshot automatic creation cycle
  • After setting snapshot capacity, schedule can be registered
  • Click the edit button when snapshot schedule setting is needed
SnapshotName of the snapshot
  • Display when a snapshot exists
  • Click the name to go to the snapshot’s detail page
Connected ServerConnected 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
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.

CategoryDetailed description
Snapshot UsageTotal Capacity of Stored Snapshots
Snapshot nameSnapshot name
CapacitySnapshot Capacity
Creation TimeSnapshot Creation Time
Additional features > MoreSnapshot management button
  • Restore: Restore volume from snapshot
  • Create restore point: Create restore point from snapshot
  • Delete: 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.

CategoryDetailed description
Replication PolicyReplication policy set by the user
Replication CycleReplication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationVolume 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.

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.

CategoryDetailed description
Tag ListTag 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
Table. Block Storage(BM) Tag Tab Items

Work History

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

CategoryDetailed description
Work History ListResource 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
Table. Work History Tab Detailed Information Items

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

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

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

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

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

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

  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.

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.

Note
If you do not configure Multi Path, it may affect the service due to maintenance, failures, etc.

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)
      
      1. 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.

        MultiPath

      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.

        MultiPath

      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.

        MultiPath

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

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

Server Connection Example Configuration
  • Server OS: LINUX
  • Mount location: /data
  • Volume capacity: 24 GB
  • File system: ext3, ext4, xfs, etc.
  • Additional allocated disk: /dev/vdb
  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
      
ItemDescription
cat /etc/fstabLinux system file containing filesystem information. Used when the server starts.
df -hConfirms the total disk usage of the mounted filesystems in the Linux system.
fdisk -lConfirms partition information.
  • Physical disks are displayed with letters such as a, b, c, etc. (e.g., /dev/sda, /dev/sdb, /dev/sdc)
  • Disk partitions are displayed with numbers such as 1, 2, 3, etc. (e.g., /dev/sda1, /dev/sda2, /dev/sda3)
Table. Mount Command Reference
CommandDescription
mDisplays the usage of the fdisk command.
nCreates a new partition.
pDisplays the changed partition information.
tChanges the system ID of the partition.
wSaves the partition information and exits the fdisk settings.
Table. Partition Creation Command (fdisk) Reference

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

    Mount
    • Set the disk to Online
    Mount
    • Initialize the disk
    Mount
    Mount
    • Format the partition
    Mount
    Mount
    Mount
    • Confirm the volume
    Mount

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.

Caution
If you disconnect the connected server from the Console without disconnecting from the server (Umount, Disk Offline), a server status error (Hang) may occur. Be sure to perform the OS task first.

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

    Umount
    • Check the disk status
    Umount

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.
Caution
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
  • If the usage rate within snapshot capacity is high (around 90%), replication may be stopped.
  • If there is a volume in the Volume Group with snapshot capacity not set, you cannot create a snapshot. Set the snapshot capacity for all volumes first.
  • 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.
Reference
  • The snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
  • If you want to automatically create snapshots via a schedule, set the snapshot schedule on the Block Storage(BM) Details page.
  • For detailed information about snapshot schedules, see Edit Snapshot Schedule.
  • The replica can use the snapshot feature after the replication policy is deleted.

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).
  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).
Caution
  • Snapshot recovery must be performed while disconnected (Umount, Disk Offline) on all connected servers, and the recovered volume can be used after reconnecting (Mount, Disk Online).
  • After the snapshot recovery is completed, all snapshots created after the snapshot used for recovery will be deleted.
  • When restoring a snapshot, the volume is restored to that point.
  • If you are using Volume Group (BM), you can perform snapshot recovery from the detail page of Volume Group (BM).

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).
  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.
Caution
  • Only one backup can be created per original.
  • A recovery copy is a separate volume created with the same capacity as the original, and incurs additional costs.
  • If you are using Volume Group (BM), you can create a backup on the detail page of Volume Group (BM).

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.
Reference
  • Snapshots that contain snapmirror in the snapshot name cannot be deleted. snapmirror is included in the snapshot name when a replication is created.
  • If you are using Volume Group (BM), you can delete snapshots from the detail page of Volume Group (BM).

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.

Reference
  • The kr-south region does not provide Block Storage(BM) replication feature.

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.
  1. Replicate Create button will be clicked. Replicate Create popup window will be opened.
  2. 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
  1. Replication page will be clicked. It moves to the Replication page.
  2. 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.
Note
  • When replicating, a replica with the same disk type is created.
  • After setting the snapshot capacity, a replica can be created, and the disk type of the created replica is the same as the original.
  • In cases where the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • After setting the snapshot capacity, the volume added to the Volume Group can be replicated in units of Group on the Volume Group page.
  • One replica can be created per volume, and additional data transfer fees apply when replicating across regions.
  • The replicated created volume cannot be added to the Volume Group.
  • If you are using Volume Group, you can check the replication information from Volume Group (BM).

Modify replication policy

You can change the replication status through replication policy modification.

Caution
During replication, you cannot modify the replication cycle and replication policy.

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.
  1. Block Storage(BM) replication page, check the modified replication policy.
Caution
  • Be aware of the following when deleting a policy.
  • After deleting the policy, the replica is not converted to the original and cannot create a replica.
  • After deleting the policy, you cannot connect to the existing replica, and you can only create a new replica.
  • Data stored only in replicas after temporary suspension will be deleted when replication is used again.
  • When using the replication policy, the replica is in a read-only state and data modification is not possible. Please use replication after unmounting from all connected resources
  • The replication policy can be mounted from the connection server only when it is deleted or in a paused state.

Modify replication cycle

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

Caution
During replication, you cannot modify the replication cycle and replication policy.

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
  1. Block Storage(BM) replication page where you can check the modified replication cycle.

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 nameRequiredVolume Group name
    • Starts with English and uses English, numbers, and special characters (-) to input 3-28 characters
    • Cannot be modified after service creation
    Target VolumeRequiredAdd 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.
Reference
  • When adding the target volume, you can add the volume corresponding to the following to the Volume Group (BM).
  • Snapshot capacity: setting
  • Snapshot automatic creation, creation cycle: not used
  • Replication: Not used
  • The target volume can be added up to a maximum of 16.

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.
    ClassificationDetailed Description
    Volume Group statusVolume 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 creationCreate a replica in a different location
    Creating a snapshotCreate a snapshot at a specific point in time
    Service CancellationButton to cancel the service
    Table. Status Information and Additional Functions
Reference
For a recovery file, the snapshot list, replication tabs are not displayed.

Detailed Information

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

ClassificationDetailed Description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Volume Group(BM), it means Volume Group SRN
Resource NameResource Name
  • In Volume Group(BM), it means Volume Group name
Resource IDService’s unique resource ID
CreatorThe user who created the service
Creation TimeThe time when the service was created
EditorUser who modified the service
Revision TimeThe time when the service was revised
Volume Group nameVolume Group Name
DivisionDivision of original related to replication
Storage Volume Group nameStorage device internal Volume Group name
  • Distinguishing information of the Volume Group used for analysis when failures and issues occur
Snapshot ScheduleSnapshot automatic generation cycle
  • Snapshot capacity setting and schedule registration are possible
  • If snapshot schedule setting is required, click the modify button
BackupVolume Group’s backup name
  • Displayed when a backup exists
  • Clicking the name moves to the detailed page of the backup
Target VolumeVolume Group added Block Storage(BM)
  • Volume Name: Volume name
  • Disk Type: Disk type of the volume
  • Capacity: Capacity of the volume
  • Snapshot Capacity: Capacity of the snapshot storage space set for the volume
Table. Detailed information items of Volume Group(BM)

Snapshot list

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

ClassificationDetailed Description
Snapshot NameSnapshot Name
Creation TimeSnapshot Creation Time
Additional Features > MoreSnapshot Management Button
  • Restore: Volume Restore with Snapshot
  • Create Copy: Create Copy from Snapshot
Table. Snapshot list tab detailed information items
Caution
  • When creating a snapshot in the Volume Group, a snapshot is created in the Block Storage (BM).
  • Volume Group snapshot is used when managing the target volume’s snapshot capacity and count.
  • If the maximum number of snapshot creations or the threshold of snapshot space (around 90%) is exceeded, old snapshots will be deleted from oldest.
  • 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 maximum number of automatic creations through scheduling is 128), and if the maximum number of creations is exceeded, no more snapshots can be created.
  • Snapshot recovery must be performed in a state where all connected servers are disconnected (Umount, Disk Offline), and the recovered volume can be used after reconnection (Mount, Disk Online).
Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00) standard.
  • When using replication, the snapmirror file cannot be deleted.
  • When using Volume Group, set the snapshot schedule on the Volume Group (BM) detailed information screen. The created snapshot can be checked in the Block Storage (BM) snapshot list.

Replication

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

ClassificationDetailed Description
Replication PolicyReplication policy set by the user
Replication CycleThe replication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationVolume information of the original and replica
  • Classification: Classification of whether it is a replica-related original
  • Volume Group Name: Volume Group name of the original or replica
  • Location: Location where the volume was created
  • Authority: User authority of the volume set according to the 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 replicating, a replica with the same disk type is created.
  • Snapshot capacity setting and replica creation are possible after setting.
  • If you are using a Volume Group, check the replication information on the Volume Group(BM) resource list page.
  • The replica Block Storage can modify the connected server when the replication policy is paused or deleted.
  • The replica Block Storage can use the snapshot feature after the replication policy is deleted.
  • If the replication policy is paused or the replication status is completed, you can modify the policy and cycle from the replica.

Tag

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

ClassificationDetailed Description
Tag ListTag List
  • Check Key, Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the existing list of created Key and Value
Fig. Volume Group(BM) Tag Tab Items

Work History

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

ClassificationDetailed Description
Job history listResource change history
  • Check job time, resource type, resource ID, resource name, job details, event topic, job result, and worker information
  • Click the detailed search button to search in detail
Table. Work History Tab Detailed Information Items

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

Volume Group snapshot is used when managing the target volume’s snapshot capacity and count

  • Snapshots can be created up to a maximum of 1,023 (the maximum number of automatic creations through scheduling is 128), and if the maximum number of creations is exceeded, no more snapshots can be created.
Reference
The snapshot schedule is based on Asia/Seoul (GMT +09:00) standard.

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.
  1. Select the volume you want to add and then click the Confirm button.
Caution
  • Volume Group’s replication policy is in use, the target volume cannot be modified.
Reference
  • When adding the target volume, you can add the following volume to the Volume Group (BM).
  • Snapshot capacity: settings
  • Snapshot automatic creation, creation cycle: not used
  • Copy: Not used
  • The target volume can be added up to a maximum of 16.

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.
Caution
  • When creating a snapshot in the Volume Group, a snapshot is also created on the connected target volume.
  • Volume Group snapshot usage, manage the snapshot capacity and number of the target volume.
  • If the maximum number of snapshot creations or the threshold of snapshot space (around 90%) is exceeded, old snapshots will be deleted from oldest.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • A snapshot can be created up to 1,023 (the automatic creation number through the schedule is up to 128), and if the maximum creation number is exceeded, no more snapshots can be created.
Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00) standard.
  • Snapshot storage space will be applied according to the settings on the Block Storage(BM) details page of the target volume.
  • If you want to automatically create snapshots through a schedule, set the snapshot schedule on the Volume Group(BM) details page.
  • For more information about the snapshot schedule, please refer to Modifying the Snapshot Schedule.
  • The replica can use the snapshot feature after the replication policy is deleted.

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.
  1. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
  2. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to restore.
  3. Restore button, click. Snapshot restore popup window opens.
  4. Snapshot name and Creation time are confirmed after clicking the Confirm button. The target volumes are restored as snapshots.
  5. Detailed Information button will be clicked. It will move to the Volume Group(BM) Detail page.
  6. Target Volume์— ์ถ”๊ฐ€๋œ ๋ณผ๋ฅจ์˜ Volume Name์„ ํด๋ฆญํ•˜์„ธ์š”. Block Storage(BM) Detail ํŽ˜์ด์ง€๋กœ ์ด๋™ํ•ฉ๋‹ˆ๋‹ค.
  7. connected server items have been added, after server connection, perform connection work (Mount, Disk Online)
Caution
  • Snapshot recovery must be performed with all target volumes disconnected (Umount, Disk Offline) from the connected server, and the recovered volume can be used after reconnection (Mount, Disk Online).
  • After the snapshot restoration is complete, all snapshots created after the snapshot used for restoration will be deleted.

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.
  1. Confirm button will be clicked. The application for creating a backup copy will be completed.
Caution
  • A backup copy can be created only one per original.
  • The recovery volume is a separate volume created with the same capacity as the original, and additional costs are incurred.

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.
Reference
When using replication, the snapmirror file cannot be deleted.

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
  1. Replication page will be clicked. It moves to the Replication page.
  2. Check the replication information.
  • When the original or replica Volume Group name is selected, it moves to the Volume Group(BM) details page.
Note
  • When creating a replica in the Volume Group, a replica Volume Group and Block Storage (BM) are created.
  • The replica Block Storage has the same type as the original and disk type.
  • You can create one replica per Volume Group, and additional data transfer fees apply when replicating across regions.

Modify replication policy

You can change the replication status through replication policy modification.

Caution
During replication, you cannot modify the replication cycle and replication policy.

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.
  1. Volume Group(BM) replication page where you can check the modified replication policy.
Caution
  • Note the following when deleting a policy.
  • After deleting the policy, the replica cannot be converted to the original and replication cannot be created.
  • After deleting the policy, you cannot connect to the existing replica, and you can only create a new replica.
  • Data stored only in replicas after temporary suspension will be deleted when replication is used again.
  • When using the replication policy, the replica is in a read-only state and data modification is not possible. Please use replication after unmounting all connected resources

Modify Replication Cycle

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

Caution
During replication, you cannot modify the replication cycle and replication policy.

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

Caution
After cancellation, it cannot be recovered, so please be careful.