Storage

• 1: Block Storage(BM)
• 1.1: Overview
• 1.1.1: Monitoring Metrics
• 1.2: How-to Guides
• 1.2.1: Connect to Server
• 1.2.2: Use Snapshot
• 1.2.3: Use Replication
• 1.2.4: Use Volume Group
• 1.3: API Reference
• 1.4: CLI Reference
• 1.5: Release Note
• 2: File Storage
• 2.1: Overview
• 2.1.1: Monitoring Metrics
• 2.1.2: ServiceWatch Metrics
• 2.2: How-to guides
• 2.2.1: Connect to Server
• 2.2.2: Use Snapshot
• 2.2.3: File-level Recovery
• 2.2.4: Use Disk Backup
• 2.2.5: Use Replication
• 2.3: API Reference
• 2.4: CLI Reference
• 2.5: Release Note
• 3: Object Storage
• 3.1: Overview
• 3.1.1: Amazon S3 Usage Guide
• 3.1.2: Monitoring Metrics
• 3.1.3: ServiceWatch Metrics
• 3.2: How-to guides
• 3.2.1: Access Control
• 3.2.2: File and Folder Management
• 3.2.3: Version Management
• 3.2.4: Permission Management
• 3.2.5: Replication Policy Management
• 3.3: Release Note
• 4: Archive Storage
• 4.1: Overview
• 4.1.1: ServiceWatch Metrics
• 4.2: How-to guides
• 4.2.1: Manage Archiving Policy
• 4.2.2: Use Version Management
• 4.2.3: Archive Recovery
• 4.3: API Reference
• 4.4: CLI Reference
• 4.5: Release Note
• 5: Backup
• 5.1: Overview
• 5.2: How-to guides
• 5.2.1: Instant Backup
• 5.2.2: Recovery
• 5.2.3: Use Backup Agent
• 5.2.4: Install Backup Agent
• 5.2.5: Use Replication
• 5.3: API Reference
• 5.4: CLI Reference
• 5.5: Release Note
• 6: Parallel File Storage
• 6.1: Overview
• 6.2: How-to guides
• 6.2.1: Use Snapshot
• 6.2.2: Install Agent
• 6.2.3: File-level Recovery
• 6.3: API Reference
• 6.4: CLI Reference
• 6.5: Release Note

1 - Block Storage(BM)

1.1 - Overview

Service Overview

Block Storage is a high-performance storage that stores data in block units arranged in a fixed size and order.
Suitable for large-scale, high-performance requirements such as databases and mail servers, and users can directly allocate volumes on the server for use.

Features

• Large volume provision: You can create volumes up to 16 TB in size.
• Full SSD-based high performance: Provides high durability and availability based on redundant controllers and Disk Array RAID. Since a Full SSD disk is provided by default, it is suitable for high-speed data processing tasks such as database workloads.
• Snapshot Backup: Data that has been modified or deleted can be recovered using the image snapshot feature. The user selects a snapshot created at the desired point in time from the list and performs the recovery.
• Replication: Creates an identical replica volume at a different location, and users can set the data replication schedule. If the original volume becomes unavailable due to failures or disasters, services can be provided through the replica volume.

Configuration diagram

Provided features

Block Storage provides the following features.

• Volume Name: Users can set or edit the name for each volume.
• Capacity: Volumes can be created with capacities ranging from a minimum of 1 GB up to a maximum of 16 TB.
• Connection Server : You can select Bare Metal Server or Multi Node GPU Cluster to connect or disconnect.
  • Multi-Server Connection (Multi Attach): Supports up to 5 server connections, with no limit on the number of volumes that can be attached to a Bare Metal Server.
• Encryption: All volumes are encrypted with the AES-256 algorithm by default, regardless of disk type.
• Snapshot: Using the image snapshot feature, you can create a snapshot at a specific point in time or generate snapshots at regular intervals.
  • Capacity: the capacity of the snapshot storage space
  • Schedule: Snapshot auto-creation interval
  • Recovery: Recover the original volume to the latest snapshot, or select a snapshot at a specific point in time to create a recovery volume
  • Recovery copy a separate volume created with the same capacity as the original (additional cost incurred)
