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

Return to the regular view of this page.

Storage

Provides a data storage service that enhances stability and efficiency through various storage configurations.

1 - Block Storage(BM)

1.1 - Overview

Service Overview

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

Key Features

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

Composition Diagram

Configuration Diagram
Figure. Block Storage configuration diagram

Provided Function

Block Storage provides the following functions.

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

Components

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

Volume

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

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

Snapshot

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

Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00) standard.
  • Snapshots can be created up to 1,023. (Automatic creation through scheduling is up to 128.)
  • Automatic generation through snapshot schedule setting is possible.
  • The snapshot capacity is added to the Block Storage(BM) fee, so adjust the capacity of the snapshot storage space.

Volume Group

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

Preceding Service

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

Service CategoryServiceDetailed Description
ComputeBare Metal ServerHigh-performance physical server used without virtualization
Table. Block Storage(BM) Preceding Service

1.1.1 - Monitoring Metrics

Block Storage BM Monitoring Metrics

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

Performance Item NameDescriptionUnit
Instance StatusFile Storage Volume Statusstatus
Volume TotalTotal Bytesbytes
IOPS [Total]iops(total)iops
IOPS [Read]iops(reading)iops
IOPS [Write]iops(writing)iops
IOPS [Other]iops (etc.)iops
Latency Time [Total]Delay Time (Total)usec
Latency Time [Read]Delay Time (Read)usec
Latency Time [write]Delay Time (write)usec
Latency Time [Other]Delayed time (etc.)usec
Throughput [Total]Processing amount (total)bytes/s
Throughput [Read]Throughput (Read)bytes/s
Throughput [Write]Throughput (Write)bytes/s
Throughput [Other]Processing capacity (etc.)bytes/s
Table. Block Storage BM Monitoring Metrics

1.2 - How-to Guides

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

Block Storage(BM) Create

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

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

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

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

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

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

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

    • When creation is complete, check the created resources on the Block Storage (BM) List page.
Note
  • All volumes are encrypted by default with server-side encryption based on the AES-256 algorithm, regardless of disk type.
  • Snapshot schedule can be set on the detail page.
  • The performance metrics (IOPS, Throughput) of the configured storage are based on the maximum values and do not guarantee consistent values.
Caution
Capacity cannot be modified after service creation. If needed, add a volume to the same server.

iSCSI Setting up

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

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

Linux Operating System

