Storage

• 1: Block Storage(BM)
• 1.1: Overview
• 1.1.1: Monitoring Metrics
• 1.1.2: ServiceWatch metric
• 1.2: How-to Guides
• 1.2.1: Connect to server
• 1.2.2: Use Snapshot
• 1.2.3: Using duplication
• 1.2.4: Using 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: Using Disk Backup
• 2.2.5: Using replication
• 2.3: API Reference
• 2.4: CLI Reference
• 2.5: Release Note
• 3: Parallel File Storage
• 3.1: Overview
• 3.2: How-to guides
• 3.2.1: Use Snapshot
• 3.2.2: Install Agent
• 3.2.3: File-level Recovery
• 3.3: API Reference
• 3.4: CLI Reference
• 3.5: Release Note
• 4: Object Storage
• 4.1: Overview
• 4.1.1: Amazon S3 Usage Guide
• 4.1.2: Monitoring Metrics
• 4.1.3: ServiceWatch metric
• 4.2: How-to guides
• 4.2.1: Access control
• 4.2.2: File and Folder Management
• 4.2.3: Version Management
• 4.2.4: Permission Management
• 4.2.5: Replication Policy Management
• 4.2.6: Copy original file
• 4.3: Release Note
• 5: Archive Storage
• 5.1: Overview
• 5.1.1: ServiceWatch Metrics
• 5.2: How-to guides
• 5.2.1: Managing Archiving Policies
• 5.2.2: Use Version Management
• 5.2.3: Archive Recovery
• 5.3: API Reference
• 5.4: CLI Reference
• 5.5: Release Note
• 6: Backup
• 6.1: Overview
• 6.2: How-to guides
• 6.2.1: Instant Backup
• 6.2.2: Restore
• 6.2.3: Using Backup Agent
• 6.2.4: Install Backup Agent
• 6.2.5: Use Replication
• 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 by a fixed size and layout.
Suitable for large-scale, high-performance requirements such as databases and mail servers, and users can directly allocate volumes to the server.

Features

• Large volume provision: You can create volumes up to 16TB in size.
• Full SSD-based high performance: Provides high durability and availability based on redundant Controllers and Disk Array RAID. * Full SSD disks are provided by default, making them suitable for high-speed data processing tasks such as database workloads.
• Snapshot Backup: Image snapshot functionality enables recovery of changed and deleted data. * The user selects the snapshot created at the desired recovery point from the list and performs the recovery.
• Replication: creates an identical replica volume at another location, and the user can set the data replication schedule. * If the original volume cannot be used due to failures or disasters, service can be provided through a 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: You can create a volume with a capacity 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): Up to 5 servers can be connected, and there is 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: Use the image snapshot feature to 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 original via the snapshot feature in the event of a disaster.
• Volume Group: Configure 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 ServiceWatch service.

Component

You can create a volume by entering the capacity 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. The user sets the name, size, disk type, snapshots, etc., creates a volume, and then attaches it to a Bare Metal Server for use.
The volume name creation rules are as follows.

• Must start with a letter and can be set to 3~28 characters using letters, numbers, and special characters (-).

snapshot

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

Volume Group

Volume Group is a group-level management feature that provides users who configure databases and applications across two or more volumes the ability to create snapshots and replications at a consistent point in time. The user can create a Volume Group by selecting a name and the target Block Storage.

Preceding Service

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

1.1.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.1.2 - ServiceWatch metric

Block Storage BM sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at 1‑minute intervals.

Basic Metrics

The following are the basic metrics for the Block Storage BM namespace.

The indicators whose names are displayed in bold below are the key indicators selected from the basic indicators provided by Block Storage BM. The key metrics are used to build the service dashboards that are automatically created for each service in ServiceWatch.

Each metric offers user guidance on which statistical values are meaningful when viewing it, and the service dashboard allows you to view key metrics using their primary statistical values.

1.2 - How-to Guides

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

Create Block Storage(BM)

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

2. On the Service Home page, click the Create Block Storage (BM) button. 2. Navigate to the Block Storage(BM) Creation page.

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

   Category	Required	Detailed description
   Volume name	Required	Volume name must start with an English letter and be entered using English letters, numbers, and special characters (-) for 3~28 characters cannot be modified after service creation
   Disk type	Required	Select disk type SSD: High-performance general volume HDD: General volume Cannot be modified after service creation
   capacity	Required	Capacity setting Enter a number between 1~16,384GB Cannot be modified after service creation
   Max IOPS	Required	Enter the IOPS value Enter a number between 5,000~20,000 HDD type does not provide performance metric configuration functionality
   Max Throughput	Essential	Enter the throughput speed (MB/s) Enter a number between 250~1,000 HDD type does not provide performance metric setting functionality
   Availability Zone	Required	Select the Availability Zone to create resources within the region If you change the Availability Zone while a connection server has been added, the selected connection server will be reset
   Connection server	Required	Select Bare Metal Server connection Provide 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.