• Replication: It replicates the volume to another location, and the user can set the replication schedule.
  • A replicated volume can also serve as the primary using the snapshot feature in the event of a disaster.
• Volume Group: Set up to 16 Block Storage volumes as a group. Snapshots and replication can be configured at the group level.
• Monitoring: You can view monitoring information such as IOPS, latency, and throughput through the Cloud Monitoring service.

Component

You can create a volume by entering the size and selecting the disk type according to the user’s service scale and performance requirements.
When using the snapshot feature, you can restore data to the desired point in time.

Volume

A volume (Volume) is the basic creation unit of the Block Storage service and is used as data storage space. Users create a volume by setting the name, capacity, disk type, snapshot, etc., and then connect it to a Bare Metal Server for use.
The volume name generation rules are as follows.

• It must start with an English letter and can be set using English letters, numbers, and special characters (-) within 3 to 28 characters.

Snapshot

Snapshot is an image backup of a volume at a specific point in time. Users can view the snapshot name and creation time in the snapshot list to select the snapshot they want to restore, and can recover data that was modified or deleted using that snapshot.
The following are considerations when using snapshots.

Volume Group

A Volume Group is a group-level management feature that allows users who configure databases and applications across two or more volumes to create consistent-point snapshots and replications. Users can create a Volume Group by selecting a name and a target Block Storage.

Preceding Service

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

1.1.1 - Monitoring Metrics

Block Storage BM Monitoring Metrics

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

1.2 - How-to Guides

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

Block Storage(BM) Create

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

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

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

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

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

   Category	Required status	Detailed description
   Volume name	Required	Volume name must start with an English letter and be 3~28 characters using English letters, numbers, and special characters (-) cannot be modified after service creation
   Disk 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,384 GB Cannot be modified after service creation
   Max IOPS	Required	Enter IOPS value Enter a number between 5,000~20,000 HDD type does not provide performance metric setting function
   Max Throughput	Required	Enter the throughput speed (MB/s) Enter a number between 250~1,000 HDD type does not provide performance metric configuration functionality
   Connection server	Required	Connect Bare Metal Server selection Provides up to 8 Bare Metal Server connections No limit on the number of volumes that can be attached to a Bare Metal Server

   Table. Block Storage (BM) Service Information Input Items

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

   • Once creation is complete, check the created resources on the Block Storage(BM) List page.

Configure iSCSI

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

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

Linux operating system

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to be used on the connected server. You will be taken to the Block Storage(BM) Details page.
4. Connection Server item, verify the server and then connect.
5. Proceed with iSCSI configuration by referring to the steps below.
   • Discover the connection information for the Storage (target IP).
     • Tab 0

     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 the storage (target IP). If it is already connected, proceed to the next step.
     • Tab 0

     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).
     • Tab 0

     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 verify the additional disk.
     • Tab 0

     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]

   • Configure Auto Login to log in automatically even after a reboot.
     • Tab 0

     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

   • Verify the configuration using the following command.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     [root@localhost ~]# lsblk

     [root@localhost ~]# lsblk

Windows operating system

1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to be used on the connected server. You will be taken to the Block Storage(BM) Details page.
4. After checking the server in the Connection Server item, connect.
5. Proceed with iSCSI configuration by referring to the steps below.
   • Open Command Prompt (Admin) and run powershell.
     • Tab 0

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

     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

   • Install Multipath I/O. If the Restart Needed item is displayed as Yes, a restart is required.
     • Tab 0

     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}

   • Modify the Initiator Port Address.
     If you are not an Active Directory member, skip this procedure. The Initiator Port Address only needs to be modified when you are an Active Directory member.
     
     • iqn is generated based on the hostname, but when joined to Active Directory, it is changed to DNS format.
       Since it is registered in Storage based on the default hostname, for iqn.1991-05.com.microsoft:iqn01.scp.com, iqn01 is the hostname. Remove the DNS information and change it to the name registered when creating the OS in the user Console, such as iqn.1991-05.com.microsoft:iqn01.
       
     • If you are not an AD member, no changes are required.
       • Tab 0

       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

   • Set the Storage (target Portal) address as a variable.
     • Tab 0

     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 Storage (target Portal).
     • Tab 0

     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).
     • Tab 0

     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 the storage (target) information.
     • Tab 0

     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 prompt appears if a reboot is required. Press Y or the Enter key to reboot.
     • Tab 0

     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

   • Check the list and path of Multipath I/O disks.
     You can check MPIO disk information using the mpclaim.exe command. Enter the generated MPIO disk number to view the disk path and status.
     • Tab 0

     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

   • Check in Disk Management.