Notice

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

  • Block Storage(BM) Check iSCSI information on the detail page.
  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List page, click the resource to be used on the connected server. You will be taken to the Block Storage(BM) Details page.
  4. Connection Server Check the server in the item and then connect.
  5. Follow the procedure below to configure iSCSI.
    • Storage (target IP) Discover the connection information.
      Color mode
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      Code Block. Storage (target IP) Connection Information Discovery
    • Connect to Storage (target IP). If already connected, proceed to the next step.
      Color mode
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful
      
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful
      
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      Code block. Storage (target IP) connection
    • To minimize search time, delete all unused Storage (target IP).
      Color mode
      [root@localhost ~]# iscsiadm -m node show
      100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      
      [root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
      [root@localhost ~]# iscsiadm -m node show
      100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      
      [root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
      Code block. Delete unused Storage (target IP)
    • Please rescan to check additional Disk.
      Color mode
      [root@localhost ~]# iscsiadm -m session --rescan
      Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      [root@localhost ~]# iscsiadm -m session --rescan
      Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      Code block. Rescan
    • Set Auto Login so that it automatically logs in even after reboot.
      Color mode
      [root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
      [root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
      [root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
      [root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
      Code block. Auto Login setting
    • Please confirm the final settings using the following command.
      Color mode
      [root@localhost ~]# lsblk
      [root@localhost ~]# lsblk
      Code block. Check configuration content

Windows Operating System

Notice

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

  • Block Storage(BM) Check iSCSI information on the detail page.
  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
  3. Click the resource to be used on the connected server on the Block Storage(BM) List page. It moves to the Block Storage(BM) Details page.
  4. After checking the server in the Connection Server item, connect.
  5. Follow the procedure below to configure iSCSI.
    • Open Command Prompt (Admin) and run PowerShell.
      Color mode
      Windows PowerShell
      Copyright (C) Microsoft Corporation. All rights reserved.
      
      PS C:\Users> cd ..
      PS C:\>
      Windows PowerShell
      Copyright (C) Microsoft Corporation. All rights reserved.
      
      PS C:\Users> cd ..
      PS C:\>
      Code block. powershell execution
    • Start the volume service.
      Color mode
      PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
      PS C:\> Start-Service -Name MSiSCSI
      PS C:\> get-service -Name MSiSCSI |  select -Property Name, DisplayName, Status, StartType
      
      Name       DisplayName                           Status    StartType
      -------    --------------                        -------   -----------
      MSiSCSI    Microsoft iSCSI Initiator Service     Running   Automatic
      PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
      PS C:\> Start-Service -Name MSiSCSI
      PS C:\> get-service -Name MSiSCSI |  select -Property Name, DisplayName, Status, StartType
      
      Name       DisplayName                           Status    StartType
      -------    --------------                        -------   -----------
      MSiSCSI    Microsoft iSCSI Initiator Service     Running   Automatic
      Code block. Volume service start
    • Please install Multipath I/O. If the Restart Needed item is displayed as Yes, a restart is required.
      Color mode
      PS C:\> Install-WindowsFeature -name Multipath-IO
      
      Success   Restart Needed   Exit Code   Feature Result
      -------   --------------   ---------   -----------------
      True      No               Success     {Multipath I/O}
      PS C:\> Install-WindowsFeature -name Multipath-IO
      
      Success   Restart Needed   Exit Code   Feature Result
      -------   --------------   ---------   -----------------
      True      No               Success     {Multipath I/O}
      Code block. Multipath I/O installation
    • Please modify the Initiator Port Address.
      If you are not an Active Directory Member, skip this procedure. The Initiator Port Address needs to be modified only if you are an Active Directory Member.
      • iqn is generated based on the Hostname, but when joined to Active Dicrectory it changes to DNS format.
        Based on the basic hostname, it is registered in Storage, so for iqn.1991-05.com.microsoft:iqn01.scp.com, iqn01 is the Hostname. Remove DNS information and change it to the name registered when creating the OS in the user Console, such as iqn.1991-05.com.microsoft:iqn01.
      • If you are not an AD Member, no changes are required.
        Color mode
        PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
        PS C:\> echo $address
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01.scp.com
        
        PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
        PS C:\> Get-InitiatorPort | select NodeAddress
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01
        PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
        PS C:\> echo $address
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01.scp.com
        
        PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
        PS C:\> Get-InitiatorPort | select NodeAddress
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01
        Code Block. Initiator Port Address Edit
    • Storage (target Portal) Set the address as a variable.
      Color mode
      PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
      PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
      Code block. Set Storage (target Portal) address as variable
    • Discover the Storage (target Portal).
      Color mode
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
      }
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.41
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
      }
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.41
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      Code block. Storage (target Portal) Discovery
    • Connect the disk (target).
      Color mode
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
      }
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370000
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000006
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1100
      PSComputerName          :
      
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370002
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000007
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1000
      PSComputerName          :IsHeaderDigest         : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
      }
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370000
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000006
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1100
      PSComputerName          :
      
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370002
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000007
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1000
      PSComputerName          :IsHeaderDigest         : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      Code block. Disk (target) connection
    • Refresh Storage (target) information.
      Color mode
      PS C:\> Update-IscsiTarget
      PS C:\> Update-IscsiTarget
      Code Block. Storage (target) Information Refresh
    • Register the Multipath I/O DSM and create an MPIO Disk.
      When creating an MPIO disk, a query occurs if a reboot is required. Reboot by entering Y or the Enter Key.
      Color mode
      PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
      PS C:\> Update-MPIOClaimedHW
      
      Confirm
      Are you sure you want to perform this action?
      The operation may require a system restart.
      [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
      False
      PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
      PS C:\> Update-MPIOClaimedHW
      
      Confirm
      Are you sure you want to perform this action?
      The operation may require a system restart.
      [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
      False
      Code block. Multipath I/O DSM registration, MPIO Disk creation
    • Multipath I/O Disk Check the list and path.
      mpclaim.exe can be used to check MPIO disk information. Enter the generated MPIO disk number to check the disk path and status.
      Color mode
      PS C:\> mpclaim.exe -s -d
      For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.
      
      MPIO Disk    System Disk  LB Policy    DSM Name
      -------------------------------------------------------------------------------
      MPIO Disk3   Disk 1       RR           Microsoft DSM
      
      PS C:\> mpclaim.exe -s -d 3
      MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
          Controlling DSM: Microsoft DSM
          SN: 600A098038314853475D543544614131
          Supported Load Balance Policies: FOO RR RRWS LQD WP LB
      
          Path ID          State              SCSI Address      Weight
          ---------------------------------------------------------------------------
          0000000077040001 Active/Optimized   004|000|001|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1000, : 25
      
          0000000077040000 Active/Optimized   004|000|000|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1001, : 26
      PS C:\> mpclaim.exe -s -d
      For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.
      
      MPIO Disk    System Disk  LB Policy    DSM Name
      -------------------------------------------------------------------------------
      MPIO Disk3   Disk 1       RR           Microsoft DSM
      
      PS C:\> mpclaim.exe -s -d 3
      MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
          Controlling DSM: Microsoft DSM
          SN: 600A098038314853475D543544614131
          Supported Load Balance Policies: FOO RR RRWS LQD WP LB
      
          Path ID          State              SCSI Address      Weight
          ---------------------------------------------------------------------------
          0000000077040001 Active/Optimized   004|000|001|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1000, : 25
      
          0000000077040000 Active/Optimized   004|000|000|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1001, : 26
      Code block. Multipath I/O Disk list and path verification
    • Please check in Disk Management.

Block Storage(BM) Check Detailed Information

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

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

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Click the resource to view detailed information on the Block Storage(BM) List page. You will be taken to the Block Storage(BM) Details page.
    • Block Storage(BM) Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Tags, Operation History tabs.
      CategoryDetailed description
      Volume StatusStatus of the volume
      • Creating: Creating
      • Available: Creation completed, server connection possible
      • Attaching: Connecting to server
      • Detaching: Disconnecting from server
      • In Use: Server connection established
      • Deleting: Service termination in progress
      • Editing: Changing settings
      • Error Deleting: Abnormal state while deleting
      • Error: Abnormal state during creation
      Create ReplicationCreate a replica at another location
      • For detailed information about replication creation, see [Create Replication](/userguide/storage/block_storage_bm/how_to_guides/replication.md/#복제-생성하기)
      | | Snapshot Creation | Create a snapshot at a specific point in time
      • For detailed information on snapshot creation, see [Create Snapshot](/userguide/storage/block_storage_bm/how_to_guides/snapshot.md/#스냅샷-생성하기)
      | |Service termination|Button to cancel the service|
      Table. Status Information and Additional Functions
Reference
In the case of a recovery copy, snapshot list, replication tabs are not displayed.

Detailed Information

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

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the Block Storage (BM) service, it refers to the volume SRN
Resource NameResource Name
  • In Block Storage(BM) service, it refers to the volume name
Resource IDUnique resource ID of the service
CreatorUser who created the service
Creation timeDate/time the service was created
EditorUser who modified the service
Modification Date/TimeDate/Time when the service was modified
Volume NameVolume Name
  • If you need to edit the volume name, click the Edit button
CategoryOriginal status regarding duplication
Storage Volume NameVolume name within storage device
  • Information distinguishing the volume used for analysis when failures and issues occur
capacityvolume capacity
IOPSIOPS value set when creating service
  • HDD type does not provide this metric
ThroughputThroughput speed (MB/s) set when creating the service
  • HDD type does not provide this metric
Disk typeDisk type
EncryptionEncryption status
  • Encryption provided by default regardless of disk type
Volume GroupName of the Volume Group that the volume belongs to
iSCSI informationStorage Target IP information for server connection
Snapshot CapacityCapacity of snapshot storage space
  • Charges incurred according to the set capacity
  • Click the edit button if you need to set snapshot capacity
  • For detailed information on snapshot capacity, refer to [Edit Snapshot Capacity](/userguide/storage/block_storage_bm/how_to_guides/_index.md/#스냅샷-용량-수정하기)
| | Snapshot Schedule | Snapshot automatic creation cycle
  • After setting snapshot capacity, schedule can be registered
  • Click the edit button when snapshot schedule setting is needed
  • For detailed information on snapshot schedule, refer to [Edit Snapshot Schedule](/userguide/storage/block_storage_bm/how_to_guides/_index.md/#스냅샷-스케줄-수정하기)
| | Snapshot | Name of the snapshot
  • Display when a snapshot exists
  • Click the name to go to the snapshot's detail page
  • For details on creating a snapshot, see [Create Snapshot](/userguide/storage/block_storage_bm/how_to_guides/snapshot.md/#복구본-생성하기)
| | Connected Server | Connected Bare Metal Server
  • **Server Name**: Server Name
  • **Image**: Server's OS image
  • **Status**: Server status
  • When adding a Bare Metal Server connection, click the **Add** button
  • When removing a Bare Metal Server connection, click the **Disconnect** button
  • For more details about the connected server, see [Edit Connected Server](/userguide/storage/block_storage_bm/how_to_guides/_index.md/#연결-서버-수정하기)
|
Table. Block Storage(BM) Detailed Information Items
Reference
For volumes created before December 18, 2025, IOPS and Throughput information is not displayed.

Snapshot List

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

CategoryDetailed description
Snapshot UsageTotal Capacity of Stored Snapshots
Snapshot nameSnapshot name
CapacitySnapshot Capacity
Creation TimeSnapshot Creation Time
Additional features > MoreSnapshot management button
  • Restore: Restore volume from snapshot
  • Create restore point: Create restore point from snapshot
  • Delete: Delete snapshot
Table. Snapshot List Tab Detailed Information Items
Caution
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • Snapshots can be created up to a maximum of 1,023 (the automatic creation count via schedule is up to 128), and if the maximum creation count is exceeded, no more snapshots can be created.
  • Snapshot recovery must be performed while all connected servers are disconnected (Umount, Disk Offline), and the recovered volume can be used after being reconnected (Mount, Disk Online).
  • Only one recovery copy can be created, and it is a separate volume that incurs the same charges as the original.
Reference
  • Snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
  • Snapmirror files cannot be deleted when using replication.
  • When using Volume Group, set the snapshot schedule on the Volume Group (BM) detail information screen. The created snapshots can be viewed in the Block Storage (BM) snapshot list.

Replication

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

CategoryDetailed description
Replication PolicyReplication policy set by the user
Replication CycleReplication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationVolume information of original and replica
  • Classification: Distinguish whether original related to replication
  • Volume Name: Volume name of original or replica
  • Location: Location where the volume was created
  • Permissions: User permissions of the volume set according to replication policy
Table. Replication Tab Detailed Information Items
Caution
If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
Reference
  • When creating a clone, a replica with the same disk type is created.
  • After setting the snapshot capacity, you can create a replica.
  • If using Volume Group, check the replication information on the Volume Group (BM) list page.
  • A replica can modify the connected server if the replication policy is stopped or deleted.
  • The replica can use the snapshot feature after the replication policy is deleted.
  • If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule in the replica.

Tag

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

CategoryDetailed description
Tag ListTag List
  • You can check the Key and Value information of tags
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the previously created Key and Value list
Table. Block Storage(BM) Tag Tab Items

Work History

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

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, resource type, resource ID, resource name, work details, event topic, work result, verify worker information
  • Click the detailed search button to perform a detailed search
Table. Work History Tab Detailed Information Items

Block Storage(BM) Resource Management

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

Edit Volume Name

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

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List Click the resource to edit the volume name. Block Storage(BM) Details page will be opened.
  4. Click the Edit button of Volume Name. Volume Name Edit popup opens.
  5. Enter the volume name and click the Confirm button.
Reference
It must start with an English letter and can be set using English letters, numbers, and the special character (-) within 3 to 28 characters.

Modify Snapshot Capacity

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

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) list page.
  3. Block Storage(BM) List page, click the resource to modify the snapshot capacity. Block Storage(BM) Details page will be opened.
  4. Click the Edit button of the Snapshot Capacity item. The Snapshot Capacity Edit popup window opens.
  5. Set the Usage status and Generation Capacity (%), and click the Confirm button.
    • Generation capacity(%) can be selected in units of 50 between 100 and 500.
Caution
  • The charges change depending on whether snapshots are used and their size. (Example: If the volume size is 10GB and the snapshot creation size is 100%, a total of 20GB charges occur.)
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
  • If the size after modification is smaller than the original, older snapshots will be deleted first.
  • When edited as unused, all snapshots will be deleted.
  • Replication can be created after setting snapshot capacity.
  • After setting the snapshot capacity, it can be added to the Volume Group.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • The replica can use the snapshot feature after the replication policy is deleted.

Edit Snapshot Schedule

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

  1. All Services > Storage > Block Storage(BM) menu, click it. Navigate to the Service Home page of Block Storage(BM).
  2. 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 on the page, click the resource to edit the snapshot schedule. Block Storage(BM) Details page will be opened.
  4. Click the Snapshot Schedule Edit button. The Snapshot Schedule Edit popup opens.
  5. Set the snapshot auto generation status and generation interval, and click the Confirm button.
    • Creation Cycle based, if you want to automatically create snapshots, select Auto Creation as Enabled.
    • Generation cycle can be selected daily, hourly, or weekly, day of week, hourly.
Caution
Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically created via schedule), and if the maximum number is exceeded, no more snapshots can be created.
Note
  • The snapshot schedule is based on Asia/Seoul (GMT +09:00).
  • After setting snapshot capacity, schedule registration is possible.
  • When setting a snapshot schedule, it cannot be added to the Volume Group.

Modify IOPS

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

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

Throughput Edit

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

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

Edit Connection Server

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

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
  3. On the Block Storage(BM) List page, click the resource to edit the connected server. You will be taken to the Block Storage(BM) Details page.
  4. If you want to add a connection server, click the Add button in the Connection Server item. The Add Connection Server popup window will open.
  5. After selecting the server you want to connect to, click the Confirm button.
  6. If you want to disconnect the server, click the Disconnect button in the Connection Server item.
    • Be sure to connect to the server and perform the disconnect operation (Umount, Disk Offline) before disconnecting.
Caution
  • Connect to the server and be sure to perform disconnect operations (Umount, Disk Offline) before releasing the connected server. If you release without OS operations, a status error (Hang) may occur on the connected server. For detailed information on server disconnect, see Disconnect Server.
Reference
  • You can connect up to 8 Bare Metal Servers created in the same location as Block Storage.
  • There is no limit on the number of volume connections for Bare Metal Server.
  • When adding a connected server, you can use it after performing connection tasks (Mount, Disk Online) on the server. For detailed information about server connection, refer to Server Connection.
  • Please connect to the server and be sure to perform disconnect operations (Umount, Disk Offline) before releasing the connected server. If you release without OS operations, a status error (Hang) may occur on the connected server. For detailed information on server disconnect, refer to Disconnect Server.
  • If the replica’s replication policy is stopped or deleted, the connected server can be modified.

Block Storage(BM) Cancel

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

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

To cancel Block Storage, follow the steps below.

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

1.2.1 - Connecting to a Server

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

Configuring Multi Path

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

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

Linux Operating System

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

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

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

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

    • Device confirmation

      1. The created volume can be confirmed using the fdisk -l command.
    • DM-Multipath application confirmation

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

      1. Set the replacement timeout when connecting to iSCSI.
      # vi /etc/iscsi/iscsid.conf
      node.session.timeo.replacement_timeout = 5
      (change the default value of 120 to 5)
      
      1. After changing the above content, restart the iSCSI service
      # systemctl restart iscsid
      

Windows Operating System

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

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

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

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

    • Device confirmation

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

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

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

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

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

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

        MultiPath

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

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

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

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

        MultiPath

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

        • If a message is displayed, reboot the server again.
      11. After the reboot is complete, you can confirm NETAPP Devices in MPIO devices.

        MultiPath

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

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

Connecting to a Server (Mount, Disk Online)

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

Linux Operating System

Server Connection Example Configuration
  • Server OS: LINUX
  • Mount location: /data
  • Volume capacity: 24 GB
  • File system: ext3, ext4, xfs, etc.
  • Additional allocated disk: /dev/vdb
  1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

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

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

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

    • Switch to root privileges

      $ sudo -i
      
    • Confirm the disk

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

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

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

      # mkdir /data
      
      # mount /dev/vdb1 /data
      
      # lsblk
      NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
      vda       252:0   0    24G  0 disk
      ├─vda1    252:1   0  23.9G  0 part [SWAP]
      └─vda14   252:14  0     4M  0 part /
      └─vda15   252:15  0   106M  0 part /boot/efi
      vdb       252:16  0    24G  0 disk
      └─vdb1    252:17  0    24G  0 part /data
      
      # vi /etc/fstab
      (add) /dev/vdb1     /data       ext4     defaults   0 0
      
ItemDescription
cat /etc/fstabLinux system file containing filesystem information. Used when the server starts.
df -hConfirms the total disk usage of the mounted filesystems in the Linux system.
fdisk -lConfirms partition information.
  • Physical disks are displayed with letters such as a, b, c, etc. (e.g., /dev/sda, /dev/sdb, /dev/sdc)
  • Disk partitions are displayed with numbers such as 1, 2, 3, etc. (e.g., /dev/sda1, /dev/sda2, /dev/sda3)
Table. Mount Command Reference
CommandDescription
mDisplays the usage of the fdisk command.
nCreates a new partition.
pDisplays the changed partition information.
tChanges the system ID of the partition.
wSaves the partition information and exits the fdisk settings.
Table. Partition Creation Command (fdisk) Reference

Windows Operating System

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

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

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

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

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

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

    • Confirm the disk

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

Disconnecting from the Server (Umount, Disk Offline)

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

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

Linux Operating System

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

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

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

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

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

Windows Operating System

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

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

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

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

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

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

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

    Umount
    • Check the disk status
    Umount

1.2.2 - Using Snapshots

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

Create Snapshot

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

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List page, click the resource to create a snapshot. Navigate to the Block Storage(BM) Details page.
  4. Snapshot Capacity Check the setting status of the item.
    • Snapshots can only be created when storage space is secured by setting the snapshot capacity.
    • For more details, please refer to Modify Snapshot Capacity.
  5. Click the Create Snapshot button. Create Snapshot popup window opens.
  6. Confirm Click the button. Creates a snapshot of the current point in time.
  7. Click the Snapshot List page. Go to the Block Storage(BM) Snapshot list page.
  8. Check the generated snapshot.
Caution
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
  • If the usage rate within snapshot capacity is high (around 90%), replication may be stopped.
  • If there is a volume in the Volume Group with snapshot capacity not set, you cannot create a snapshot. Set the snapshot capacity for all volumes first.
  • Snapshots can be created up to a maximum of 1,023 (the automatic creation count via schedule is up to 128), and if the maximum creation count is exceeded, no more snapshots can be created.
Reference
  • The snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
  • If you want to automatically create snapshots via a schedule, set the snapshot schedule on the Block Storage(BM) Details page.
  • For detailed information about snapshot schedules, see Edit Snapshot Schedule.
  • The replica can use the snapshot feature after the replication policy is deleted.

Recover Snapshot

Block Storage(BM) volumes can be restored from a snapshot. To perform snapshot recovery, follow the steps below.

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) list page.
  3. Block Storage(BM) List On the page, click the resource to restore from the snapshot. Block Storage(BM) Details Navigate to the page.
  4. If there is a server added in the Connection Server item, after connecting to the server, perform the disconnect operation (Umount, Disk Offline).
  5. Snapshot List Click the page. Block Storage(BM) Snapshot List Go to the page.
  6. After checking the Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to restore.
  7. Recovery Click the button. The snapshot recovery popup window opens.
  8. Snapshot Name and Creation Date and Time after checking, click the Confirm button. Recover the Block Storage volume as a snapshot.
  9. Click the Details button. You will be taken to the Block Storage (BM) Details page.
  10. Connection Server If there is a server added in the item, after connecting to the server, perform the connection tasks (Mount, Disk Online).
Caution
  • Snapshot recovery must be performed while disconnected (Umount, Disk Offline) on all connected servers, and the recovered volume can be used after reconnecting (Mount, Disk Online).
  • After the snapshot recovery is completed, all snapshots created after the snapshot used for recovery will be deleted.
  • When restoring a snapshot, the volume is restored to that point.
  • If you are using Volume Group (BM), you can perform snapshot recovery from the detail page of Volume Group (BM).

Create a recovery copy

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

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource to restore from a snapshot. You will be taken to the Block Storage(BM) Details page.
  4. Connection Server If there is a server added in the item, after connecting to the server, perform the disconnect operation (Umount, Disk Offline).
  5. Snapshot List page, click it. Block Storage(BM) Snapshot List page, go to it.
  6. After confirming the Snapshot name and Creation date/time, click the More button of the snapshot you want to create a recovery copy for.
  7. Click the Create Recovery button. The snapshot recovery creation popup opens.
  8. After entering the Recovery volume name, click the Confirm button. A popup notifying the creation of the recovery copy opens.
  9. Click the Confirm button. The recovery copy creation request is completed.
Caution
  • Only one backup can be created per original.
  • A recovery copy is a separate volume created with the same capacity as the original, and incurs additional costs.
  • If you are using Volume Group (BM), you can create a backup on the detail page of Volume Group (BM).

Delete Snapshot

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

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Service Home on the page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
  3. Block Storage(BM) List page, click the resource to delete the snapshot. Block Storage(BM) Details page will be opened.
  4. Click Snapshot List. Go to the Block Storage (BM) Snapshot List page.
  5. After checking the Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to delete.
  6. Click the Delete button. The snapshot will be removed from the Snapshot List page.
Reference
  • Snapshots that contain snapmirror in the snapshot name cannot be deleted. snapmirror is included in the snapshot name when a replication is created.
  • If you are using Volume Group (BM), you can delete snapshots from the detail page of Volume Group (BM).

1.2.3 - Using Replication

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

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

Create a copy

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

  1. All Services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
  3. Block Storage(BM) list page, click on the resource to create a replica. It moves to the Block Storage(BM) details page.
  4. Snapshot capacity item’s setting status should be checked.
  • Replication creation is only possible when storage space is secured through snapshot capacity setting.
  • For more detailed information, please refer to Modifying snapshot capacity.
  1. Replicate Create button will be clicked. Replicate Create popup window will be opened.
  2. Replication location and replication volume name, replication cycle should be entered and the confirm button should be clicked. It creates a replica with the same disk type.
  • Replication location: Select a location different from the original Block Storage(BM) volume.
  • Replica Volume Name: It should start with English and use English, numbers, and special characters(-) to input 3-28 characters.
  • Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the selected cycle.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Replication page will be clicked. It moves to the Replication page.
  2. Check the replication information.
  • When selecting the volume name of the original or replica, it moves to the Block Storage(BM) details page of the volume.
Note
  • When replicating, a replica with the same disk type is created.
  • After setting the snapshot capacity, a replica can be created, and the disk type of the created replica is the same as the original.
  • In cases where the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • After setting the snapshot capacity, the volume added to the Volume Group can be replicated in units of Group on the Volume Group page.
  • One replica can be created per volume, and additional data transfer fees apply when replicating across regions.
  • The replicated created volume cannot be added to the Volume Group.
  • If you are using Volume Group, you can check the replication information from Volume Group (BM).

Modify replication policy

You can change the replication status through replication policy modification.

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

To modify the replication policy, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
  3. Block Storage(BM) list page, click the resource to modify the replication policy. It moves to the Block Storage(BM) details page.
  4. Replication page is clicked. It moves to the Block Storage(BM) replication page.
  5. Replication Policy’s Edit button should be clicked. Replication Policy Edit popup window will be opened.
  • Usage: performs replication. Paused can be modified to Usage.
  • Temporary suspension: temporarily suspends replication. If in use, it can be modified to temporary suspension.
  • Delete: It deletes the replication. In case of pause, it can be modified to delete, and after deletion, replication cannot be used again.
  1. Block Storage(BM) replication page, check the modified replication policy.
Caution
  • Be aware of the following when deleting a policy.
  • After deleting the policy, the replica is not converted to the original and cannot create a replica.
  • After deleting the policy, you cannot connect to the existing replica, and you can only create a new replica.
  • Data stored only in replicas after temporary suspension will be deleted when replication is used again.
  • When using the replication policy, the replica is in a read-only state and data modification is not possible. Please use replication after unmounting from all connected resources
  • The replication policy can be mounted from the connection server only when it is deleted or in a paused state.

Modify replication cycle

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

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

To modify the replication cycle, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
  3. Block Storage(BM) list page, click the resource to modify the replication cycle. It moves to the Block Storage(BM) details page.
  4. Replication page will be clicked. It moves to the Block Storage(BM) replication page.
  5. Replication Cycle’s Edit button should be clicked. Replication Cycle Edit popup window will be opened.
  • Replication cycle: Select from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the selected cycle.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Block Storage(BM) replication page where you can check the modified replication cycle.

1.2.4 - Using Volume Group

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

Creating Volume Group (BM)

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

To create Block Storage, follow the next procedure.

  1. All services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Volume Group(BM) menu should be clicked. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) page, click the Volume Group(BM) creation button. It moves to the Volume Group(BM) creation page.
    Classification
    Mandatory
    Detailed Description
    Volume Group nameRequiredVolume Group name
    • Starts with English and uses English, numbers, and special characters (-) to input 3-28 characters
    • Cannot be modified after service creation
    Target VolumeRequiredAdd target volume to Volume Group
    • Add button is clicked, and then select the target volume in the target add popup
    • Target volume basis
      • Snapshot capacity: Setting
      • Snapshot automatic creation, creation cycle: Not used
      • Replication: Not used
      • Up to 16 can be added
    Table. Volume Group(BM) Service Information Input Items
  4. Complete button을 클릭하세요 -> 4. Complete button should be translated as: 4. Click the Complete button. So the final translation is: 4. Click the Complete button.
  • Once creation is complete, check the created resource from the Volume Group(BM) list page.
Reference
  • When adding the target volume, you can add the volume corresponding to the following to the Volume Group (BM).
  • Snapshot capacity: setting
  • Snapshot automatic creation, creation cycle: not used
  • Replication: Not used
  • The target volume can be added up to a maximum of 16.

Volume Group(BM) detailed information check

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

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

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click on the resource to check the detailed information. It moves to the Volume Group(BM) details page.
  • Volume Group(BM) details page displays status information and additional feature information, and consists of details, snapshot list, replication, tags, job history tabs.
    ClassificationDetailed Description
    Volume Group statusVolume Group’s status
    • Creating: being created
    • Available: creation completed, server connection available
    • Deleting: service termination in progress
    • Editing: settings being changed
    • Error Deleting: abnormal state during deletion
    • Error: abnormal state during creation
    Replication creationCreate a replica in a different location
    Creating a snapshotCreate a snapshot at a specific point in time
    Service CancellationButton to cancel the service
    Table. Status Information and Additional Functions
Reference
For a recovery file, the snapshot list, replication tabs are not displayed.

Detailed Information

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

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

Snapshot list

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

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

Replication

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

ClassificationDetailed Description
Replication PolicyReplication policy set by the user
Replication CycleThe replication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationVolume information of the original and replica
  • Classification: Classification of whether it is a replica-related original
  • Volume Group Name: Volume Group name of the original or replica
  • Location: Location where the volume was created
  • Authority: User authority of the volume set according to the replication policy
Table. Replication tab detailed information items
Caution
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped
Reference
  • When replicating, a replica with the same disk type is created.
  • Snapshot capacity setting and replica creation are possible after setting.
  • If you are using a Volume Group, check the replication information on the Volume Group(BM) resource list page.
  • The replica Block Storage can modify the connected server when the replication policy is paused or deleted.
  • The replica Block Storage can use the snapshot feature after the replication policy is deleted.
  • If the replication policy is paused or the replication status is completed, you can modify the policy and cycle from the replica.

Tag

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

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

Work History

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

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

Volume Group(BM) Resource Management

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

Modifying the Snapshot Schedule

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

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the snapshot schedule. It moves to the Volume Group(BM) details page.
  4. Snapshot Schedule item’s Edit button should be clicked. Snapshot Schedule Edit popup window will be opened.
  5. Set the snapshot automatic creation and creation cycle, and click the confirm button.
  • Creation Cycle basis to automatically create a snapshot, in the case of Auto Creation select Yes.
  • Creation cycle can be selected as daily, hourly, or weekly, day of the week, hourly.
Caution

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

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

Modifying the target volume

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

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the target volume. It moves to the Volume Group(BM) detail page.
  4. If you add a target volume, click the Add button in the Target Volume item. The Add Volume popup window opens.
  • If you want to disconnect the volume, click the Disconnect button in the Target Volume section.
  1. Select the volume you want to add and then click the Confirm button.
Caution
  • Volume Group’s replication policy is in use, the target volume cannot be modified.
Reference
  • When adding the target volume, you can add the following volume to the Volume Group (BM).
  • Snapshot capacity: settings
  • Snapshot automatic creation, creation cycle: not used
  • Copy: Not used
  • The target volume can be added up to a maximum of 16.

Volume Group(BM) snapshot usage

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

Creating a snapshot

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

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click on the resource to create a snapshot. It moves to the Volume Group(BM) details page.
  4. Create Snapshot button is clicked. Create Snapshot popup window is opened.
  5. Confirm button, click. It creates a snapshot of the current point in time.
  6. Snapshot List page, click. It moves to the Volume Group(BM) Snapshot list page.
  7. Check the generated snapshot.
Caution
  • When creating a snapshot in the Volume Group, a snapshot is also created on the connected target volume.
  • Volume Group snapshot usage, manage the snapshot capacity and number of the target volume.
  • If the maximum number of snapshot creations or the threshold of snapshot space (around 90%) is exceeded, old snapshots will be deleted from oldest.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • A snapshot can be created up to 1,023 (the automatic creation number through the schedule is up to 128), and if the maximum creation number is exceeded, no more snapshots can be created.
Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00) standard.
  • Snapshot storage space will be applied according to the settings on the Block Storage(BM) details page of the target volume.
  • If you want to automatically create snapshots through a schedule, set the snapshot schedule on the Volume Group(BM) details page.
  • For more information about the snapshot schedule, please refer to Modifying the Snapshot Schedule.
  • The replica can use the snapshot feature after the replication policy is deleted.

Restoring a snapshot

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

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to be restored with a snapshot. It moves to the Volume Group(BM) detail page.
  4. Click the Volume Name of the volume added to the Target Volume. It moves to the Block Storage(BM) Detail page.
  5. connected server item has a server added, after server connection, perform disconnect work (Umount, Disk Offline) please.
  1. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
  2. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to restore.
  3. Restore button, click. Snapshot restore popup window opens.
  4. Snapshot name and Creation time are confirmed after clicking the Confirm button. The target volumes are restored as snapshots.
  5. Detailed Information button will be clicked. It will move to the Volume Group(BM) Detail page.
  6. Click the Volume Name of the volume added to Target Volume. You will be taken to the Block Storage(BM) Detail page.
  7. connected server items have been added, after server connection, perform connection work (Mount, Disk Online)
Caution
  • Snapshot recovery must be performed with all target volumes disconnected (Umount, Disk Offline) from the connected server, and the recovered volume can be used after reconnection (Mount, Disk Online).
  • After the snapshot restoration is complete, all snapshots created after the snapshot used for restoration will be deleted.

Creating a recovery version

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

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click on the resource to create a backup. It moves to the Volume Group(BM) details page.
  4. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
  5. Snapshot name and Creation time are confirmed, then click the More button of the snapshot you want to create a restore from.
  6. Restore Point Creation button should be clicked. Snapshot restore point creation popup window will be opened.
  7. Enter the Prefix and then click the Confirm button. A pop-up window announcing the creation of a backup will open.
  • The name of the backup is created with the input prefix value + original Block Storage name entered.
  1. Confirm button will be clicked. The application for creating a backup copy will be completed.
Caution
  • A backup copy can be created only one per original.
  • The recovery volume is a separate volume created with the same capacity as the original, and additional costs are incurred.

Deleting a snapshot

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

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to delete the snapshot. It moves to the Volume Group(BM) details page.
  4. Click Snapshot list. You will be taken to the Volume Group (BM) snapshot list page.
  5. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to delete.
  6. Delete button will be clicked. Snapshot list page will remove the snapshot.
Reference
When using replication, the snapmirror file cannot be deleted.

Volume Group(BM) replication usage

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

Create a copy

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

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to create a replica. It moves to the Volume Group(BM) details page.
  4. Replicate Create button should be clicked. Replicate Create popup window will be opened.
  5. Replication Location and Replication Volume Group, Replication Block Storage Name Prefix, Replication Cycle should be entered and the Confirm button should be clicked. It creates a replica Volume Group and a replica Block Storage volume with the same disk type.
  • Replication location: Select a location different from the original Volume Group (BM).
  • Replica Volume Group name: It should start with English and use English, numbers, and special characters (-) to input 3-28 characters.
  • Replica Block Storage Name Prefix: It should start with English and use English, numbers, and special characters (-) to input 3-28 characters.
  • The replica Block Storage(BM) is created with a volume name of ‘replica Block Storage name prefix + original Block Storage volume name’.
  • Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the cycle below.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Replication page will be clicked. It moves to the Replication page.
  2. Check the replication information.
  • When the original or replica Volume Group name is selected, it moves to the Volume Group(BM) details page.
Note
  • When creating a replica in the Volume Group, a replica Volume Group and Block Storage (BM) are created.
  • The replica Block Storage has the same type as the original and disk type.
  • You can create one replica per Volume Group, and additional data transfer fees apply when replicating across regions.

Modify replication policy

You can change the replication status through replication policy modification.

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

To modify the replication policy, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the replication policy. It moves to the Volume Group(BM) details page.
  4. Replication page will be clicked. It moves to the Volume Group(BM) Replication page.
  5. Replication Policy’s Edit button is clicked. Replication Policy Edit popup window is opened.
  • Usage: performs replication. Pause can be modified to Usage.
  • Temporary Suspension: temporarily suspends replication. If in use, it can be modified to temporary suspension.
  • Delete: It deletes the replication. In case of pause, it can be modified to delete, and after deletion, replication cannot be used again.
  1. Volume Group(BM) replication page where you can check the modified replication policy.
Caution
  • Note the following when deleting a policy.
  • After deleting the policy, the replica cannot be converted to the original and replication cannot be created.
  • After deleting the policy, you cannot connect to the existing replica, and you can only create a new replica.
  • Data stored only in replicas after temporary suspension will be deleted when replication is used again.
  • When using the replication policy, the replica is in a read-only state and data modification is not possible. Please use replication after unmounting all connected resources

Modify Replication Cycle

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

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

To modify the replication cycle, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the replication cycle. It moves to the Volume Group(BM) details page.
  4. Replication page is clicked. It moves to the Volume Group(BM) replication page.
  5. Replication Cycle’s Edit button should be clicked. Replication Cycle Edit popup window will be opened.
  • Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the cycle below.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Volume Group(BM) replication page where you can check the modified replication cycle.

Volume Group(BM) cancellation

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

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

1.3 - API Reference

API Reference

1.4 - CLI Reference

CLI Reference

1.5 - Release Note

Block Storage(BM)

2025.12.16
FEATURE IOPS, Throughput setting feature added
  • You can set the volume performance metrics (IOPS, Throughput) and edit them on the detail page.
    • IOPS: 3,000 ~ 16,000
    • Throughput: 125 ~ 1,000
    • No separate charges during the preview period (billing planned for the first half of 2026).
2025.10.23
FEATURE Add snapshot recovery creation feature
  • The feature to create a recovery (Recovery) using snapshots has been added.
    • A recovery copy is a separate volume created with the same capacity as the original, and additional costs are incurred.
2025.07.01
FEATURE New feature addition and monitoring integration
  • HDD Disk type has been added. When creating Block Storage (BM), HDD disk can be selected.
  • Provides an IaC environment through Terraform.
  • You can use the snapshot feature on a replica volume.
  • Cloud Monitoring has been linked.
    • You can view IOPS, Latency, and Throughput information in Cloud Monitoring.
2025.02.27
FEATURE Add replication and Volume Group feature
  • Block Storage(BM) Feature Change
    • Block Storage(BM) Replication feature that allows volumes to be replicated to another location has been added.
    • The Volume Group feature has been added, allowing you to set up to 16 Block Storage (BM) volumes as a group to create snapshots and replication at a consistent point in time.
    • For detailed information, please refer to Block Storage(BM) Overview.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM and Service Home, tags etc. reflected the common CX changes.
2024.10.01
NEW Block Storage(BM) Service Official Version Release
  • Launched a high-performance storage service suitable for handling large-scale data and database workloads.

2 - File Storage

2.1 - Overview

Service Overview

File Storage servers connected via network can easily store and share data can, making it suitable for application environments that use multiple servers.
You can select the disk type according to performance requirements, and it will automatically expand or shrink according to the user’s data size without capacity limits.

Features

  • Free volume usage: The volume capacity is automatically expanded or reduced according to data creation and deletion without user configuration. There is no cost for creating volumes, and only usage fees for stored data capacity are incurred.
  • Various disk types provided: Users can select disk type according to usage purpose. HDD that can store large data cost‑effectively, SSD that provides reduced response time and high IOPS performance, and high‑performance SSD can be used.
  • Snapshot Backup: Through the image snapshot feature, recovery of changed or deleted data is possible, and when performing disk backup, snapshots can be stored in a location different from the original. Users select the snapshot created at the point in time they wish to recover from the list and perform the recovery.
  • Replication: Creates an identical replica volume at a different location, and the user can set the data replication schedule. In case the original volume cannot be used due to failures or disasters, service can be provided through the replica volume.

Configuration Diagram

Diagram
Figure. file Storage diagram

Provided Features

File Storage provides the following features.

  • Volume Name: Users can set or edit names per volume.
  • Disk Type: You can select the disk type according to the user’s performance requirements.
    • HDD: General Volume
    • SSD: High-performance general volume
    • High-performance SSD: Performance-optimized volume that can be connected to a Multi-node GPU Cluster
    • SSD SAP_S, SSD SAP_E: SAP Account dedicated volume
  • Protocol: You can select the protocol according to the user’s OS Image.
    • NFS: Primarily used on Linux operating systems
    • CIFS: Primarily used in Windows operating systems
  • Free volume usage: Provides flexible volume size based on the amount of stored data without user capacity settings.
  • Connection Resources: Virtual Server, Bare Metal Server, Multi-node GPU Cluster can be connected and used.
  • Encryption: Regardless of disk type, all volumes are encrypted with the XTS-AES-256 algorithm.
  • Snapshot: Through the image snapshot feature, you can create snapshots immediately or schedule them.
    • Retention Count: The number of snapshots retained that are automatically created via schedule
    • Schedule: Snapshot automatic 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
  • Replication: Replicates the volume to another location, and the user can set the replication interval.
  • Disk Backup: Stores snapshots on backup-dedicated HDD storage and allows you to select the backup location.
  • VPC Endpoint connection: File Storage can be used via Private Network connection from an external network.
  • Monitoring: You can view usage, IOPS, Throughput, etc., monitoring information through the Cloud Monitoring service.
  • ServiceWatch Service Integration Provided: You can monitor data through the ServiceWatch service.

Components

You can create a volume by selecting the disk type and protocol according to the user’s service environment and performance requirements.
When using the snapshot feature, you can restore data to the point in time you want to recover.

Volume

Volume (Volume) is the basic creation unit of the File Storage service and is used as data storage space. Users select a name, disk type, and protocol (CIFS/NFS) to create a volume, then connect it to one or more servers for use.
The volume name creation rules are as follows.

  • Must start with a lowercase English letter and can be set to 3~21 characters using lowercase letters, numbers, and special character (_).

Snapshot

Snapshot (Snapshot) is an image backup at a specific point in time. Using the image snapshot feature, you can recover changed or deleted data or store the snapshot in a different location from the original when performing disk backup. The user selects the snapshot created at the point in time they want to recover from the snapshot list and performs the recovery.
The notes for using snapshots are as follows.

Reference
  • Snapshot creation time is based on Asia/Seoul (GMT +09:00).
  • Snapshots can be created up to 800, and snapshots generated by schedule are not included. (Automatic creation via schedule is up to 128)
  • By selecting the snapshot recovery button, you can restore the File Storage volume to the latest snapshot.
  • If you select a specific snapshot from the snapshot list, recovery is possible by creating a new volume based on the snapshot.
  • Automatic creation is possible through snapshot schedule settings.
  • Snapshot capacity is included in File Storage usage and incurs charges, so adjust storage capacity by setting the snapshot retention period.

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

Service CategoryServiceDetailed Description
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeBare Metal ServerHigh-performance physical server used without virtualization
Table. File Storage Preceding Service

2.1.1 - Monitoring Metrics

File Storage monitoring metrics

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

Performance Item NameDescriptionUnit
Instance StatusFile Storage volume statusstatus
Volume UsedVolume Usedbytes
Volume UsageUsage Rate%
Volume TotalTotal Bytesbytes
IOPS [Total]iops(total)iops
IOPS [Read]IOPS (read)iops
IOPS [Write]IOPS (writing)iops
IOPS [Other]IOPS (etc.)iops
Latency Time [Total]Delay Time (Total)usec
Latency Time [Read]Delay time (read)usec
Latency Time [write]Delayed time (writing)usec
Latency Time [Other]Delayed time (etc.)usec
Throughput [Total]Processing amount (total)bytes/s
Throughput [Read]Throughput (Read)bytes/s
Throughput [Write]Throughput (Write)bytes/s
Throughput [Other]Throughput (etc.)bytes/s
Fig. File Storage Monitoring Metrics

2.1.2 - ServiceWatch Metrics

File Storage sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.

Reference
How to check metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Indicators

The following are the basic metrics for the File Storage namespace.

Indicator NameDetailed DescriptionUnitMeaningful Statistics
iops_readIOPS (read)-measurement at the time of query
iops_writeIOPS (write)-measurement value at the time of query
latency_readLatency (read)MicrosecondsAverage
latency_writeLatency (write)MicrosecondsAverage
throughput_readThroughput (read)Bytes/SecondMeasurement at query time
throughput_writeThroughput (write)Bytes/SecondMeasured value at query time
Table. File Storage Basic Metrics

2.2 - How-to guides

Users can enter the required information for File Storage through the Samsung Cloud Platform Console, select detailed options, and create the service.

Caution
  • Service fees are charged based on usage without capacity constraints.
  • The volume is allocated 100 GB by default. If you want to use more than 100 GB, please inquire about it via Support Center’s Contact Us.
  • If you add or modify company information in Cost Management’s Billing Management, the Mount name (IP information) of File Storage is automatically changed.
    • Before modifying company information, be sure to check the service impact due to changes in Mount name (IP information).
  • When company information is invited to another Organization, the Mount name (IP information) of File Storage is automatically changed.

File Storage Create

You can create and use the File Storage service from the Samsung Cloud Platform Console.

To create a File Storage, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the Create File Storage button on the Service Home page. You will be taken to the Create File Storage page.
  3. File Storage creation On the page, enter the information required to create the service, and select detailed options.
    Category
    Required
    Detailed description
    Volume NameRequiredVolume Name
    • Start with a lowercase English letter and use lowercase letters, numbers, and the special character (_) to enter 3 to 21 characters
    • Generated as ‘user input value + {6-character UUID composed of lowercase English letters and numbers}’
    • Cannot be modified after service creation
    Disk TypeRequiredSelect Disk Type
    • Disk Types
      • HDD: Standard Volume
      • High-Performance SSD: Performance-optimized volume that can be attached to a Multi-node GPU Cluster
      • SSD: High-Performance Standard Volume
      • SSD SAP_S, SSD SAP_E: Volume exclusive to SAP Account (selectable only when created with SAP Account)
    • Cannot be modified after service creation
    • Set to be identical to the original when creating the service via snapshot recovery volume creation, and cannot be modified
    ProtocolRequiredProtocol for sharing volumes over the network from the server
    • NFS: primarily used on Linux operating systems
    • CIFS: primarily used on Windows operating systems
    • Through snapshot recovery volume creation, it is set identical to the original when creating a service and cannot be modified
    Protocol > PasswordRequiredSet account password for volume access when using CIFS protocol
    • Enter 6~20 characters including letters, numbers and special characters ($ % { } [ ] " \)
    Protocol > Password ConfirmationRequiredAccount Password Confirmation
    • Re-enter the password identically
    Recovery Snapshot NameOptionalName of the recovery snapshot used when creating the volume
    • Provide the recovery snapshot name when creating a service through snapshot recovery volume creation
    Table. File Storage Service Information Input Items
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the File Storage List page.
Warning
We recommend storing up to 3.5 million files per directory within the volume. If you exceed 3.5 million, severe performance degradation may occur, so separate directories and manage the number of stored files.
Reference
  • Regardless of disk type, all volumes have server-side encryption based on the XTS-AES-256 algorithm applied by default.
  • SSD SAP When using the SSD SAP disk type, if a failure occurs causing a failover, the LIF (storage mount IP) is automatically transferred. However, you cannot create new volumes on other storage.
  • Snapshot schedule can be set on the detail page.

File Storage View detailed information

File Storage service can view and edit the full resource list and detailed information. File Storage Detail page consists of Detailed Information, Snapshot List, Replication, Disk Backup, Tags, Job History tabs.

To view detailed information of the File Storage service, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Go to File Storage’s Service Home page.
  2. Click the File Storage menu on the Service Home page. Go to the File Storage list page.
  3. Click the resource to view detailed information on the File Storage list page. It navigates to the File Storage details page.
  • File Storage Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Disk Backup, Tags, Job History tabs.
    CategoryDetailed description
    Volume StatusRepresents the status of a volume
    • Creating: Creating
    • Creating From Snapshot: Creating a new volume from snapshot
    • Available: Creation complete, server connection possible
    • Deleting: Service termination in progress
    • Error Deleting: Abnormal state during deletion
    • Inactive: Abnormal state
    • Error: Abnormal state during creation
    • Migrating: Temporary maintenance state
    • Migrating To: Temporary maintenance state
    • Reverting: Reverting snapshot
    • Reverting Error: Snapshot revert abnormal
    Create ReplicationCreate a replica at another location
    • Backups and replicas cannot be used
    • For detailed information on creating replication, see [Create Replication](/userguide/storage/file_storage/how_to_guides/replication.md/#복제-생성하기)
    | | Create Disk Backup | Create a backup copy to store snapshots in backup-dedicated HDD Storage
    • **HDD**, **SSD** disk types can be used
    • Up to 2 backup copies can be created
    • Backup copies and replicas cannot be used
    • For more details on creating disk backups, see [Create Disk Backup](/userguide/storage/file_storage/how_to_guides/disk_backup.md/#디스크-백업-생성하기)
    | | Create Snapshot | Immediately create a snapshot at the time of creation
    • For detailed information about creating snapshots, see [Create Snapshot](/userguide/storage/file_storage/how_to_guides/snapshot.md/#스냅샧-생성하기)
    | | More > Snapshot Recovery | Recover volume with the latest snapshot in **Available** state
    • For detailed information on snapshot recovery, see [Snapshot Recovery](/userguide/storage/file_storage/how_to_guides/snapshot.md/#스냅샷-복구하기)
    | | More > File-level Restore | Enable file-level restore function within snapshots
    • For detailed information on file-level restore, see [Using File-level Restore](/userguide/storage/file_storage/how_to_guides/file_restore.md/#파일-단위-복구-사용하기) reference | | More > Disable file-level restore | Disable file-level restore function within snapshots[Disable file-level restore](/userguide/storage/file_storage/how_to_guides/file_restore.md/#파일-단위-복구-해제하기) Reference | |Service Cancellation|Button to cancel the service|
      Table. Status Information and Additional Functions
Note
Disk backup cannot be used with high-performance SSD disk types.

Detailed Information

On the File Storage List page, you can view detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the File Storage service, it refers to a volume SRN
Resource NameResource Name
  • In the File Storage service, it refers to the volume name
Resource IDService’s unique resource ID
CreatorUser who created the service
Creation DateTimeDate and time the service was created
Volume NameVolume Name
CategoryClassification of original status regarding duplication, disk backup
Disk typeDisk type
UsageVolume usage
ProtocolNFS, CIFS protocol for sharing volumes over the network from the server
Mount nameMount name per volume for server connection
  • ‘scp_{6-digit UUID composed of lowercase English letters and numbers}’ is created
  • The replica’s Mount name can be checked after pausing the replication policy once for the first time
EncryptionEncryption status
  • Encryption provided by default regardless of disk type
Snapshot > ScheduleSnapshot automatic creation cycle
  • Automatically create and store snapshots according to the schedule
  • If snapshot settings are needed, click the **Edit** button
  • For detailed information on snapshot settings, see [Edit Snapshot](/userguide/storage/file_storage/how_to_guides/_index.md/#스냅샷-수정하기)
| | Snapshot > Retention Count | Snapshot Retention Count
  • Number of snapshots retained that are automatically created by schedule
  • If retention count is not entered, 10 is applied automatically
  • If snapshot settings are needed, click the **Edit** button
  • For detailed information on snapshot settings, refer to [Edit Snapshot](/userguide/storage/file_storage/how_to_guides/_index.md/#스냅샷-수정하기)
| | Connected Resources | Connected resources (Bare Metal Server, Virtual Server, GPU Server)
  • **Resource Type**: Service type of the connected resource
  • **Resource Name**: Name of the connected resource
  • **IP**: IP information of the connected resource
  • **Status**: Status of the connected resource
  • NFS volumes are recommended to connect to Linux servers, CIFS volumes to Windows servers
  • Up to 300 connected resources can be added
  • When adding or removing connected resources, select the **Edit** button
  • For more details about connected resources, see [Edit Connected Resources](/userguide/storage/file_storage/how_to_guides/_index.md/#연결-자원-수정하기) reference
| | VPC Endpoint | Connected VPC Endpoint Service
  • **VPC Endpoint Name**: Name of the connected VPC Endpoint
  • **IP**: IP information of the connected VPC Endpoint
  • **Status**: Status of the connected VPC Endpoint
  • When adding or removing a VPC Endpoint, select the **Edit** button
  • For details on editing a VPC Endpoint, see [Edit VPC Endpoint](/userguide/storage/file_storage/how_to_guides/_index.md/#vpc-endpoint-수정하기)
|
Table. File Storage Detailed Information Items

Snapshot List

You can view the snapshot of the selected resource on the File Storage list page.

CategoryDetailed description
Snapshot UsageTotal Capacity of Stored Snapshots
Snapshot NameSnapshot Name
CapacitySnapshot Capacity
Creation TimeSnapshot Creation Time
StatusSnapshot status
  • Available: creation completed, can be restored
  • Creating: creating
  • Error: abnormal state
  • Deleting: deleting
  • Error Deleting: abnormal state while deleting
  • Restoring: restoring
Additional Features > MoreSnapshot Management Button
  • Create Recovery Volume: Create a recovery volume based on a snapshot
  • Delete: Delete Snapshot
Table. Snapshot List Item
Reference
  • Snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
  • Snapshots can be created up to 800, and snapshots created by schedule are not included. (Automatic creation via schedule is up to 128)
  • If you are using replication or disk backup, you cannot delete the snapmirror snapshot.
  • When the snapshot recovery button is clicked, the volume will be restored to the latest snapshot in the Available state.
  • When selecting to create a recovery volume on the snapshot list page, a new volume based on the snapshot is created without modifying the existing volume.
  • The snapshot list can be viewed in the original and backup. The replica can be viewed after the policy is deleted.
  • Snapshot creation, recovery, and recovery volume creation can be used on the original.
  • When using replication or disk backup, you cannot recover with a snapshot, and you can only create a recovery volume.

Replication

You can view the replication information of the selected resource on the File Storage list page.

Notice
Only one copy can be created.
CategoryDetailed description
Replication PolicyReplication policy set by the user
Replication CycleReplication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationOriginal and replica volume information
  • Distinction: Distinguish whether original related to replication
  • Volume Name: Name of the original or replica volume
  • Location: Location where the volume was created
  • Permission: User permissions of the volume set according to replication policy
Table. Clone Tab Detailed Information Items
Caution
When using replication, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, delete the replication policy and recover with a snapshot.
Note
  • When creating a clone, a replica with the same disk type is created.
  • Replication Policy, Replication Cycle can be modified when the replication status in the replica is Completed or Stopped.
  • File-level recovery of the replica can be used when the replication status is Completed or Stopped.
  • The replica’s connection server, VPC Endpoint can be modified when the replication status is stopped.
  • The snapshot-related functions of the replica can be used after the replication policy is deleted.

Disk Backup

You can view the disk backup information of the selected resource on the File Storage List page.

Notice
  • Disk type is HDD or SSD only the original can disk backup. It cannot be used on clones or high-performance SSD.
  • Up to 2 backup copies can be created.
CategoryDetailed description
Backup PolicyBackup policy set by the user
Backup CycleBackup cycle of the original set by the user
  • For detailed information on modifying the backup cycle, see [Modify Backup Cycle](/userguide/storage/file_storage/how_to_guides/dsik_backup.md/#백업-주기-수정하기)
| | Backup status | Backup progress status according to policy settings | | Backup retention count | Number of snapshots retained in the backup | | Volume Information | Original and backup volume information
  • **Classification**: Distinguish whether original related to backup
  • **Volume Name**: Name of the original or backup volume
  • **Location**: Location where the volume was created
  • **Permission**: User permissions of the volume set according to backup policy
|
Table. Disk Backup Tab Detailed Information Items
Caution
When using disk backup, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, cancel the backup and recover with a snapshot.
Reference
  • When creating a backup, it is created as an HDD disk type regardless of the original disk type.
  • Backup Policy, Backup Frequency can be modified when the backup status in the backup set is Completed or Stopped.
  • File-level recovery of the backup can be used when the backup status is Completed or Stopped.
  • The backup copy’s connection server, VPC Endpoint can be modified when the backup status is stopped.
  • Only deletion of backup snapshots is possible.

Tag

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

CategoryDetailed description
Tag ListTag List
  • You can view the Key, Value information of tags
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the existing list of Keys and Values
Table. File Storage Tag Tab Item

Work History

You can view the operation history of the selected resource on the File Storage list page.

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, resource type, resource ID, resource name, work details, event topic, work result, verify worker information
Table. Work History Tab Detailed Information Items

File Storage Resource Management

If you need to modify settings of the created File Storage or add or delete connected servers, you can perform the task on the File Storage Details page.

Edit Snapshot

You can modify the snapshot schedule and retention count. To modify a snapshot, follow these steps.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. File Storage List page, click the resource to modify the snapshot settings. Navigate to the File Storage Details page.
  4. Click the Edit button of the Snapshot item. The Snapshot Edit popup window opens.
  5. Set the Use status and Schedule, Storage Count, and click the Confirm button.
    • Schedule based, if you want to automatically create snapshots, select Use.
  • Schedule can be selected daily, hour-wise, or weekly, day of week, hour-wise.
    • Storage count: Enter a number between 1 and 128. If not entered, it defaults to 10.
Caution
  • If the number of retained items after modification is less than before, older snapshots will be deleted first.
  • If you modify it as unused, the previously created snapshot will be retained.
  • Since snapshot capacity is included in File Storage usage and incurs charges, adjust the storage capacity by setting the number of snapshots to retain.
Reference
  • Snapshot schedule is based on Asia/Seoul (GMT +09:00).

Edit Connected Resources

You can connect or disconnect resources. To modify the connected resources, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. On the File Storage List page, click the resource to edit the linked resource. Navigate to the File Storage Details page.
  4. Click the Edit button of the Connection Resource item. The Select Connection Resource popup opens.
  5. After selecting or deselecting the resource, click the Confirm button.
    • You can select multiple resources at the same time.
Caution
Please connect to the server, perform the disconnect operation (Umount, disconnect network drive), and then disconnect the connected server. If you disconnect without OS operations, a status error (Hang) may occur on the connected server. For detailed information on disconnecting the server, refer to Disconnect Server.
Reference
  • You can connect up to 300 resources at the same location. If you need to connect more than 300, use the API.
  • When adding a connected server, you can use it after performing connection tasks (Mount, network drive connection) on the server. For detailed information about server connections, see Connect to Server.
  • The replica’s connection server can be modified when the replication state is stopped.
  • The backup copy’s connected server can be modified when the backup status is stopped.

VPC Endpoint Edit

You can connect or disconnect a VPC Endpoint.

Notice
Disk type is SSD SAP_S, you cannot modify the VPC Endpoint.

To modify the connection resource, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. File Storage List page, click the resource to modify the VPC Endpoint connection. Navigate to the File Storage Details page.
  4. Click the Edit button of the VPC Endpoint item. The Select VPC Endpoint popup opens.
  5. After selecting or deselecting the resource, click the Confirm button.
    • You can select multiple resources at the same time.
Caution
  • After connecting to the server, be sure to perform the disconnect operation (Umount, disconnect network drive) before releasing the VPC Endpoint. If you release it without OS operations, a status error (Hang) may occur on the connected server. For detailed information on disconnecting the server, refer to Disconnect Server.
  • High-performance SSD Even with the disk type, data sharing is possible by connecting a VPC Endpoint, but be careful as it does not guarantee sufficient performance of the high-performance SSD for connecting internal VPC resources.
  • high-performance SSD Disk type, after checking the connection IP in the VPC Endpoint section, apply for the VPC Endpoint service. You can add a VPC Endpoint created based on the connection IP.
Reference
  • The VPC Endpoint of the replica can be modified when the replication status is stopped.
  • The VPC Endpoint of the backup can be modified when the backup status is stopped.

File Storage Cancel

You can cancel unused File Storage to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
  • Be careful because data cannot be recovered after termination.
  • Service termination is possible for File Storage volumes without connected resources. Please terminate the service after removing all connected servers.
  • Service termination is possible for File Storage volumes without a VPC Endpoint connection. Remove all VPC Endpoints before terminating the service.
  • If the volume is in Available, Error, Inactive state, it can be terminated.
  • The original using Replication or Disk Backup can be terminated after deleting the relevant policy.
    • Replication policy: Pause > Delete
    • Backup policy: Pause > Service termination
  • The replica can be terminated after the replication policy is deleted.
  • The backup copy can be terminated after stopping the backup policy log.

To cancel File Storage, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. File Storage List On the page, select the resource to cancel, and click the Cancel Service button.
  4. When termination is complete, check on the File Storage List page whether the resource has been terminated.

2.2.1 - Connecting to the Server

When using a volume on the server, connection or disconnection work is required.
In the File Storage Details page, add the connection server and then connect to the server to perform the connection work (Mount, Network Drive Connection). After use, perform the disconnection work (Umount, Network Drive Disconnection) and then remove the connection server.

Connecting to the Server (Mount, Network Drive Connection)

To use the volume added to the connection server, you must connect to the server and perform the connection work (Mount, Network Drive Connection). Follow the procedure below.

Linux Operating System (NFS)

Server Connection Example Configuration
  • Mount information: 10.10.10.10:/filestorage
  • Mount location: /data
  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.

  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.

  3. On the File Storage List page, click the resource to be used by the connection server. Move to the File Storage Details page.

  4. Check the server in the Connection Server section and connect to it.

  5. Refer to the procedure below to connect (Mount) the volume.

    • Switch to root privileges

      $ sudo -i
      
    • Install packages (Redhat series)

      # yum install nfs-utils
      
    • Install packages (Debian series)

      # apt-get install nfs-common
      
    • Activate and run NFS-related daemons

      # systemctl enable rpcbind.service
      # systemctl start rpcbind.service
      
    • Mount the volume

      # mkdir /data
      
      # mount -t nfs -o vers=3,noresvport 10.10.10.10:/filestorage /data
      
      # vi /etc/fstab
      (Add) 10.10.10.10:/filestorage /data nfs defaults,vers=3,_netdev,noresvport 0 0
      
Note
  • Supports NFS Version 3.

Windows Operating System (CIFS)

  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.

  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.

  3. On the File Storage List page, click the resource to be used by the connection server. Move to the File Storage Details page.

  4. Check the server in the Connection Server section and connect to it.

  5. Refer to the procedure below to connect (Network Drive Connection) the volume.

    • Right-click This PC in File Explorer and click Map Network Drive.
    • Enter the drive and folder based on the detailed information of the File Storage volume to be connected, and then click Finish.
    • To set up automatic connection at login, select Reconnect at sign-in.
  6. In the Network Credentials pop-up window, enter the account name (ID) and password, and then click OK.

    • The account name (ID) can be found on the File Storage Details page.
    • The password is the password set when Creating File Storage.
    • If you are connecting two or more volumes with the CIFS protocol set, add the Storage IP and Storage name to the hosts file and then connect.
    * Mount name
    \\10.10.10.10\filestorage1
    \\10.10.10.10\filestorage2
    
    * Hosts file contents added
    10.10.10.10 filestoragename1 #description
    10.10.10.10 filestoragename2 #description
    
    * Use the name written in the hosts file
    When connecting filestorage1: \\ filestoragename1\filestorage1
    When connecting filestorage2: \\ filestoragename2\filestorage2
    

Disconnecting from the Server (Umount, Network Drive Disconnection)

Connect to the server and perform the disconnection work (Umount, Network Drive Disconnection), and then release the connection server from the Console. Follow the procedure below.

Caution
If you release the connection server from the Console without performing the disconnection work (Umount, Network Drive Disconnection) on the server, a server status error (Hang) may occur. Be sure to perform the OS work first.

Linux Operating System (NFS)

  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.

  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.

  3. On the File Storage List page, click the resource to be released from the connection server. Move to the File Storage Details page.

  4. Check the server information in the Connection Server section and connect to the server.

  5. Refer to the commands listed below to perform the disconnection work (Umount).

    • Umount the volume
      # umount /data
      
      # vi /etc/fstab
      (Delete) 10.10.10.10:/filestorage /data nfs defaults,vers=3,_netdev,noresvport 0 0
      

Windows Operating System (CIFS)

  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.
  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.
  3. On the File Storage List page, click the resource to be released from the connection server. Move to the File Storage Details page.
  4. Check the server information in the Connection Server section and connect to the server.
  5. Refer to the procedure below to disconnect (Network Drive Disconnection) the volume.
    • Right-click the already connected Network Drive in File Explorer.

    • Select Disconnect Network Drive.

Note: I translated all Korean text to English while maintaining the original Markdown grammar and document format.

2.2.2 - Using Snapshots

You can create, delete, or restore snapshots of the created File Storage. You can perform these actions on the File Storage Details page and Snapshot List page.

Create Snapshot

You can create a snapshot of the current point in time immediately. To create a snapshot, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List page, click the resource to create a snapshot. File Storage Details page, you will be taken there.
  4. Click the Create Snapshot button. The Create Snapshot popup window opens.
  5. Confirm Click the button. It creates a snapshot.
  6. Click the Snapshot List button. Navigate to the File Storage Snapshot List page.
  7. Check the generated snapshot.
Caution
  • Snapshot charges are included in the File Storage usage fees.
  • When using replication or disk backup, you cannot recover with a snapshot, and you can only create a recovery volume.
Reference
  • Snapshot creation time is based on Asia/Seoul (GMT +09:00).
  • Snapshots can be created up to 800, and snapshots generated by schedule are not included. (Automatic creation via schedule is up to 128)
  • If you want to automatically create snapshots via schedule, set up snapshots on the File Storage Details page.
  • For detailed information about the snapshot schedule, see Edit Snapshot.

Recover Snapshot

File Storage volume can be restored to the latest snapshot in Available state. To restore the snapshot, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List On the page, click the resource to restore from snapshot. File Storage Details Navigate to the page.
  4. Click the Snapshot List button. It navigates to the File Storage Snapshot List page.
  5. Check the latest snapshot in Available state. The volume will be restored with that snapshot.
  6. Click the Snapshot Recovery button. The Snapshot Recovery popup opens.
  7. After checking the Snapshot name and creation date/time, click the Confirm button.
    • When recovery starts, it becomes Reverting, and when completed, it becomes Available.
Caution
  • If you want to recover using a snapshot that is not the latest snapshot, recovery is possible by creating a recovery volume.
  • When restoring, it is restored to the latest snapshot in Available state, and restoration is not possible in the following situations.
    • File Storage if the volume is not in Available state
    • If there are no recoverable snapshots
    • If the latest snapshot changes during recovery creation
    • If the latest snapshot is not in Available state

Create snapshot recovery volume

You can create a volume using a snapshot. To create a snapshot recovery volume, follow these steps.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List page, click the resource to restore from snapshot. Move to the File Storage Details page.
  4. Click the Snapshot List button. It navigates to the File Storage Snapshot List page.
  5. After checking Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to restore.
  6. Click Create recovery volume. The Create snapshot recovery volume popup opens.
  7. Click the Confirm button. You will be taken to the Create File Storage page.
  8. File Storage Creation page, enter the information required to create the service, and select detailed options.
    • Please enter the volume name and password.
    • The disk type and protocol are set the same as the original and cannot be modified.
      Category
      Required
      Detailed description
      Volume NameRequiredVolume Name
      • Start with a lowercase English letter and use lowercase letters, numbers, and the special character (_) to input 3 to 21 characters
      • Generated as ‘user input value + {6-character UUID composed of lowercase English letters and numbers}’
      • Cannot be modified after service creation
      Disk TypeRequiredSelect Disk Type
      • HDD: Standard Volume
      • SSD: High-performance Standard Volume
      • Cannot be modified after service creation
      • When creating a service via snapshot recovery volume creation, it is set identical to the original and cannot be modified
      ProtocolRequiredProtocol for sharing volumes over the network from the server
      • NFS: primarily used on Linux operating systems
      • CIFS: primarily used on Windows operating systems
      • Through snapshot recovery volume creation, it is set identical to the original when creating a service and cannot be modified
      Protocol > PasswordRequiredSet account password for volume access when using CIFS protocol
      • Enter 6~20 characters including letters, numbers and special characters (excluding $ % { } [ ] " \)
      Protocol > Password ConfirmationRequiredAccount Password Confirmation
      • Re-enter the password identically
      Recovery Snapshot NameOptionalName of the recovery snapshot used when creating a volume
      • Provide the recovery snapshot name when creating a service through snapshot recovery volume creation
      Table. File Storage Service Information Input Items
  9. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, check the created resource on the File Storage List page.

Delete Snapshot

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

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. Click the resource to delete the snapshot on the File Storage List page. It moves to the File Storage Details page.
  4. Click the Snapshot List button. It navigates to the File Storage Snapshot List page.
  5. After checking the Snapshot name and Creation date/time, click the More button of the snapshot you want to delete.
  6. Click the Delete button. The snapshot will be removed from the Snapshot List page.
Reference
  • Snapmirror files cannot be deleted when using replication.

2.2.3 - Restoring Files

You can restore data at the file level using the created snapshot. This task can be performed on the File Storage Details page.

Using File-Level Restoration

You can activate the file-level restoration feature and use it. After activating the feature, connect to the server and select and restore the data. To restore files, follow these steps:

  1. Click the All Services > Storage > File Storage menu. You will be taken to the Service Home page of File Storage.

  2. On the Service Home page, click the File Storage menu. You will be taken to the File Storage List page.

  3. On the File Storage List page, click the resource you want to restore. You will be taken to the File Storage Details page.

  4. Click the More button at the top right and then click the File-Level Restoration button. The File-Level Restoration popup window will open.

  5. Click the Confirm button. This will activate the file-level restoration feature.

    • While the file-level restoration is being activated, the File-Level Restoration button will be displayed as Deactivate File-Level Restoration.
  6. Check the server information in the Connected Server section and connect to the server.

  7. Refer to the following procedure to restore the data:

    • Connect to the server and check the mount name of File Storage.

    • Move to the snapshot location under the mount name.

    # cd /Mount_name/.snapshot/snapshot_name
    
    • In the snapshot location, check the file to be restored and restore it to the desired path.

Deactivating File-Level Restoration

After using the file-level restoration feature, you can deactivate it. To deactivate file-level restoration, follow these steps:

  1. Click the All Services > Storage > File Storage menu. You will be taken to the Service Home page of File Storage.
  2. On the Service Home page, click the File Storage menu. You will be taken to the File Storage List page.
  3. On the File Storage List page, click the resource you want to deactivate file-level restoration for. You will be taken to the File Storage Details page.
  4. Click the More button at the top right and then click the Deactivate File-Level Restoration button. The Deactivate File-Level Restoration popup window will open.
  5. Click the Confirm button. This will deactivate the file-level restoration feature.

2.2.4 - Using Disk Backup

After creating a backup of File Storage on a backup-dedicated HDD Storage, you can periodically store snapshots. You can perform tasks on the File Storage Details page and the Disk Backup page.

Caution
Backup copies created through Disk Backup can be restored using the File-level Restore feature. For detailed information about File-level Restore, see File-level Restore.
Guide
  • disk type is HDD or SSD only on the original disk backup is possible. Clones or high-performance SSD cannot be used.
  • Up to 2 backup copies can be created.

Create Disk Backup

You can create a backup volume on the original or another location’s backup-only HDD storage.

To create a backup volume, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Go to the File Storage list page.
  3. File Storage List On the page, click the resource to create a backup. File Storage Details Navigate to the page.
  4. Create Disk Backup Click the button. Create Disk Backup The popup window opens.
  5. After entering the backup information, click the Confirm button. It creates a backup copy of the HDD disk type.
    • Backup Location: Select the location where the backup will be created.
    • Backup frequency: Choose from 1 hour, daily, weekly, monthly. Replication will be performed at the next interval.
      • Daily: Daily 23:59:00
      • Weekly: Every Sunday 23:59:00
      • Monthly: 1st of each month 23:59:00
  6. Disk Backup page click. Disk Backup page moves.
  7. Disk Backup Check the information.
  • When selecting the volume name of the original or backup, you will be taken to the File Storage Details page of that volume.
Caution
When using disk backup, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, cancel the backup and recover with a snapshot.
Reference
  • A backup of HDD type is created regardless of the original disk type.
  • You can create 2 backups per volume, and data transfer fees are added when backing up across regions.

Modify Disk Backup Policy

You can change the backup status by modifying the backup policy. To modify the backup policy, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. Click the resource to modify the backup policy on the File Storage List page. You will be taken to the File Storage Details page.
  4. Disk Backup tab.
  5. Click the Edit button of the Backup Policy. The Disk Backup Policy Edit popup window opens.
    • Use: Performs backup. If Paused, can be modified to Use.
    • Pause: Temporarily pauses the backup. If use is the case, it can be edited to Pause.
    • Delete: Deletes the backup. If Paused, can be changed to Delete, and after deletion the backup cannot be used again.
  6. Check the modified backup policy on the Disk Backup page of File Storage.
Reference
Backup Policy, Backup Schedule can be modified in the backup copy when the backup status is Completed or Stopped.

Modify disk backup schedule

Through modifying the backup schedule, you can change the synchronization cycle between the original and the backup. To modify the backup schedule, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. On the Service Home page, click the File Storage menu. You will be taken to the File Storage List page.
  3. Click the resource to modify the backup cycle on the File Storage List page. Navigate to the File Storage Details page.
  4. Disk Backup Click the page.
  5. Click the Edit button of Backup Cycle. The Backup Cycle Edit popup window opens.
  6. Backup frequency: select from 1 hour, daily, weekly, monthly. Create snapshots at the next interval. * Daily: Daily 23:59:00 * Every week: Every Sunday 23:59:00 * Monthly: Monthly 1st 23:59:00
  7. Check the modified backup schedule on the Disk Backup page of File Storage.
Reference
Backup Policy, Backup Frequency can be modified in the backup copy when the backup status is Completed or Stopped.

Modify disk backup retention count

You can set the number of snapshots retained in the backup. To modify the backup retention count, follow these steps.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. Click the resource to modify the backup cycle on the File Storage List page. Navigate to the File Storage Details page.
  4. Disk Backup Click the page.
  5. Click the Edit button of Backup retention count. Edit Disk Backup Retention Count popup opens.
  6. Enter the backup retention count. * The number of stored items can be set from 1 to 128.
  7. Check the modified Backup Schedule on the Disk Backup tab of the File Storage Details page.

2.2.5 - Using Replication

You can create a replica of File Storage at another location and synchronize it periodically. You can perform tasks on the File Storage Details page and the Replication page.

Reference
  • kr-south region does not provide File Storage replication feature.

Create Clone

You can create a replica volume at a different location. To create a replica volume, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. Click the resource to create a replica on the File Storage List page. You will be taken to the File Storage Details page.
  4. Click the Create Clone button. The Create Clone popup opens.
  5. Enter Replication Location and Replication Volume Name, Password, Replication Interval, and click the Confirm button. It creates a replica with the same disk type.
    • Replication Location: Select a location different from the original File Storage volume.
  • Clone Volume Name: Start with a lowercase English letter and use lowercase letters, numbers, and the special character (_) to enter 3 to 21 characters.
    • Password: This is the account password for accessing CIFS volumes. Enter 6 to 20 characters including letters, numbers, and special characters (excluding $%{}[]"\).
    • Replication cycle: 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed at the selected interval.
      • Daily: Daily 23:59:00
      • Weekly: Every Sunday 23:59:00
      • Monthly: 1st of each month 23:59:00
  1. Click the Clone page. Navigate to the Clone page.
  2. Check the replication information.
  • When selecting the volume name of the original or replica, you will be taken to the volume’s File Storage Details page.
Caution
When using replication, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, delete the replication policy and recover with a snapshot.
Reference
  • When creating a replica, a replica with the same disk type and protocol is created.
  • One replica can be created per volume, and data transfer fees are added for cross-region replication.

Edit replication policy

Through modifying the replication policy, you can change the replication status. To modify the replication policy, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. On the File Storage List page, click the resource to modify the replication policy. You will be taken to the File Storage Details page.
  4. Click the Replication page. You will be taken to the File Storage Replication page.
  5. Click the Edit button of Replication Policy. The Edit Replication Policy popup window opens.
    • Use: Performs replication. If Pause, can be changed to Use.
    • Pause: Temporarily pauses replication. If use, it can be modified to Pause.
  • Delete: Deletes the replication. If Paused, it can be changed to Delete, and after deletion, replication cannot be used again.
  1. File Storage Replication on the page, please check the modified replication policy.
Caution
  • After deletion, the replica becomes the original, so you cannot replicate to the previous configuration again by modifying the replication policy.
  • Data stored only in the replica after pausing will be deleted if replication is used again.
  • When using replication policy, the replica is read only and data cannot be changed. Use replication after unmounting all connected resources.
Reference
  • If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule in the replica.

Modify replication cycle

Through modifying the replication cycle, you can change the synchronization cycle between the original and the replica. To modify the replication cycle, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List on the page, click the resource to modify the replication cycle. File Storage Details navigate to the page.
  4. Replication Click the page. File Storage Replication Navigate to the page.
  5. Click the Edit button of Replication Cycle. The Replication Cycle Edit popup opens.
    • Replication Cycle: Choose from 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed at the selected interval.
      • Daily: Daily 23:59:00
      • Weekly: Every Sunday 23:59:00
      • Monthly: 1st of each month 23:59:00
  6. Check the modified Replication Cycle on the File Storage Replication page.
Reference
  • If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule on the replica.

2.3 - API Reference

API Reference

2.4 - CLI Reference

CLI Reference

2.5 - Release Note

File Storage

2025.10.23
FEATURE Add disk type and provide ServiceWatch integration
  • SAP Account dedicated volume SSD SAP_E, SSD SAP_E disk type has been added.
    • If you use a SAP Account dedicated volume, when a failure occurs causing a failover, the LIF (storage mount IP) is automatically transferred.
    • Can only be used in SAP Account.
  • ServiceWatch service integration provision
    • You can monitor data through the ServiceWatch service.
2025.07.01
FEATURE Add disk type and disk backup feature
  • High-performance SSD disk type has been added, and can be used by connecting to a Multi-node GPU Cluster.
  • Disk Backup Through the function, you can store snapshots in backup-dedicated HDD Storage. You can select a location other than the original location.
2025.02.27
FEATURE Add disk type and replication, VPC Endpoint connection feature
  • File Storage feature change
    • SSD disk type has been added, allowing you to select the disk type according to the purpose.
    • Create the same replica volume at a different location, and you can set the data replication cycle.
    • Through a VPC Endpoint connection, you can use File Storage from an external network.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM and Service Home, tags, etc. reflected common CX changes.
2024.10.01
NEW File Storage Service Official Version Release
  • Because it automatically expands or shrinks based on usage, users can use the volume without capacity limits.
  • You can select the connection target through the access control function.
2024.07.02
NEW Beta version release
  • We have launched the File Storage service, a storage that allows multiple client servers to share files via network connection.

3 - Object Storage

3.1 - Overview

Service Overview

Object Storage is an object storage service that allows users to easily store and use their desired data, with URL-based access for very convenient data management. It enables search and retrieval of large-scale data, and provides features such as encryption and version management. It offers both Public and Private URLs, and Public URLs can be accessed even from the internet environment.

Key Features

  • S3 API Utilization: Easy and fast access from applications through Restful API, and compatible with Amazon S3, so it can be easily used in applications integrated with Amazon S3.
  • Secure Usage: Provides encryption (SSE-S3), access control, and Public/Private access features, making it suitable for safely storing user data or backup data for service recovery.
  • Cost Efficiency: Users do not need to pre-set bucket capacity, and storage space is provided with efficient pricing that charges based on actual usage.
  • Replication: Can perform replication to buckets in different locations or the same location. Multiple replication policies can be set, and if the original bucket cannot be used due to failure or disaster, the service can be provided through the replicated bucket.

Architecture Diagram

Architecture Diagram
Fig. Object Storage Architecture Diagram

Provided Features

Object Storage provides the following features.

  • Storage Management: Provides features for creating Object Storage, creating folders, deleting folders, uploading files, downloading files, and deleting files.
  • Version Management: When version management is used, all versions of uploaded files are managed. Previous files can be easily downloaded through the version list.
  • Encryption: When encryption is enabled, encryption is provided via SSE-S3 method.
  • Access Control: When access control is used, you can directly enter Public IPs allowed to access Object Storage, or select resources within the same Account allowed to access (Virtual Server, Bare Metal Server, VPC Endpoint, etc.).
  • Replication: Can perform replication to buckets in different locations or the same location.
    • Multiple replication policies can be set
  • Permission Management: By default, Private permission is provided, and Public permission and permission management features are provided.
    • Private Permission: Allows file sharing and downloading only to users who know the authentication key
    • Public Permission: Allows file sharing and downloading to anyone worldwide by accessing the file’s URL
  • Monitoring: Monitoring information such as total file count, data amount (Bytes), and HTTP Method request count can be checked through the Cloud Monitoring service.
  • ServiceWatch Service Integration: Data can be monitored through the ServiceWatch service.

Components

Authentication Key

The authentication key is an essential element that must be created in advance to use Object Storage.
The purpose of using the authentication key is as follows.

  • An authentication key is required to create and access the Object Storage service from Samsung Cloud Platform Console.
  • The API provided by Object Storage is compatible with Amazon S3, and tools using Amazon S3 can be used in the same way. In this case, authentication key input is required, and it is used as a tool to identify users with permissions. For detailed instructions on creating and checking authentication keys, see How-to guides > Create Authentication Key.

Bucket

A Bucket is the top-level folder, and all folders and files exist under the bucket. When you create Object Storage service in Samsung Cloud Platform Console, a bucket is created, and you can then upload folders or files.
Bucket naming rules are as follows:

  • Bucket names must be at least 3 characters and at most 63 characters.
  • Bucket names can only consist of lowercase letters, numbers, periods ., and hyphens -.
  • Bucket names must start with a lowercase letter or number.
  • Bucket names must not have two periods adjacent to each other.
  • Bucket names must not end with a period or hyphen.
  • Bucket names must not have periods and hyphens adjacent to each other.
  • Bucket names must not use IP address format (e.g., 192.168.x.x).
  • Bucket names cannot use the name admin.
  • Bucket names must be unique within an Account/Region.
  • Previously used bucket names can be reused after 1 hour.
Valid Bucket Name ExamplesInvalid Bucket Name Examples
Can be used with bucket names like
  • cpexamplebucket1
  • scp-example-bucket-01
  • my-scp-object-storage
Cannot be used with bucket names like
  • scp_example_bucket(includes underscore)
  • DocExampleBucket(includes uppercase)
  • -scp-example-bucket(starts with hyphen)

Folder

Folders are used to logically group files.
Folder naming rules are as follows:

  • Folder names can consist of Korean, English, numbers, and special characters.
  • Special characters that cannot be entered are as follows:
Special Characters Not Allowed in Folder Names
  • Percent sign%
  • Ampersand&
  • Question mark?
  • Exclamation mark!
  • Less than sign<, greater than sign>
  • Slash/
  • Equal sign=
  • Plus sign+
  • Dollar sign$
  • Pound sign#
  • Backtick
  • Caret^
  • Vertical bar/pipe|
  • Left curly brace{, right curly brace}
  • Left square bracket[, right square bracket]

File

A File refers to data stored in Object Storage and is the same as a regular file.
File naming rules are as follows:

  • File names can consist of Korean, English, numbers, and special characters.
  • Special characters that cannot be entered are as follows:
Special Characters Not Allowed in File Names
  • Percent sign%
  • Ampersand&
  • Question mark?
  • Exclamation mark!
  • Less than sign<, greater than sign>
  • Slash/
  • Equal sign=
  • Plus sign+
  • Dollar sign$
  • Pound sign#
  • Backslash\
  • Backtick
  • Caret^
  • Vertical bar/pipe|
  • Left curly brace{, right curly brace}
  • Left square bracket[, right square bracket]
  • Plus sign+

Folder names and file names are separated by a slash /. The following are examples of valid folder names and file names:

Examples of Mixed Folder and File Name Usage
  • 3scp-example
  • my.happy_photo-2024/20240101.jpg
  • video/2024/video01.wmv
Note
The path length including folder name, file name, and delimiter (/) is limited to 1,024 Bytes (based on UTF-8 Encoding).

URL

You can access Object Storage buckets through URLs. Public and Private URLs are provided, allowing access not only from the same Samsung Cloud Platform environment but also from external internet environments.
The URL structure is composed as follows:

URL Without Account IDURL With Account ID
https://[Representative URL]/[bucket name]/[folder name]/[file name]https://[Representative URL]/[accountId]:[bucket name]/[folder name]/[file name]
ComponentDescriptionExample
Representative URLThe Representative URL can be checked from the URL in Check Object Storage Detailed Information
  • Representative URL includes the region name.
-
accountIdaccount ID
  • If accessing files with Public Access enabled without authentication key (Access Key, Secret Key), account ID input is required; otherwise, access is possible without account ID.
c2ef8be0481d4094af3c6d046e536d25
bucket nameBucket name created by the userbucketname
folder nameFolder name where the file is locatedfolder/folder01/folder02/
file nameFile nameFilename02
Table. Object Storage URL Components

Complete URL information for files can be found in Check File Information.

Constraints

Constraints of Object Storage are as follows:

ComponentDescription
Number of creatable Object Storage servicesUp to 1,000 per region
File name length (including path)1,024 Bytes or less
File upload capacity
  • Console: 3GB or less per uploaded file
  • Upload API: 5GB for single upload operation, 5TB for Multipart
Number of files in bucketUp to 200 million
Table. Object Storage Constraints
Warning
  • It is recommended to store up to 200 million files in a bucket. If exceeding 200 million, severe performance degradation may occur, so manage the number of files.
  • When using S3 Backend Filesystem solutions (ex. s3fs, objectivefs, etc.), it is recommended not to use version management. Performance degradation may occur when using version management.
Note
When executing Amazon S3 API after changing IAM permissions, it may take up to 30 seconds.
Note
  • Korea South3 (kr-south3) region constraints
    • File upload and download functions through Samsung Cloud Platform Console are limited.
    • S3 API/CLI usage using Public URL is limited.
    • However, Private URL access through resources created in Samsung Cloud Platform Console (Virtual Server, etc.) is possible.
  • Korea South1 (kr-south1), Korea South2 (kr-south2) region constraints

Prerequisite Services

Object Storage has no prerequisite services.

3.1.1 - Amazon S3 Utilization Guide

Object Storage provides functions such as service creation, list retrieval, folder list retrieval, folder creation, file upload, download, etc., through the Samsung Cloud Platform Console. Additionally, these functions are also provided via an API compatible with Amazon S3. Therefore, tools that use Amazon S3 can be used in the same way.
To use Amazon S3’s utility, you need to create and verify an authentication key. For details, see Create Authentication Key.

Caution

When using the Amazon S3 utility, you must use the following version. If you use a different version, some features may be limited, so be careful.

  • SDK v2: 2.22.x or lower
  • SDK v1: 1.12.781 or less
  • CLI v2: 2.22.x or lower
  • CLI v1: 1.36.x or lower
  • SDK for JavaScript v3 : 3.728.0 or lower
  • SDK for Python(Boto3) : 1.35.x or lower

Amazon S3 API

The list of Amazon S3 APIs supported by Samsung Cloud Platform Object Storage service is as follows.

Reference
For detailed information about the Amazon S3 API, please refer to Amazon S3 API Guide.
CategoryDetailed description
head-bucketBucket Information Lookup
list-bucketsList bucket
get-bucket-versioningBucket versioning query
put-bucket-versioningModify bucket versioning
get-bucket-encryptionBucket encryption settings query
put-bucket-encryptionApply bucket encryption settings
delete-bucket-encryptionDelete bucket encryption setting
copy-objectObject copy, move, rename
put-objectCreate object
get-objectObject download
list-objectsObject list query
head-objectObject detailed view
get-object-aclObject ACL query
delete-objectDelete Object
  • If versioning is enabled, deleting a file adds a Delete Marker to the file and the Delete Marker becomes the latest version
  • If permanent deletion of a file is required, delete by specifying the version ID
list-object-versionsObject version list query
delete-objectDelete object version
presignPUT object Presigned URL issuance
get-bucket-aclBucket public permission check
create-bucketCreate bucket
delete-bucketDelete bucket
get-bucket-corsBucket CORS (Cross OriginResources) configuration check
put-bucket-corsCreate bucket CORS (PUT)
delete-bucket-corsBucket CORS Delete
put-bucket-taggingBucket tagging creation
get-bucket-taggingBucket tagging query
delete-bucket-taggingDelete bucket tagging
put-bucket-websiteCreate bucket website
get-bucket-websitebucket website view
delete-bucket-websiteDelete bucket website
get-bucket-policy-statusBucket policy status query
put-bucket-aclCreate bucket ACL
create-multipart-uploadMultipart upload creation
upload-partMultipart upload execution
complete-multipart-uploadMultipart upload completed
list-multipart-uploadsMultipart upload list
abort-multipart-uploadDelete incomplete multipart upload
put-object-taggingObject tagging creation
get-object-taggingObject tagging query
delete-object-taggingObject tagging Delete
list-objects-V2Object query (v2)
put-object-aclObject acl creation
list-partsParts lookup
put-public-access-blockPublic access block creation
get-public-access-blockpublic access block lookup
delete-public-access-blockpublic access block delete
put-bucket-lifecycleCreate bucket lifecycle (only Expiration rule can be used)
get-bucket-lifecycleBucket Lifecycle Query
delete-bucket-lifecycleBucket Lifecycle Delete
put-bucket-replicationModify bucket replication policy
  • When using replication-configuration, the following items need to be checked
    • Role: IAM SRN input required
    • Rules > Destination’s Bucket: Bucket SRN input required
    • If Rule ID is not entered, it is automatically generated with a random value
    • Rule Priority is not applied, so any entered value has no effect (can set all to 1)
    • When changing Rule ID, a new policy is created (the existing policy is deleted)
get-bucket-replicationGet bucket replication policy
delete-bucket-replicationDelete bucket replication policy
Table. List of Amazon S3 supported APIs

Amazon S3 CLI

To use Amazon S3 with the AWS CLI, please refer to Amazon S3 CLI Guide.

Amazon S3 SDK for Java

To use the Amazon S3 SDK for Java, please refer to Amazon S3 SDK Guide.

Note
For SDK guides and Rest API guides for other languages, please check the AWS official website.
Note
  • For using the Amazon S3 SDK, refer to the required region parameter below.
    • Korea West (kr-west1) case: kr-west
    • Korea South 1,2,3(kr-south1,2,3) case: kr-south
  • region parameter is for reference only, and the actual region is distinguished based on the URL.
Note
  • South Korea South 3 (kr-south3) region constraints
    • Samsung Cloud Platform Console through file upload and download functionality is limited.
    • Use of S3 API/CLI via Public URL is restricted.
    • However, access to Private URLs through resources (such as Virtual Server) created in the Samsung Cloud Platform Console is possible.
  • South Korea South1 (kr-south1), South Korea South2 (kr-south2) region constraints

3.1.2 - Monitoring Metrics

Object Storage Monitoring Metrics

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

Metric NameDescriptionUnit
ObjectsNumber of objects stored in a bucketcnt
Bucket UsedAmount of data stored in a bucket (bytes)bytes
Requests [Upload Avg]Average upload usage per bucketbytes
Requests [Download Avg]Average download usage per bucketbytes
Requests [Total]Total number of HTTP requests executed on a bucketcnt
Requests [Get]Number of HTTP GET requests executed on objects in a bucketcnt
Requests [Head]Number of HTTP HEAD requests executed on objects in a bucketcnt
Requests [List]Number of LIST requests executed on objects in a bucketcnt
Requests [Post]Number of HTTP POST requests executed on objects in a bucketcnt
Requests [Put]Number of HTTP PUT requests executed on objects in a bucketcnt
Requests [Delete]Number of HTTP DELETE requests executed on objects in a bucketcnt
Table. Object Storage Monitoring Metrics

3.1.3 - ServiceWatch metric

Object Storage sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at a 1-minute interval.

Reference
To check metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Indicators

The following are the basic metrics for the namespace Object Storage.

Performance ItemDetailed DescriptionUnitMeaningful Statistics
Table. Object Storage Basic Metrics

3.2 - How-to guides

The user can enter the required information for Object Storage through the Samsung Cloud Platform Console, select detailed options, and create the service.

Creating an access key

To create and use the Object Storage service in the Samsung Cloud Platform Console, you need to generate an authentication key in advance.

Authentication key creation can be done from My Menu > My Info. > Authentication Key Management > Create Authentication Key. For more details, see IAM > Create Authentication Key.

Reference
  • The authentication key (Access Key, Secret Key) is used when authenticating Amazon S3 utility.
  • The authentication key is used not only for Object Storage, but also for authentication in OpenAPI and CLI.
  • Up to 2 authentication keys can be generated.
Caution
  • If the authentication key expires, access rights to the Object Storage service will be restricted. To ensure smooth service usage, check the authentication key’s expiration period in advance.
  • If you disable the authentication key, access rights to the Object Storage service will be restricted.

Object Storage Create

You can create and use the Object Storage service in the Samsung Cloud Platform Console.

To create Object Storage, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Service Home on the page click the Create Object Storage button. Navigate to the Create Object Storage page.
  3. Object Storage creation Enter the information required to create the service on the page.
    Category
    Required
    Detailed description
    Bucket NameRequiredBucket name created by the user
    • Starts with a lowercase English letter or digit, and using lowercase English letters, digits, hyphen-, period., input 3~63 characters
    • Period. cannot appear consecutively two or more times.
    • Period. and hyphen- cannot be adjacent.
    • Cannot end with a period. or hyphen-.
    • IP format not allowed
    • admin name not allowed
    Table. Object Storage Required Information Input Items
Caution
In the Archive Storage service, if you create with the bucket name that is being used as the Archiving target, be careful as the configured Archiving policy will be applied.
  1. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, check the created resources on the Object Storage List page.

Object Storage Check Detailed Information

Object Storage service can view and edit the full resource list and detailed information.
Object Storage Details page consists of Details, Folder List, Tag tabs.

To view detailed information of the Object Storage service, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage List page.
  3. Object Storage List page, click the resource to view detailed information. Navigate to the Object Storage Details page.
    • Object Storage Details page displays status information and additional feature information, and consists of Details, Folder List, Replication, Tag tabs.
      CategoryDetailed description
      Bucket statusBucket status
      • Active: Available state
      Service cancellationButton to cancel the service
      Table. Status Information and Additional Functions
Note
Object Storage resources do not support operation history.
If necessary, please check via the Logging&Audit service. For more details, see Logging & Auddit > How-to Guides.

Detailed Information

Object Storage list page, you can view the detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the Object Storage service, it refers to a bucket SRN
Resource NameResource Name
  • In Object Storage service, it refers to the bucket name
Resource IDUnique resource ID in the service
Bucket NameBucket name created by the user
CategoryField that distinguishes original or replica
  • Currently only the original exists, and a replica will be added when the DR feature is introduced later
UsageTotal data usage of the bucket
EncryptionEncryption usage information
  • When encryption is used, SSE‑S3 encryption key method and AES256 encryption algorithm are applied
  • Encryption settings can be configured on the Object Storage Details page after creating Object Storage
Version ManagementVersion Management Usage Information
  • If settings for version management are required, click the Edit button
URLProvides Public and Private addresses so that Object Storage can be accessed via URL
  • Public: Provided to allow access from external networks
  • Private: Provides an address accessible from resources created within the same Account in the Samsung Cloud Platform Console
Access ControlWhen access control is used, you can control it so that only authorized resources can access the bucket
  • After switching to use access control, you must click the Edit button to add resources to be allowed for each access
    • Public IP Allow: Add as a single IP/CIDR
    • Service Resource Allow: Select service resources created in the same Account/Region
    • Cloud Functions Service: Set whether the service is used
Table. Object Storage Detailed Information Tab Items

Folder List

Through the folder list tab, you can view the list of folders and files stored in the bucket.

CategoryDetailed description
NameFile name or folder name
SizeFile size
Modification Date and TimeThe date and time the file was most recently modified
Additional Features > MoreFile, Folder Management Buttons
  • File Information: View additional information of the file
  • File Copy: Copy the selected file
    • For detailed information on copying files, refer to Copy File.
  • Permission Edit: Set Public Access permission for the file
  • Version List: If versioning is enabled, view the version list
  • Download: Download the selected file
    • For detailed information on downloading files, refer to Download File.
  • Create Presigned URL: Allows file download using a Presigned URL for a set period
    • Enter the required time (1~720 minutes) and click the Confirm button to generate.
  • Delete: Delete the selected file or folder
    • For folders, only deletion is possible.
New FolderAdd new folder
File UploadUpload a new file or a file in progress
  • For detailed information about file upload, see Upload File
DeleteDelete file or folder
  • Activate Delete button when multiple files are selected
  • Deletion possible when single/multiple folders are selected
  • Deletion possible when single/multiple files are selected
  • Deletion possible when multiple files and folders are selected
DownloadFile download
  • Download only possible when a single file is selected
  • Button disabled when a folder is selected
  • Button disabled when multiple files are selected
  • Button disabled when multiple files and folders are selected
Table. Folder List Tab Items
Reference
  • Korea South 3 (kr-south3) region constraints
    • The file upload and download functionality via the Samsung Cloud Platform Console is limited.
    • Use of S3 API/CLI via Public URL is restricted.
    • However, accessing Private URLs through resources (such as Virtual Server) created in the Samsung Cloud Platform Console is possible.
  • Korea South 1 (kr-south1), Korea South 2 (kr-south2) region constraints
  • If delete marker is the latest version, it cannot be seen in the folder list.
  • delete marker version cannot be found in the version list.

Replication

Object Storage list You can view and manage the replication information of the selected resource on the page.

CategoryDetailed description
Policy NameName of the replication policy
  • Enter up to 255 characters, including English letters, numbers, and special characters (-,.)
Replication targetReplication target bucket name
Replication locationReplication location (region)
Target fileReplication target file list
StateReplication policy status
  • Active: Active
  • Inactive: Inactive
AddAdd new replication policy
MorePolicy management possible
  • **Disable**: Disable the policy (display as enabled when disabled)
  • **Edit**: Can edit replication target, target files, and options of the replication policy
    • For details on editing replication policies, see [Edit Replication Policy](/userguide/storage/object_storage/how_to_guides/obj_policy.md#복제-정책-수정하기)
  • **Delete**: Delete the policy
    • For details on deleting replication policies, see [Delete Replication Policy](/userguide/storage/object_storage/how_to_guides/obj_policy.md#복제-정책-삭제하기)
Table. Object Storage Replication Information Tab Items

Tag

Object Storage List page, you can view the tag information of the selected resource, and you can add, modify, or delete it.

CategoryDetailed description
Tag ListTag List
  • Tag’s Key and Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the existing list of Keys and Values
Table. Object Storage Tag Tab Items

Work History

Reference
Object Storage resources do not support operation history.
If needed, please check via the Logging&Audit service. For more details, see Logging&Auddit > How-to Guides.

Object Storage Encryption Setup

You can set it to encrypt the data stored in the bucket. After setting bucket encryption, the encryption setting is applied to uploaded data. When using encryption, the SSE‑S3 encryption key method and the AES256 encryption algorithm are applied.

Reference
Object Storage bucket encryption can provide two types (SSE‑S3/SSE‑KMS). SSE‑S3 is server‑side encryption (SSE‑S3) using Amazon S3 managed keys. SSE‑KMS is server‑side encryption (SSE‑KMS) using Key Management Service (KMS) keys.
In this service, server‑side encryption (SSE‑S3) using Amazon S3 managed keys is released as the default method, and server‑side encryption (SSE‑KMS) using Key Management Service (KMS) keys will be provided later according to the service roadmap.

Information

If there is data saved before bucket encryption was set, the encryption settings will not be applied.

  • If you re-upload the file, encryption will be applied.
  • To set encryption for existing data, you need to re-upload it.

Object Storage Follow the steps below to use bucket encryption.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage List page.
  3. Object Storage List page, click the resource (bucket) to use encryption. Object Storage Details page will be opened.
  4. On the Object Storage Detailed page, check if encryption is not used.
  5. If Encryption is Not Used, click the Edit button.Encryption Edit Popup opens.
  6. After checking Encryption Use, click the Confirm button.

Object Storage Cancel

You can cancel unused Object Storage to reduce operating costs. However, if you cancel the service, the running service may be immediately stopped, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
  • Service termination is possible for buckets with no stored data.
  • If a file is being uploaded, the upload will be canceled.
  • Please be careful as data cannot be recovered after deletion.

If you want to cancel Object Storage, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage list page.
  3. Object Storage list on the page, select the resource (bucket) to cancel, and click the Cancel Service button.
  4. Please enter bucket name to confirm termination.
  5. If you have entered the Bucket Name correctly, the Confirm button will be activated. Click the Confirm button.
  6. When termination is complete, check whether the resource has been terminated on the Object Storage List page.