5. When the popup indicating creation opens, click the Confirm 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 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. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List Navigate to the page.
3. On the Block Storage(BM) List page, click the resource to be used on the connected server. 3. Block Storage(BM) Details Navigate to the page.
4. After verifying the server in the Connection Server item, connect.
5. Refer to the procedure below to set up iSCSI.
   • Discover the connection information for 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.

   • Delete all unused Storage (target IP) to minimize search time.
     • 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

   • Rescan to check the added 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]

   • Set Auto Login so that you are logged 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. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List Go to the page.
3. On the Block Storage(BM) List page, click the resource to be used on the connected server. 3. Block Storage(BM) Details Go to the page.
4. Connection Server item, check the server and then connect.
5. Proceed with iSCSI configuration by referring to the following procedure.
   • 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 set to 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 needs to be modified only when it is an Active Directory member.
     
     • The iqn is generated based on the hostname, but when joined to Active Directory, it changes 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 from 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 the 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. *
     Inquiries occur when a reboot is required during MPIO disk creation. 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 view 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.

Block Storage(BM) Check detailed information

Block Storage(BM) service allows you to view and edit the full resource list and detailed information. Block Storage(BM) Details page consists of the Detailed Information, 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. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Go to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to view detailed information. 3. Block Storage(BM) Details Navigate to the page.
   • The 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	볼륨의 상태 Creating: In progress Available: Creation complete, server connection available 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 during deletion Error: Abnormal state during creation
     Clone creation	Create a replica in a different location For detailed information on creating a replica, see 복제 생성하기
     Create snapshot	Create a snapshot at a specific point in time For detailed information on snapshot creation, see 스냅샷 생성하기
     Service cancellation	Button to cancel the service

     Table. Status information and additional features

Detailed Information

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

Snapshot List

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

Replication

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

Tag

Block Storage (BM) List page lets you view, add, modify, or delete the tag information of the selected resource.

Operation 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 a connected server, you can perform the operation on the Block Storage(BM) Details page.

Edit volume name

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

1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List Navigate to the page.
3. Block Storage (BM) List Click the resource to edit the volume name on the page. 3. Block Storage(BM) Details Navigate to the page.
4. Volume Name’s Edit button, click it. 4. Edit Volume Name the popup window opens.
5. Enter the volume name and click the Confirm button.

Expand Capacity

You can expand the volume capacity. To increase capacity, follow the steps below.

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

Modify snapshot size

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

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

Edit Snapshot Schedule

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

1. Click the All Services > Storage > Block Storage(BM) menu. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Block Storage(BM) List Navigate to the page.
3. Block Storage (BM) List page, click the resource to edit the snapshot schedule. 3. Block Storage(BM) Details Navigate to the page.
4. Click the Edit button of the Snapshot Schedule item. 4. Edit Snapshot Schedule The popup window opens.
5. Set the snapshot auto‑creation status and creation interval, and click the Confirm button.
   • If you want to automatically create snapshots based on the Generation interval, select Automatic creation as Enabled.
   • Generation cycle is daily, hourly selectable, or weekly, day of week, hourly selectable.

Max IOPS Update

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

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

Edit Max Throughput

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

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

Edit connection server

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

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

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 stopped immediately, so you should proceed with the termination only after fully considering the impact that may arise from the service interruption.

To cancel Block Storage, follow the steps below.

1. All Services > Storage > Block Storage(BM) Click the menu. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Go 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.
   • After navigating to the detailed page of the resource to be terminated, you can also terminate it individually by clicking the Cancel Service button.
4. When the pop-up notifying service termination opens, enter Delete and then click the Confirm button.
5. When termination is complete, check on the Block Storage(BM) List page whether 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.
Block Storage(BM) Details On the page, after adding a connected server, log into the server and perform Multi Path configuration and connection tasks (Mount, Disk Online). After use is complete, perform the disconnect operation (Umount, Disk Offline) and remove the connected server.

Setting up Multi Path

A Multi Path configuration is required before using the volume on the connected server. Follow the steps below.

Linux operating system

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

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

3. Block Storage(BM) List page, click the resource to configure Multi Path. 3. Block Storage(BM) Details Navigate to the page.

4. After checking the server in the Connection Server item, connect. 4. 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 application

     1. In the Linux system, Multi Path is automatically applied during volume detection, and it can be verified with the multipath –ll command.
     2. Volumes with Multi Path applied use Multipath device names such as /dev/mapper/##### rather than the /dev/sd# format, and can be verified with the fdisk –l command.

   • iSCSI replacement timeout value setting

     1. When establishing an iscsi connection, 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. 1. Navigate to the Service Home page of Block Storage (BM).

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