View detailed information of Block Storage (BM)

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

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

1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to view detailed information. You will be taken to the Block Storage(BM) Details page.
   • Block Storage(BM) Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Tags, Operation History tabs.

     Category	Detailed description
     Volume status	Volume status Creating: In progress Available: Creation completed, server connection possible Attaching: Connecting to server Detaching: Disconnecting from server In Use: Server connection established Deleting: Service termination in progress Editing: Changing settings Error Deleting: Abnormal state while deleting Error: Abnormal state while creating
     Clone creation	Create a replica in a different location For more information on creating a replica, see Creating a Replica
     Create snapshot	Create a snapshot at a specific point in time For detailed information on creating snapshots, refer to Creating a Snapshot
     Service termination	Cancel service button

     Table. Status information and additional features

Detailed information

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

Snapshot list

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

Clone

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

tag

On the Block Storage(BM) List page, you can view the tag information of the selected resource and 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) Managing Resources

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

Edit volume name

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

1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource whose volume name you want to edit. You will be taken to the Block Storage(BM) Details page.
4. Click the Edit button for Volume name. The Edit Volume Name popup opens.
5. Enter the volume name and click the Confirm button.

Increase capacity

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

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

Modify Snapshot Size

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

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. Block Storage(BM) List page: click the resource to modify the snapshot capacity. You will be taken to the Block Storage(BM) Details page.
4. Click the Edit button of the Snapshot Capacity item. The Snapshot Capacity Edit popup window opens.
5. Set the Use status and generation capacity (%), then click the Confirm button.
   • Generation Capacity(%) can be selected in increments of 50 between 100 and ~500.

Edit Snapshot Schedule

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

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to edit the snapshot schedule. You will be taken to the Block Storage(BM) Details page.
4. Click the Edit button for the Snapshot Schedule item. The Snapshot Schedule Edit popup opens.
5. Set the snapshot auto creation status and creation interval, then click the Confirm button.
   • If you want to automatically create snapshots based on the creation cycle, select automatic creation as enabled.
   • Select the generation cycle as daily, hourly, or as weekly, day of week, hourly.

Edit Max IOPS

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

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. Block Storage(BM) List page, click the resource whose IOPS value you want to modify. You will be taken to the Block Storage(BM) Details page.
4. Click the Edit button of Max IOPS. The Max IOPS Edit popup opens.
5. After entering the Max IOPS value to change, click the Confirm button.
   • The Max IOPS value can be set to a value between 5,000 and 20,000.

Edit Max Throughput

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

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

Edit Connection Server

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

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to edit the connected server. You will be taken to the Block Storage(BM) Details page.
4. When adding a connection server, click the Add button in the Connection Server item. The Add Connection Server popup opens.
5. After selecting the server you want to connect to, click the Confirm button.
6. If you need to disconnect the server, click the Disconnect button in the Connection Server field.
   • Be sure to log into the server, perform the disconnect operations (Umount, Disk Offline), and then disconnect.

Cancel Block Storage(BM)

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

To cancel Block Storage, follow the steps below.

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

1.2.1 - Connect to Server

When using a volume on the server, a connect or disconnect operation is required.
On the Block Storage(BM) Details page, after adding a connected server, log in to the server to configure Multi Path and perform connection tasks (Mount, Disk Online). After use, perform disconnection tasks (Umount, Disk Offline) and remove the connected server.

Configure Multi Path

Before using the volume on the connected server, Multi Path configuration is required. Follow the steps below.

Linux operating system

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

2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.

3. On the Block Storage(BM) List page, click the resource to configure Multi Path. You will be taken to the Block Storage(BM) Details page.

4. In the Connection Server item, verify the server and then connect. Configure Multi Path according to the guide below.

   • Device Check

     1. The created volume can be verified with the fdisk -l command.

   • Verify DM-Multipath configuration

     1. In the volume detection process, the Linux system automatically applies Multi Path, which can be verified with the multipath –ll command.
     2. Volumes with Multi Path applied use Multipath device names such as /dev/mapper/##### instead of the /dev/sd# format, and can be verified with the fdisk –l command.

   • iSCSI replacement timeout value setting

     1. When connecting iSCSI, set the replacement timeout.

     # vi /etc/iscsi/iscsid.conf
     node.session.timeo.replacement_timeout = 5
     (default 120 값을 5 로 변경) 
     

     2. After modifying the above, restart the iscsi service.

     # systemctl restart iscsid
     

Windows operating system

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

2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.

3. On the Block Storage(BM) List page, click the resource to set Multi Path. You will be taken to the Block Storage(BM) Details page.

4. In the Connection Server item, verify the server and then connect. Configure Multi Path according to the guide below.

   • Device Check

     1. Click the Start > Server Manager menu to launch Server Manager.
     2. When you click the Server Manager > File and Storage Services > Volumes > Disks menu, you can view the iscsi device.
     3. Since Multi-Path is not yet configured, a single device appears as multiple devices for each path.

   • Install MPIO (Reboot required)

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

     2. Add Roles and Features Wizard When the popup window opens, click the Next button.

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

     4. Select destination server(Server selection) On the page, the current server is automatically detected. Verify the information and click the Next button.

     5. Select features(Feature selection) page, select Features from the left menu, check Multipath I/O, then click the Next button.

        

     6. Confirm installation selections(Confirm installation selections) on the page, after checking Restart the destination server automatically if required, when the popup appears, click Yes and click the Install button.

     7. The installation starts and automatically reboots.

     8. When reconnecting to the server, the installation is already complete. Click the close button to close the wizard popup window.

     9. Click Server Manager > DashBoard > tools > MPIO.

        

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

         • If the message appears, reboot the server.

     11. After the reboot, you can check NETAPP Devices in MPIO devices.

         

     12. In the Windows Run dialog (Command Prompt), run diskmgmt.msc to open the Disk management popup window.

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

Connect to Server (Mount, Disk Online)

To use the volume added to the connected server, you must log into the server and perform the connection tasks (Mount, Disk Online). Follow the steps below.

Linux operating system

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to which you want to connect the server. You will be taken to the Block Storage(BM) Details page.
4. Connected Server item, check the server and then connect. Mount the volume according to the guide below.
   • Switch to root privileges
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     $ sudo -i

     $ sudo -i

   • Check Disk
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # 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

     # 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 partition
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

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

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

   • Partition format setting (example: ext4)
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # 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

     # 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

   • Volume Mount
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # 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

     # 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

     Item	Explanation
     cat /etc/fstab	This is the filesystem information file for the Linux system. It is used when the server starts.
     df -h	Check the total disk usage mounted on a Linux system.
     fdisk -l	Check partition information. Physical disks are displayed as /dev/sda, /dev/sdb, /dev/sdc with letters such as a, b, c Disk partitions are displayed as /dev/sda1, /dev/sda2, /dev/sda3 with numbers such as 1, 2, 3

     Table. Refer to the Mount command

     command	Explanation
     m	Check the usage of the fdisk command.
     n	Create a new partition.
     p	Verify the updated partition information.
     t	Change the system ID of the partition.
     w	Save the partition information and exit the fdisk configuration.

     Table. Refer to the partition creation command (fdisk).

Windows operating system

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

2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.