3. On the Block Storage(BM) List page, click the resource to configure Multi Path. 3. Block Storage(BM) Details Navigate to the page.

4. After verifying the server in the Connection Server item, connect. 4. 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 it is a Multi Path configuration, 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 this page, the current server is automatically detected. 4. Check the content and click the Next button.

     5. Select features(Feature selection) On the page, select Features from the left menu, check Multipath I/O, and 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. 8. 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 a message appears, reboot the server again.

     11. After the reboot, you can verify 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 verify 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 in to 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. 1. Navigate to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Go to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to connect the server. 3. Block Storage(BM) Details Navigate to the page.
4. After checking the server in the Connection Server item, connect. 4. Follow the guide below to mount the volume.
   • 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,_netdev   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,_netdev   0 0

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

     Table. Refer to the Mount command

     Reference

     The _netdev option is used when mounting network‑based file systems (NFS, iSCSI, CIFS/SMB, etc.) on Linux, and can prevent mount errors that may occur during boot.

     command	Explanation
     m	Check the usage of the fdisk command.
     n	Create a new partition.
     p	Check the updated partition information.
     t	Change the partition’s system ID.
     w	Save the partition information and then 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. 1. Go to the Service Home page of Block Storage (BM).

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

3. On the Block Storage(BM) List page, click the resource to connect the server. 3. Block Storage(BM) Details Go to the page.

4. After verifying the server in the Connection Server item, connect. 4. Connect the volume (Disk Online) according to the guide below.

   • Windows Start icon right-click, then 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)

After accessing the server and performing the disconnect tasks (Umount, Disk Offline), you need to detach the server in the Console. Follow the steps below.

Linux operating system

1. Click the All Services > Storage > Block Storage(BM) menu. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Go to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to disconnect the server. 3. Block Storage(BM) Details Navigate to the page.
4. Connection Server item, verify the server and then connect. 4. Unmount the volume according to the guide below.
   • 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. 1. Navigate to the Service Home page of Block Storage (BM).

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

3. Block Storage(BM) List On the page, click the resource to disconnect the server. 3. Block Storage (BM) Details Navigate to the page.

4. Connection Server item, verify the server and then connect. 4. Please disconnect the volume (Disk Offline) according to the guide below.

   • Windows Start icon right-click, then run Computer Management
   • In the Computer Management tree, 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 - Using duplication

You can create a replica of the generated Block Storage (BM) in another location and synchronize it periodically. You can perform operations 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. 1. Go to the Service Home page of Block Storage (BM).

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

3. On the Block Storage(BM) List page, click the resource to create a replica. 3. Block Storage(BM) Details Navigate to the page.

4. Verify the setting of the Snapshot Capacity item.

   • Replication can be created only when storage space is available through snapshot capacity configuration.
   • For more details, see 스냅샷 용량 수정하기.

5. Click the Create Clone button. 5. Create Clone popup window opens.

6. After entering the information for creating a clone, click the Create button. 6. Creates a replica with the same disk type.

   Category	Required status	Detailed description
   Replication Policy	Required	Select replication policy Within region: Create replication in the same region’s Availability Zone Cross-region: Create replication in an Availability Zone of a different region
   Clone location	Essential	Select the location to create the replica Region: Select a location different from the original Block Storage (BM) volume Selection is required only when creating replication between regions Availability Zone: Select the Availability Zone to create the replica
   복제 볼륨명	필수	영문으로 시작하며 영문, 숫자와 특수문자(-)를 사용하여 3~28자로 입력하세요.
   복제 주기	필수	5분, 1시간, 매일, 매주, 매월 중 선택하세요. 아래 주기로 복제를 수행합니다. 매일: 매일 23:59:00 매주: 매주 일요일 23:59:00 매월: 매월 1일 23:59:00

   Table. Replication creation information items

7. On the Block Storage(BM) Details page, after clicking the Replication tab, check the replication information you created.

   • 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. 1. Go to the Service Home page of Block Storage (BM).
2. On the Service Home page, click the Block Storage(BM) menu. 2. Go to the Block Storage(BM) List page.
3. On the Block Storage(BM) List page, click the resource to edit the replication policy. 3. Block Storage(BM) Details Go to the page.
4. Clone page, please click. 4. Block Storage(BM) Replication Go to the page.
5. Click the Edit button of the Replication Policy. 5. Edit Replication Policy The popup window opens.
   • Usage: Performs replication. * If it is Paused, you can change it to Enabled.
   • Pause: Temporarily stops replication. * If use is the case, it can be changed to pause.
   • Delete: Delete the replica. * If it is Paused, you can change it to Delete, and after deletion, you cannot use replication again.
6. Check the modified Replication Policy on the Block Storage(BM) Replication page.