3. On the Block Storage(BM) List page, click the resource to connect the server. You will be taken to the Block Storage(BM) Details page.

4. From the Connected Server item, verify the server and then connect. Follow the guide below to attach the volume (Disk Online).

   • Right-click the Windows Start icon and run Computer Management.
   • In the Computer Management tree structure, select Storage > Disk Management.
   • Check Disk

   

   • Disk Online

   

   • Disk initialization

   

   

   • Partition format

   

   

   

   • Check volume

   

Disconnect Server (Umount, Disk Offline)

Connect to the server and perform the disconnect operations (Umount, Disk Offline), then you must disconnect the server from the Console. Follow the steps below.

Linux operating system

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to detach the server connection. You will be taken to the Block Storage(BM) Details page.
4. After checking the server in the Connected Server item, connect. Follow the guide below to unmount the volume (Umount).
   • Volume Umount
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # 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

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

2. On the Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) List page.

3. On the Block Storage(BM) List page, click the resource to detach the server connection. You will be taken to the Block Storage(BM) Details page.

4. In the Connected Server item, verify the server before connecting. Follow the guide below to detach the volume (Disk Offline).

   • Windows Start icon right-click, then run Computer Management
   • In the Computer Management tree structure, select Storage > Disk Management
   • Right-click the disk to be removed, then run Offline.

   

   • Check disk status

   

1.2.2 - Use Snapshot

You can create, delete, or recover a snapshot of a created Block Storage (BM). You can perform these actions on the Block Storage (BM) Details page and the Snapshot List page.

Create Snapshot

Users can create a snapshot at the desired point in time.

1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. Click the resource to create a snapshot on the Block Storage(BM) List page. Navigate to the Block Storage(BM) Details page.
4. Check the setting status of the Snapshot Capacity item.
   • Snapshots can be created only when storage space has been secured by configuring snapshot capacity.
   • For detailed information, refer to Modify Snapshot Capacity.
5. Click the Create Snapshot button. The Create Snapshot popup opens.
6. Click the Create button. It creates a snapshot of the current point in time.
7. Click the Snapshot List page. You will be taken 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 restore a snapshot, 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. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. Block Storage(BM) List Click the resource to restore from a snapshot. Block Storage(BM) Details page will be opened.
4. If a server has been added in the Connected Server item, connect to the server and then perform the disconnect tasks (Umount, Disk Offline).
   • For more details, refer to Disconnect Server.
5. Click the Snapshot List page. Navigate to the Block Storage(BM) Snapshot List page.
6. After checking the Snapshot name and Creation timestamp, click the More button of the snapshot you want to restore.
7. Recover button, click it. The snapshot recovery popup opens.
8. After verifying the snapshot name and creation time, click the Confirm button. Recover the Block Storage volume from the snapshot.
9. Click the Details button. Navigate to the Block Storage(BM) Details page.
10. Connection Server If a server has been added to this item, connect to the server and perform the connection tasks (Mount, Disk Online).
    • For detailed information, refer to Connect to Server.

Create a recovery copy

You can create a recovery copy from a snapshot of a Block Storage (BM) volume. To create a snapshot recovery copy, 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. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to restore from a snapshot. You will be taken to the Block Storage(BM) Details page.
4. If a server has been added in the Connected Server item, connect to the server and then perform the disconnect tasks (Umount, Disk Offline).
   • For more details, refer to Disconnect Server.
5. Click the Snapshot List page. Go to the Block Storage(BM) Snapshot List page.
6. After confirming the Snapshot name and Creation timestamp, 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 Create button. A popup notifying the creation of the recovery image will appear.
9. Click the Confirm button. The recovery copy creation request is complete.

Delete Snapshot

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

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to delete the snapshot. You will be taken to the Block Storage(BM) Details page.
4. Click Snapshot List. It navigates to the Block Storage(BM) Snapshot List page.
5. After confirming the Snapshot name and creation 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.
   • After selecting the snapshots to delete from the snapshot list, you can click the Delete button at the top of the list to delete them all at once.
     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).

1.2.3 - Use Replication

After creating a replica of the generated Block Storage(BM) in another location, you can synchronize it periodically. You can perform the tasks on the Block Storage(BM) Details page and the Replication page.

Create Clone

You can create a replica volume in a different location.

1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource for which you want to create a replica. You will be taken to the Block Storage(BM) Details page.
4. Check the setting status of the Snapshot Capacity item.
   • Replication can be created only when storage space is available through snapshot capacity configuration.
   • For detailed information, refer to Modify Snapshot Capacity.
5. Click the Create Clone button. The Create Clone popup opens.
6. Enter the Replication location, Replication volume name, and Replication schedule, then click the Create button. It creates a replica with the same disk type.
   • Replication Location: Select a location different from the original Block Storage(BM) volume.
   • Replication Volume Name: Start with an English letter and use English letters, numbers, and special characters (-) to enter 3 to 28 characters.
   • Replication interval: Select from 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed using the interval below.
     • Daily: every day 23:59:00
     • Weekly: Every Sunday 23:59:00
     • Monthly: 1st day of each month 23:59:00
7. Click the Clone page.
   You will be taken to the Clone page.
8. Check the replication information.
   • When selecting the volume name of the source or replica, you are taken to the volume’s Block Storage(BM) Details page.

Edit replication policy

You can change the replication status by modifying the replication policy.

To modify the replication policy, follow these steps.

1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to edit the replication policy. You will be taken to the Block Storage(BM) Details page.
4. Click the Replication page. Go to the Block Storage(BM) Replication page.
5. Click the Edit button of the Replication Policy. The Edit Replication Policy popup opens.
   • Use: performs replication. If it is Paused, you can change it to Use.
   • Pause: Temporarily stops replication. If use, you can modify to Pause.
   • Delete: Delete the replica. If Paused, it can be changed to Delete, and after deletion, replication cannot be used again.
6. Check the updated Replication Policy on the Block Storage(BM) Replication page.

Edit replication cycle

You can change the synchronization interval between the original and the replica by modifying the replication interval.

To modify the replication interval, follow these steps.

1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
3. Click the resource to modify the replication interval on the Block Storage(BM) List page. You will be taken to the Block Storage(BM) Details page.
4. Click the Replication page. Go to the Block Storage(BM) Replication page.
5. Click the Edit button of Replication Cycle. Replication Cycle Edit popup opens.
   • Replication interval: Select from 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed using the interval below.
     • Daily: 23:59:00
     • Weekly: Every Sunday 23:59:00
     • Monthly: 1st day of each month 23:59:00
6. Check the modified Replication Interval on the Block Storage(BM) Replication page.

1.2.4 - Use Volume Group

The Volume Group(BM) service allows you to configure up to 16 Block Storage(BM) volumes as a group, enabling the creation of consistent point-in-time snapshots and replications.
Users can create the service by entering the required information for the Volume Group (BM) and selecting detailed options through the Samsung Cloud Platform Console.

Create Volume Group (BM)

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

To create a Block Storage, follow these steps.

1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
2. Click the Volume Group(BM) menu. Navigate to the Volume Group(BM) List page.
3. On the Volume Group(BM) page, click the Volume Group(BM) Create button. You will be taken to the Volume Group(BM) Create page.

   Category	Required	Detailed description
   Volume Group name	Required	Volume Group name must start with an English letter and be 3 to 28 characters using English letters, numbers, and special characters (-) cannot be modified after service creation
   target volume	Required	Add target volume to Volume Group After clicking the Add button, select the target volume in the add target popup Target volume criteria Snapshot size: Set Snapshot auto-creation, creation interval: Not used Replication: Not used Up to 16 can be added

   Table. Volume Group (BM) Service Information Input Items
4. Click the Create button.
   • When creation is complete, check the created resources on the Volume Group(BM) List page.

Check detailed information of Volume Group (BM)

Volume Group(BM) service allows you to view and edit the full resource list and detailed information. Volume Group(BM) Details page consists of Details, Snapshot List, Replication, Operation History tabs.