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
      Snapshot CreationCreate a snapshot at a specific point in time
      Service terminationButton to cancel the service
      Table. Status Information and Additional Functions
Reference
In the case of a recovery copy, snapshot list, replication tabs are not displayed.

Detailed Information

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

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

Snapshot List

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

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

Replication

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

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

Tag

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

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

Work History

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

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

Block Storage(BM) Resource Management

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

Edit Volume Name

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

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

Modify Snapshot Capacity

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

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

Edit Snapshot Schedule

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

  1. All Services > Storage > Block Storage(BM) menu, click it. Navigate to the Service Home page of Block Storage(BM).
  2. Service Home page에서 Block Storage(BM) 메뉴를 클릭하세요. Block Storage(BM) 목록 페이지로 이동합니다.
  3. Block Storage(BM) List on the page, click the resource to edit the snapshot schedule. Block Storage(BM) Details page will be opened.
  4. Click the Snapshot Schedule Edit button. The Snapshot Schedule Edit popup opens.
  5. Set the snapshot auto generation status and generation interval, and click the Confirm button.
    • Creation Cycle based, if you want to automatically create snapshots, select Auto Creation as Enabled.
    • Generation cycle can be selected daily, hourly, or weekly, day of week, hourly.
Caution
Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically created via schedule), and if the maximum number is exceeded, no more snapshots can be created.
Note
  • The snapshot schedule is based on Asia/Seoul (GMT +09:00).
  • After setting snapshot capacity, schedule registration is possible.
  • When setting a snapshot schedule, it cannot be added to the Volume Group.

Modify IOPS

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

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

Throughput Edit

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

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

Edit Connection Server

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

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

Block Storage(BM) Cancel

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

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

To cancel Block Storage, follow the steps below.

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

1.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. Target Volume에 추가된 볼륨의 Volume Name을 클릭하세요. Block Storage(BM) Detail 페이지로 이동합니다. -> 4. Click the Volume Name of the volume added to the Target Volume. It moves to the Block Storage(BM) Detail page.
  5. connected server item has a server added, after server connection, perform disconnect work (Umount, Disk Offline) please.
  1. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
  2. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to restore.
  3. Restore button, click. Snapshot restore popup window opens.
  4. Snapshot name and Creation time are confirmed after clicking the Confirm button. The target volumes are restored as snapshots.
  5. Detailed Information button will be clicked. It will move to the Volume Group(BM) Detail page.
  6. Target Volume에 추가된 볼륨의 Volume Name을 클릭하세요. Block Storage(BM) Detail 페이지로 이동합니다.
  7. connected server items have been added, after server connection, perform connection work (Mount, Disk Online)
Caution
  • Snapshot recovery must be performed with all target volumes disconnected (Umount, Disk Offline) from the connected server, and the recovered volume can be used after reconnection (Mount, Disk Online).
  • After the snapshot restoration is complete, all snapshots created after the snapshot used for restoration will be deleted.

Creating a recovery version

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

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click on the resource to create a backup. It moves to the Volume Group(BM) details page.
  4. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
  5. Snapshot name and Creation time are confirmed, then click the More button of the snapshot you want to create a restore from.
  6. Restore Point Creation button should be clicked. Snapshot restore point creation popup window will be opened.
  7. Prefix를 입력한 후, 확인 버튼을 클릭하세요. becomes 9. Enter the Prefix and then click the Confirm button. 복구본 생성을 알리는 팝업창이 열립니다. becomes A pop-up window announcing the creation of a backup will open. So the translation is: 9. Enter the Prefix and then click the Confirm button. A pop-up window announcing the creation of a backup will open.
  • The name of the backup is created with the input prefix value + original Block Storage name entered.
  1. Confirm button will be clicked. The application for creating a backup copy will be completed.
Caution
  • A backup copy can be created only one per original.
  • The recovery volume is a separate volume created with the same capacity as the original, and additional costs are incurred.

Deleting a snapshot

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

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

Volume Group(BM) replication usage

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

Create a copy

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

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

Modify replication policy

You can change the replication status through replication policy modification.

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

To modify the replication policy, follow the following procedure.

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

Modify Replication Cycle

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

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

To modify the replication cycle, follow the following procedure.

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

Volume Group(BM) cancellation

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

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

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
    Create Disk BackupCreate 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
    Create SnapshotImmediately create a snapshot at the time of creation
    More > Snapshot RecoveryRecover volume with the latest snapshot in Available state
    More > File-level RestoreEnable file-level restore function within snapshots
    More > Disable file-level restoreDisable file-level restore function within snapshotsDisable file-level restore Reference
    Service CancellationButton 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
Snapshot > Retention CountSnapshot 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
Connected ResourcesConnected 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
VPC EndpointConnected 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
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
Backup statusBackup progress status according to policy settings
Backup retention countNumber of snapshots retained in the backup
Volume InformationOriginal 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. Service Home 페이지에서 File Storage 메뉴를 클릭하세요. File Storage List 페이지로 이동합니다.
  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. Backup CycleEdit 버튼을 클릭하세요. Backup Cycle Edit 팝업창이 열립니다.
  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 -

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

3.2.1 - Access Control

If you set bucket access control to enabled, only resources that are allowed access can access the bucket. You can set it to allow access by entering a public IP or for resources created in the Samsung Cloud Platform Console.

Set up access control

You can set bucket access control to enabled.

Object Storage Follow the steps below to set up access control.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage list page.
  3. Click the resource (bucket) to set access control on the Object Storage List page. It navigates to the Object Storage Details page.
  4. Verify that Access Control is Unused on the Object Storage Details page.
  5. Click the Edit button if Access Control is Unused. The Edit Access Control popup opens.
  6. After checking Access Control Use, click the Confirm button. On the Object Storage Details page, Access Control will be changed to Use.
Notice
If you change the access control to use, you can set the access control for Public UP, service resources, and Cloud Functions services.
  1. Public IP, Register service resources to allow access, or set whether to use access control for the Cloud Functions service.
CategoryDetailed description
Public IP AllowAdd registered Public IP or CIDR
  • Example: 192.168.x.x, 192.168.x.x/24
Allow Service ResourcesSelect service resources created in the same Account/Region
  • Service: Service Name
    • Example: Virutal Server, GPU Server, Bare Metal Server, Multi-node GPU Cluster, VPC Endpoint, PostgreSQL, MariaDB, MySQL, EPAS, Microsoft SQL Server
  • Resource Name: Name of the service resource
Allow Cloud Functions serviceSetting whether to allow Object Storage access to modify Java Runtime code in Cloud Functions service
  • Allowed when set, Cloud Functions service can load Java Runtime executable files stored in Object Storage
Table. Access Control Items
Reference
If you modify the access permission, it may take up to 30 seconds for the changes to be completed.
Reference

South Korea (kr-south) region constraints

  • South Korea (kr-south) region does not provide Cloud Functions service, so the Cloud Functions Service Allowance feature cannot be used.

Allow Public IP Access

If bucket access control is set to enabled, you can add a public IP allowance.

Object Storage in to add Public IP access permission, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Service Home page will be navigated to.
  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 set access control. Navigate to the Object Storage Details page.
  4. Object Storage Details page, check if access control is enabled.
    • If Access control is unused, click the Edit button, then in the Access control popup change access control to Enabled.
    • Only when access control is enabled, the Allow IP Access, Allow Service Resources, Allow Cloud Functions Service list is displayed.
  5. Public IP Allow in Edit click the button. Public IP Allow Edit The popup window opens.
  6. Enter the Public IP to allow access, and click the Add button.
    ColumnRequiredDetailed description
    Public IP AllowedRequiredEnter as a single IP or CIDR format (up to 150 entries)
    • 192.168.x.x (IP format)
    • 192.168.x.x/24 (CIDR format)
    Table. Public IP Allowance Edit Popup Input Items
  7. Check the items added to the list and press the Confirm button.
  8. Check the added Public IP in the Object Storage Details page’s Access Control > Allow Public IP list.
Reference
  • If you modify the Public IP allowance, it may take up to 30 seconds for the changes to be completed.
  • Public IPs are allowed up to a maximum of 150.

Allow access to service resources

If bucket access control is set to enabled, you can add service resources in the allowed service resources.

Object Storage Follow the steps below to allow access to service resources.

  1. Click the All Services > Storage > Object Storage menu. Go to the Service Home page.
  2. Service Home page, click the Object Storage menu. Navigate to the Object Storage list page.
  3. Object Storage List page, click the resource (bucket) to set access control. Object Storage Details page navigate.
  4. Object Storage Details on the page, check whether Access Control is enabled.
    • Access control is unused, click the Edit button, then in the Access control popup change access control to Enabled.
    • Only when access control is enabled, the IP access allowed, service resource allowed, Cloud Functions service allowed list is displayed.
  5. Click the Edit button in Allow Service Resources. The Select Service Resources popup opens.
Notice
  • The allowed criteria per service are as follows.

    • Virtual Server/GPU Server/Bare Metal Server/Multi-node GPU Cluster: Allowed per server
    • VPC Endpoint: Allow per VPC Endpoint
    • PostgreSQL, MariaDB, MySQL, EPAS, Microsoft SQL Server: Allowed per cluster
  • To access Object Storage from the server, the following tasks are required.

    1. Verify Object Storage IP via nslookup command on the server
    2. Register rule through Security Group or Firewall service and apply to server
      • Target address: Object Storage IP confirmed in ①
      • Direction : Outbound
      • Service : TCP 80, 443 (80 when using http / 443 when using https)
Caution

If each service’s status is as follows, permission and revocation of service resource access are possible. If it is not the following status, previously permitted service resources may also be affected.

  • Virtual Server/GPU Server: Build, Building, Networking, Scheduling, Block_Device_Mapping, Spawning, Deleting, Error and other statuses
  • Bare Metal Server/Multi-node GPU Cluster: Running, Starting, Stopping, Stopped
  • VPC Endpoint: Active
  • PostgreSQL/MariaDB/MySQL/EPAS/Microsoft SQL Server: Running
  1. Select the server to allow access, and press the Confirm button.
  2. Check the added server in the Object Storage Details page’s Access Control > Service Resource Allow list.
Reference
  • Modifying service resource permissions may take up to 30 seconds for changes to be completed.
  • Up to 150 service resources are allowed.

Cloud Functions Allow Service Access

If access control on the bucket is set to enabled, you can allow the Cloud Functions service to access Object Storage.

To allow access to the Cloud Functions service from Object Storage, follow these steps.

  1. All Services > Storage > Object Storage Click the menu. Service Home page will be displayed.
  2. Click the Object Storage menu on the Service Home page. You will be taken to the Object Storage list page.
  3. Object Storage List On the page, click the resource (bucket) to set access control. Object Storage Details Navigate to the page.
  4. Object Storage Details page, check if access control is enabled.
    • If Access Control is Disabled, click the Edit button, then in the Access Control popup change Access Control to Enabled.
    • Only when access control is enabled, the list of Allow IP Access, Allow Service Resources, Allow Cloud Functions Service is displayed.
  5. Click the Edit button in Cloud Functions Service Allow. The Cloud Functions Service Edit popup opens.
  6. After checking Allow, click the Confirm button.
Reference
  • When the access permission setting for the Cloud Functions service is completed, the Cloud Functions service can retrieve the Java Runtime executable stored in Object Storage.
  • For loading the Java Runtime executable in the Cloud Functions service, refer to Change Java Runtime code.
Reference

South Korea (kr-south) region constraints

  • The South Korea (kr-south) region does not provide Cloud Funtions service, so the Allow Cloud Functions Service feature cannot be used.

3.2.2 - File and Folder Management

If you need to manage, such as saving files to the created Object Storage or downloading saved files, you can perform tasks on the Object Storage Details and Folder List pages.

Create new folder

A new folder may need to be created to store new data in the bucket.

Object Storage Follow the steps below to create a new folder.

  1. All Services > Storage > Object Storage Click the menu. Service Home page will be displayed.
  2. Click the Object Storage menu on the Service Home page. It navigates to the Object Storage list page.
  3. Object Storage List page, click the resource (bucket) to create a new folder. You will be taken to the Object Storage Details page.
  4. Folder List Click the tab. Folder List Navigate to the page.
  5. Click the New Folder button. New Folder popup window opens.
  6. Enter the folder name to use, and click the Confirm button. A popup window notifying the creation of a new folder will open.
Caution
  • Folder names must not contain special characters that are not allowed. For more details, see Folder Name Creation Rules.
  • The total path length, including folder name, file name, and delimiter (/), is limited to within 1,024 Bytes (based on UTF-8 encoding).
  1. After clicking the Confirm button, check the created folder in the Folder List.

File Upload

Reference
  • Korea South 3 (kr-south3) region constraints
    • The file upload and download functionality through the Samsung Cloud Platform Console is limited.
    • Using S3 API/CLI via Public URL is restricted.
  • However, accessing a Private URL through resources (such as Virtual Server) created in the Samsung Cloud Platform Console is possible.
  • Korea South1 (kr-south1), Korea South2 (kr-south2) region constraints

You can upload a new file or a file you are working on to the bucket. Object Storage Follow the steps below to upload files.

  1. Click All Services > Storage > Object Storage menu. Go to the Service Home page.
  2. Click the Object Storage menu on the Service Home page. You will be taken to the Object Storage list page.
  3. Object Storage List On the page, click the resource (bucket) to upload files. Object Storage Details Navigate to the page.
  4. Click the Folder List tab. You will be taken to the Folder List page.
  5. File Upload Click the button. File Upload The popup window opens.
  6. After clicking the File Attachment button, select the file to upload or drag the file to attach into the popup window.
Caution
  • You can upload up to 3 files, each up to 3 GB.
  • The attached file name must not contain prohibited special characters. For more details, refer to File Name Creation Rules.
  • The total path length, including folder name, file name, and delimiter (/), is limited to within 1,024 Bytes (based on UTF-8 encoding).
  • If there are duplicate files, you cannot upload.
  1. If you have selected all files, click the Upload button.
  2. If the upload was successful, check the file in the folder list.

File Download

Reference
  • Korea South 3(kr-south3) region constraints
    • File upload and download functions via Samsung Cloud Platform Console are restricted.
    • 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.
  • Korea South1 (kr-south1), Korea South2 (kr-south2) region constraints

You can download files stored in the bucket. Object Storage Follow the steps below to download the file.

  1. Click the All Services > Storage > Object Storage menu. You will be taken to the Service Home page.
  2. Click the Object Storage menu on the Service Home page. Go to the Object Storage list page.
  3. Object Storage List page, click the resource (bucket) to download. Object Storage Details page will be opened.
  4. Click the Folder List tab. You will be taken to the Folder List page.
  5. Click the More > Download button located at the far right end of the file to be downloaded. The file download will start.
  6. Check that the file download has completed in the browser.

View file information

You can retrieve information about files stored in the bucket. Object Storage Follow the steps below to view file information.

  1. All Services > Storage > Object Storage Click the menu. Service Home page will be opened.
  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) that contains the file you want to view file information. Object Storage detail page will be opened.
  4. Folder List Click the tab. Folder List Navigate to the page.
  5. Click the More > File Info button located at the far right of the file to view information. File Info popup window opens.
  6. File Information Check detailed file information in the popup window.
    CategoryDetailed description
    file namefile name
    Content typeObject type
    Total sizeFile size
    Modification Date/TimeThe date and time the file was most recently modified
    PermissionPublic Access allowance
    URLProvide Public and Private addresses to access the file path URL
    • Public: Provided to be accessible from external internet network
    • Private: Provides an address accessible from resources created in the same Account and same region of the Samsung Cloud Platform Console
    Table. File Information Items

Copy file

You can copy the file stored in the bucket to the same location. To copy a file, follow these steps.

  1. Click the Storage > Object Storage menu. Go to the Object Storage list page.
  2. Object Storage List On the page, click the resource (bucket) to copy the file. Object Storage Details Navigate to the page.
  3. Folder List Click the tab. Folder List Navigate to the page.
  4. Click the More > File Copy button at the far right of the file to be copied. The File Copy popup window opens.
  5. After entering the filename, click the Confirm button. A popup notifying file copy will open.
Caution
  • Only files with a full path length (including bucket name, folder name, file name, delimiter (/)) of 1,024 Bytes or less (based on URL Encoding) can be copied.
  • In the Samsung Cloud Platform Console, you can only copy files when the file size is 5 GB or less. If the file size exceeds 5 GB, you can copy using the S3 API.
  • You can copy within the same bucket and folder.
  • If the bucket does not use versioning, files with the same name in the folder will be overwritten.
  1. After clicking the Confirm button, check the copied file in the Folder List.

Delete files and folders

You can delete files and folders stored in the bucket. Object Storage Follow the steps below to delete files and folders.

Caution
  • When deleting a folder, all subfolders/files inside the folder will be deleted.
  • All versions will be deleted at once when the file is deleted.
  1. All Services > Storage > Object Storage Click the menu. Service Home page will be opened.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage list page.
  3. Click the resource (bucket) that contains the file or folder to delete on the Object Storage list page. It moves to the Object Storage details page.
  4. Folder List tab, click it. Folder List page, navigate.
  5. Click the More > Delete button located at the far right of the file or folder to be deleted. The Delete popup window will open.
    • After selecting multiple files or folders from the left check box, you can click the Delete button at the top to delete multiple files or folders at once.
  6. Click the Confirm button in the delete popup to complete the deletion.
  7. Folder List Check that files or folders have been deleted from the list.
Reference
When deleting multiple files and folders simultaneously, it may take a long time.

3.2.3 - Permission Management

Each file is provided with Private permission by default, and each file can be changed to Public permission through permission settings. Private permission allows file disclosure and download only to users who know the Access Key and Secret Key, but Public permission allows file disclosure and download to anyone worldwide when accessing the file’s Public URL, so caution is required.

Check permission management

You can check the permission settings on the file.

Object Storage Follow the steps below to check file permissions.

  1. All Services > Storage > Object Storage Click the menu. Service Home Navigate to the page.
  2. Service Home on the page, click the Object Storage menu. Go to the Object Storage list page.
  3. Object Storage list page, click the resource (bucket) that contains the file whose permissions you want to check. Object Storage details page will be opened.
  4. Folder List Click the tab. Folder List Navigate to the page.
  5. Click the More > File Info button located at the far right of the file you want to view file information. The File Info popup window opens.
  6. File Information in the popup window Permissions please check.
    CategoryDetailed description
    PermissionPublic Access allowed or Public Access not allowed
    Table. Permission Information Description

Public Access Allow

You can set the file’s Public Access permission to allow. Object Storage Follow the steps below to set file permissions to allow Public Access.

  1. All Services > Storage > Object Storage Click the menu. Service Home Navigate to the page.
  2. Service Home on the page, click the Object Storage menu. Go to the Object Storage list page.
  3. On the Object Storage List page, click the resource (bucket) that has files to allow Public Access. You will be taken to the Object Storage Details page.
  4. Folder List Click the tab. Folder List Navigate to the page.
  5. Click the More > File Info button located at the far right of the file you want to view file information for. The File Info popup window opens.
  6. Check that Permission is in Public Access not allowed state, and click the Confirm button.
  7. Click the More > Permission Management button located at the right end of the file. The Edit Permission Management popup window opens.
  8. Edit Permission Management In the popup, check Allow Public Access for Permission Management, and click the Confirm button. Navigate to the Folder List page.
  9. Click the More > File Info button located at the far right of the file. The File Info popup window opens.
  10. Permission is Public Access allowed. Check the state.
Notice
When Public Access is allowed, accessing the file’s Public URL allows the file to be publicly disclosed and downloaded by anyone worldwide.
Please set it only if file disclosure is absolutely necessary.

3.2.4 - Replication Policy Management

You can perform replication to a bucket in a different location or the same location.
You can set multiple replication policies, and if the original bucket is unavailable due to a failure or disaster, you can provide service through the replica bucket.

Notice
  • The replication feature operates in a 1:N structure, allowing replication within a region or between regions. When performing cross-region replication, data transfer fees are added.
  • The replication feature applies only to files uploaded after the replication policy is set.
  • Even if you delete the original version file, files in the replica bucket are not deleted.
    • Example: If set from Bucket A to Bucket B, even if the version file of Bucket A is deleted, it remains in Bucket B.
  • You can set up bidirectional replication.
    • Example: When set as Bucket A ↔ Bucket B, files uploaded to Bucket A are replicated to Bucket B, and files uploaded to Bucket B are replicated to Bucket A.
  • The duplicated file is not duplicated.
    • Example: If set as Bucket A → Bucket B → Bucket C, files replicated from Bucket A → Bucket B are not replicated from Bucket B → Bucket C.
Reference
kr-south region does not provide inter-region Object Storage replication functionality.

Add replication policy

Notice
  • You can set replication on the created bucket.
  • To add a replication policy, you must set the version control feature to enabled.
  • To set up the version management feature, refer to Setting Version Management.

To add a replication policy, follow these steps.

  1. All Services > Storage > Object Storage Click the menu. Navigate to Object Storage’s Service Home page.
  2. Click the Object Storage menu on the Service Home page. You will be taken to the Object Storage list page.
  3. Object Storage List page, click the resource to add a replication policy. It will navigate to the Object Storage Details page.
  4. Click the Duplicate tab.
  5. Click the Add button. Add replication policy popup opens.
  6. After entering the policy information, click the Confirm button. A popup window notifying the creation of the replication policy opens.
CategoryRequiredDetailed Description
Policy NameRequiredEnter the name of the replication policy
  • Enter within 255 characters, including English letters, numbers, and special characters (-._)
Replication LocationRequiredSelect replication location (region)
  • Other locations can be selected
Replication Bucket NameRequiredSelect the name of the replication bucket
  • If set the same as the source bucket name, adding a replication policy is not allowed
Target FileRequiredSelect files to replicate
  • All: Replicate all files
  • Prefix: Replicate files that start with the value entered as a prefix
    • Enter within 1,024 bytes based on UTF-8 encoding (same as file length constraint)
  • Special characters (%<>#\`^|{}[]) cannot be entered
  • When performing putobject using the S3 API’s prefix option, the prefix must start with /
Delete marker duplicationSelectWhether to use delete marker duplication
Table. Replication Policy Add Popup Items
  1. Confirm button을 클릭하세요. 복제 정책이 추가됩니다.
Caution

If there is an invalid policy, you cannot add a replication policy.

  • Example: If a deleted policy remains for a replication bucket, you cannot add a replication policy.

Edit replication policy

You can modify the replication policy’s replication location, replication bucket name, and target file.

Notice
  • To modify the replication policy, you must set the version control feature to enabled.
  • How to set up the version management feature, refer to Set up version management.

To modify the replication policy, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Navigate 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 modify the replication policy. Navigate to the Object Storage Detail page.
  4. Clone tab을 클릭하세요.
  5. Click the More > Edit button of the policy you want to modify in the replication policy list. Edit Replication Policy popup window opens.
  6. After modifying the replication policy information, click the Confirm button. A popup window notifying the replication policy modification will open.
CategoryRequiredDetailed description
Replication locationRequiredSelect replication location (region)
  • Other locations can be selected
Replication Bucket NameRequiredEnter the name of the replicated bucket
  • If set the same as the original bucket name, replication policy cannot be modified
  • If you set a bucket already in use as the replication bucket, replication policy cannot be modified
Target FileRequiredSelect files to replicate
  • All: Replicate all files
  • Prefix: Replicate files that start with the value entered as a prefix
    • Enter within 1,024 bytes based on UTF-8 encoding (same as file length constraint)
    • Special characters (%<>#\`^|{}[]) cannot be entered
    • When performing putObject using the S3 API’s prefix option, the prefix must start with /
Delete marker duplicationSelectWhether to use delete marker duplication
Table. Replication Policy Edit Popup Items
  1. Confirm 버튼을 클릭하세요. 복제 정책 수정이 완료됩니다.
Caution

If there is an invalid policy, you cannot add a replication policy.

  • Example: If a policy remains after the replica bucket has been deleted, you cannot add a replication policy.

Change replication policy status

You can enable or disable the replication policy to change whether the replication policy is performed.

To change the replication policy status, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Navigate 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. Click the resource to change the replication policy status on the Object Storage List page. Navigate to the Object Storage Details page.
  4. Clone tab click.
  5. In the replication policy list, click the More > Activate or More > Deactivate button for the policy whose status you want to change. A popup window notifying the replication policy status change will open.
    • Activation: Performs replication according to the replication policy.
    • Disable: Stops performing replication.
  6. Click the Confirm button. The status of the replication policy will change.

Delete replication policy

You can delete unused replication policies.

To modify the replication policy, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Navigate to Object Storage’s Service Home page.
  2. Click the Object Storage menu on the Service Home page. It moves to the Object Storage List page.
  3. Object Storage List On the page, click the resource to delete the replication policy. Object Storage Details Navigate to the page.
  4. Clone 탭을 클릭하세요.
  5. Click the More > Delete button of the policy you want to edit in the replication policy list. A popup notifying the deletion of the replication policy will open.
  6. Confirm Click the button. The replication policy will be deleted.
Caution
  • If you change the usage of versioning for the source and replica buckets, replication will not be performed correctly.
    • If versioning of the source bucket is set to disabled, replication will not be performed. If set back to enabled, replication will be performed for files uploaded after the setting.
    • If you set versioning of the replica bucket to disabled, replication will be performed but versioning is not possible. If you set it back to enabled, versioning will apply from the point it is set.
  • If you delete the source bucket, the configured replication policy will also be deleted.
  • If you delete the replica bucket, the replication policy set on the source bucket remains.
    • If you recreate a replication bucket with the same bucket name as a deleted replication bucket, replication will be performed to that bucket.

3.2.5 -

3.3 - Release Note

Object Storage

2025.10.23
FEATURE Duplication, file copy feature added and Cloud Functions service integration
  • Object Storage’s replication feature has been added.
    • You can perform replication to a bucket in a different location or the same location, and you can set multiple replication policies.
  • File copy feature has been added.
    • You can copy the desired file within the same bucket and folder.
  • Cloud Functions service has been added to access control.
    • You can upload Java Runtime executable files in Cloud Functions.
2025.07.01
FEATURE Add access server resources and Presigned URL feature
  • A server resource target product has been added to Object Storage access control.
    • Multi-node GPU Cluster, PostgreSQL, MariaDB, MySQL, EPAS, Microsoft SQL Server
  • Presigned URL has been added.
    • You can download the file using a Presigned URL for the set period of time.
  • You can perform Copyobject on encrypted files.
2025.04.28
FEATURE Amazon S3 version added
  • Additional versions of the Amazon S3 SDK and Amazon S3 CLI that can be used have been added.
2025.02.27
FEATURE VPC Endpoint connection feature added
  • Object Storage feature change
    • VPC Endpoint can be used to access Object Storage from external networks.
  • Samsung Cloud Platform Common Function Change
    • Account, IAM and Service Home, tags, etc. have been reflected in the common CX changes.
2024.10.01
NEW Object Storage Service Official Version Release
  • Launched an object storage service that makes data storage and retrieval easy.
2024.07.02
NEW Beta version release
  • We have launched Object Storage, a service that provides a space (bucket) to economically store large amounts of data.

4 - Archive Storage

Data stored in Object Storage can be automatically transferred to Archive Storage for storage and easily recovered when needed.

4.1 - Overview

Service Overview

Archive Storage is a storage service suitable for long-term storage of large amounts of data. Users can set a schedule to automatically transfer infrequently used data stored in Object Storage to Archive Storage, thereby efficiently configuring storage and managing costs. Additionally, if a user requests, data stored in Archive Storage can be restored to Object Storage for use.

Special Features

  • Free capacity usage: If you create a bucket in Archive Storage, the bucket automatically expands or shrinks according to the user’s data archiving and deletion. There is no cost for creating a storage bucket, and you are only charged for storage usage.

  • Stable Data Recovery: Data that has been stored long-term can be searched and reliably recovered within 3 hours. When recovering data, select the target file and the Object Storage bucket where you want to store it to recover the data.

  • Cost Efficiency: Depending on the purpose and frequency of data usage, you can efficiently configure Object Storage and Archive Storage to store and manage data at a reasonable cost.

  • Convenient Use: You can conveniently use functions such as bucket creation, Archiving schedule setting, and data recovery on the Samsung Cloud Platform Console. After migrating data for all files in Object Storage, you can apply a source deletion policy.

Diagram

Diagram
Figure. Archive Storage diagram

Provided Features

Archive Storage provides the following functions.

  • Archiving Plan Setting: Set a schedule to perform archiving on all files in the Object Storage bucket.
  • Data Recovery: You can recover to the Object Storage bucket and folder you want to store using folders or files stored in Archive Storage.
  • Archiving status monitoring: Archiving status (success, cancelled, failed, in progress, pending, skipped) can be checked.
  • Recovery status monitoring: You can check the recovery status (success, cancelled, failure, in progress, pending).
  • Encryption: If encryption is set to use, encryption is provided via the SSE‑S3 method.
  • Version Management: You can manage archived files by version and recover by selecting the desired version.

Components

Authentication Key

To create and access the Archive Storage service on the Samsung Cloud Platform Console, an authentication key is required. Therefore, to use Archive Storage, you must generate an authentication key.

bucket

Bucket (Bucket) is the top-level folder and all folders and files exist under the bucket. When you create an Archive Storage service in the Samsung Cloud Platform Console, a bucket is created, and thereafter you can upload folders or files.
The bucket name creation rules are as follows.

  • Bucket name must be at least 3 characters and at most 63 characters.
  • Bucket names can only consist of lowercase English letters, numbers, period. and hyphen-.
  • Bucket name must start with a lowercase English letter or a number.
  • Bucket names must not be used with two periods placed side by side.
  • Bucket names cannot end with a period or hyphen.
  • Bucket names cannot have periods and hyphens adjacent.
  • Bucket names do not use IP address format (e.g., 192.168.x.x).
  • You cannot use the name admin as a bucket name.
  • Bucket name must be unique within the Account.
  • The previously used bucket name can be used after up to 1 hour.
Valid bucket name exampleInvalid bucket name example
Usable bucket names are as follows
  • cpexamplebucket1
  • scp-example-bucket-01
  • my-scp-object-storage
The following bucket names cannot be used
  • scp_example_bucket(including underscore)
  • DocExampleBucket(including uppercase)
  • -scp-example-bucket(starting with hyphen)

folder

Folder (Folder) is used to logically group files.
The folder name creation rules are as follows.

  • Folder names can consist of Korean, English, numbers, and special characters.
  • The special characters that cannot be entered are as follows.
Special characters that cannot be used in folder names
  • percentage sign%
  • ampersand&
  • question mark?
  • exclamation mark!
  • less-than sign<,greater-than sign>
  • slash/
  • equals sign=
  • plus sign+
  • dollar sign$
  • pound sign#
  • apostrophe
  • caret^
  • vertical bar/pipe|
  • left curly brace{,right curly brace}
  • left bracket[,right bracket]

file

File (File) is the data stored in Archive Storage and is the same as a regular file.
The file name generation rules are as follows.

  • File names can consist of Korean, English, numbers, and special characters.
  • The special characters that cannot be entered are as follows.
Special characters not allowed in file names
  • percentage sign%
  • ampersand&
  • question mark?
  • exclamation mark!
  • less-than sign<, greater-than sign>
  • slash/
  • equals sign=
  • plus+
  • dollar$
  • pound sign#
  • backslash\
  • apostrophe
  • caret^
  • vertical bar/pipe|
  • left curly brace{, right curly brace}
  • left square bracket[, right square bracket]
  • plus+

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

Example of mixed use of folder names and file names
  • 3scp-example
  • my.happy_photo-2024/20240101.jpg
  • video/2024/video01.wmv
Note
The length of the path, including folder name, file name, and the delimiter (/), is limited to within 1,024 Bytes (based on UTF-8 encoding).

Constraints

Archive Storage’s constraints are as follows.

CategoryDescription
Number of creatable Archive Storage services1,000 or less
File name length (including path)1,024 Bytes or less
Table. Archive Storage Constraints
Reference
  • If using through IAM role, Archive Storage cannot be used via Samsung Cloud Platform Console, and only IAM users can use it.

Preliminary 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
StorageObject StorageObject storage that facilitates data storage and retrieval
Table. Archive Storage Preliminary Service

4.2 - How-to guides

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

Create authentication key

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

API key creation can be done from My menu > My Info. > API key management > Create API key. For detailed information, see IAM > Create API key.

Note
  • The authentication key is used not only for Archive Storage, but also for authentication in OpenAPI and CLI.
  • Authentication keys can be generated up to a maximum of 2.
Caution
  • If the authentication key expires, access to the Archive Storage service will be restricted. To ensure smooth service usage, please check the expiration period of the authentication key in advance.
  • If you disable the authentication key, access rights to the Archive Storage service will be restricted.

Archive Storage Create

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

To create Archive Storage, follow the steps below.

  1. All Services > Storage > Archive Storage Click the menu. Go to the Service Home page of Archive Storage.
  2. Service Home on the page click the Create Archive Storage button. Navigate to the Create Archive Storage page.
  3. Archive Storage creation On the page, enter the information required to create the service, and select detailed options.
    Category
    Required
    Detailed description
    Bucket NameRequiredBucket name for performing Archiving
    • Start with a lowercase letter or number, and use lowercase letters, numbers, dash-, and period. to input 3~63 characters
    • Cannot have two or more consecutive periods.
    • Periods. and dashes- cannot be adjacent
    • Cannot end with a period. or dash-
    • IP format not allowed
    • admin name not allowed
    • Cannot use a bucket name already in use in the same region within the Samsung Cloud Platform Console
    Table. Archive 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 Archive Storage List page.
Notice

Archive Storage Check detailed information

Archive Storage Detail page consists of Detailed Information, Folder List, Archiving History, Recovery History, Tag tabs.

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

  1. All Services > Storage > Archive Storage Click the menu. Navigate to Archive Storage’s Service Home page.
  2. Service Home page, click the Archive Storage menu. Go to the Archive Storage list page.
  3. Archive Storage list on the page, click the resource to view detailed information. Archive Storage details navigate to the page.
    • Archive Storage Details The page displays status information and additional feature information, and consists of Details, Folder List, Archiving History, Recovery History, Tags tabs.
      CategoryDetailed description
      Archive Storage statusArchive Storage status information
      • Active: available
      • Error: abnormal state during termination
      • Deleting: service termination in progress
      Service terminationButton to cancel the service
      Table. Archive Storage status information and additional functions

Detailed Information

In the Detailed Information tab, you can view the resource’s detailed information and, if necessary, edit the information.

CategoryDetailed description
ServiceService group
resource typeresource type
SRNUnique resource ID in Samsung Cloud Platform
Resource NameResource Name
  • In Archive Storage service, it means the bucket name
Resource IDService’s unique resource ID
Bucket nameUser-created bucket name
UsageTotal data usage of the bucket
EncryptionEncryption usage information
  • When encryption is used, the SSE‑S3 encryption key method and AES256 encryption algorithm are applied
  • Encryption settings are configured on the Archive Storage detail page after creating Archive Storage
Version ManagementVersion Management Usage Information
  • Click the Edit button to set usage
Archiving policyCheck configured archiving target and policy tasks
  • If not in use, click the Add button to set the policy
Archiving targetObject Storage bucket to perform archiving
Policy WorkArchiving Policy List
  • Display Policy Information
    • Policy ID: Policy ID value
    • Target File: Archiving target object
    • Full Version Archiving: Execution time of Archiving policy operation
    • Status: Active (enabled), Inactive (disabled)
  • Click the Add button to add a new policy
  • Click the More button to manage
    • Deactivate: Deactivate a policy in Active state (when deactivated, display as changed to Active)
    • Edit: Can change the execution time of the Archiving policy
Table. Archive Storage detailed information tab items
Reference
  • Archiving target can be set only once initially. After setting, it cannot be modified.
  • Policy work performs archiving for the entire version files of Object Storage.
  • Archiving policy can only be modified, not deleted.
  • Archiving policy is performed once a day based on the addition point.
Caution
If you reuse the bucket name of the Archiving target, be careful as the configured archiving policy will be applied.

Folder List

Folder List in the tab, you can view the list and size of folders that have been archived.

CategoryDetailed description
NameName of the file or folder on which Archiving was performed
  • You can search by entering the first letter of the folder or file in the search area.
SizeSize of archived file or folder
Modification Date/TimeFile or folder’s last modified date/time
More buttonManage selected files or folders
  • Version list: Check version list of selected file
    • Can restore to desired version or delete version history
  • Restore: Restore selected files or folders
  • Delete: Delete selected files or folders
Table. Archive Storage folder list tab items

Archiving History

Archiving History in the tab, you can view the list of archiving performed over a specific period.

CategoryDetailed description
Query periodSelect the period to check the Archiving history
  • Up to 90 days can be queried
StatusSelect Archiving status
  • All, In progress, Success, Failure, Cancelled, Pending, Skip can be selected
Policy IDArchiving Policy ID
  • When clicked, Status Check popup opens
  • Policy ID, execution time, status, target file, capacity, progress can be checked
Execution Date and TimeArchiving Start Time
Completion Date/TimeArchiving Completion Time
StatusArchiving status information
Cancel TaskCancel Archiving Task
  • If Archiving status is Pending or In Progress, enable
  • When clicked, Cancel Task popup opens
Table. Archive Storage Archiving History Tab Items

Recovery History

You can view the list of Archives that performed recovery tasks over a specific period in the Recovery History tab.

CategoryDetailed description
Search periodSelect the period to view the recovery history
  • Up to 90 days can be queried
StatusSelect recovery status
  • All, In progress, Success, Failure, Cancel, Waiting, Skip can be selected
  • Recovery target, Archive recovery ID, Recovery date/time, Status, Original location can be verified
Recovery TargetRecovery Target Object Storage Name
  • When clicked, Check Status popup opens
Recovery Date and TimeRecovery Start Time
Completion Date/TimeRecovery Completion Time
StatusRecovery status information
Cancel recovery operationCancel recovery operation
  • If the recovery status is Pending or In progress, activated
  • When clicked, Cancel operation popup opens
Table. Archive Storage Recovery History Tab Items

tag

In the Tag tab, you can view the resource’s tag information, 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. Archive Storage tag tab items

Archive Storage Set up encryption

You can configure the data stored in the bucket to be encrypted. After setting bucket encryption, the encryption setting is applied to data uploaded thereafter. When encryption is used, the SSE‑S3 encryption key method and the AES256 encryption algorithm are applied.

Reference

Archive Storage’s 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 using Amazon S3 managed keys (SSE-S3) has been released as the default method, and server-side encryption using Key Management Service (KMS) keys (SSE-KMS) will be provided in the future according to the service roadmap.

Notice

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.

To set up encryption, follow the steps below.

  1. All Services > Storage > Archive Storage Click the menu. Navigate to Archive Storage’s Service Home page.
  2. Click the Archive Storage menu on the Service Home page. Go to the Archive Storage list page.
  3. Archive Storage List page, click the resource (bucket) to use encryption. Navigate to the Archive Storage Details page.
  4. On the Archive Storage Details page, after confirming that encryption is unused, click the edit button. Encryption Edit popup window opens.
  5. After checking the use of encryption, click the Confirm button.

Archive Storage Cancel

Note
Archiving is in progress or when restoring an Archive file, Archive Storage cannot be cancelled.

To cancel Archive Storage, follow the steps below.

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

4.2.1 - Archiving Policy Management

You can add, modify, or delete Archiving policies.

Archiving Add Policy

To add an Archiving policy, follow the steps below.

  1. All Services > Storage > Archive Storage Click the menu. Go to the Service Home page of Archive Storage.
  2. Service Home on the page click the Archive Storage menu. Navigate to the Archive Storage list page.
  3. Click the resource on the Archive Storage List page to view detailed information. It navigates to the Archive Storage Details page.
  4. Click the Add button of Policy Actions. The Add Archiving Policy popup opens.
  5. After entering the Archiving policy information, click the Confirm button.
    CategoryDetailed description
    Archiving targetSelect the bucket of Object Storage to perform Archiving
    • Cannot be modified after initial setup
    • Only buckets within the same region can be added
    • Buckets used in policies of other Arcvhie Storage cannot be selected
    Target ObjectSelect Archiving target object
    • All only selectable
    Archiving policy workWhen selected, archiving is performed on all version objects of Object Storage
    • When using Archive Storage version management: manage all versions separately
    • When not using Archive Storage version management: manage by overwriting the current version
    Execution timearchiving execution time input
    • Enter a number between 1 and 3,650
    Table. Archiving policy addition popup items
Reference
  • Archiving target can be set only once initially. It cannot be modified after being set.
  • Policy work performs archiving for the entire version files of Object Storage.
  • Archiving policy can only be edited, not deleted.
  • Archiving policy is performed once a day based on the addition point.

Archiving Modify policy

To modify the Archiving policy, follow the steps below.

  1. Click the All Services > Storage > Archive Storage menu. Navigate to the Service Home page of Archive Storage.
  2. Click the Archive Storage menu on the Service Home page. Go to the Archive Storage list page.
  3. Archive Storage List page, click the resource to view detailed information. It navigates to the Archive Storage Details page.
  4. Policy Actions After selecting the policy you want to edit from the list, click the More > Add button on the right. Edit Archiving Policy popup opens.
  5. After modifying the Archiving policy information, click the Confirm button.
Caution
If you reuse the bucket name of the Archiving target, the configured archiving policy will be applied, so be careful.

Archiving Change policy status

You can change whether the Archiving policy is performed by enabling or disabling the Archiving policy.

To change the Archiving policy status, follow the steps below.

  1. All Services > Storage > Archive Storage Click the menu. Navigate to the Service Home page of Archive Storage.
  2. Click the Archive Storage menu on the Service Home page. Navigate to the Archive Storage List page.
  3. Click the resource to change the Archiving policy status on the Archive Storage List page. It navigates to the Archive Storage Details page.
  4. Policy Actions in the list, click the More > Activate or More > Deactivate button for the policy whose status you want to change. A popup window notifying the Archiving policy status change will open.
    • Activation: Perform archiving according to the archiving policy.
    • Disable: Stops performing archiving.
  5. Click the Confirm button. The status of the Archiving policy will change.

Archiving Cancel operation

Notice
Only Archiving tasks that are pending or in progress can be cancelled.

To cancel Archiving, follow the steps below.

  1. All Services > Storage > Archive Storage menu. Go to the Service Home page of Archive Storage.
  2. Click the Archive Storage menu on the Service Home page. Navigate to the Archive Storage list page.
  3. Archive Storage List on the page, click the resource to cancel the Archiving operation. Navigate to the Archive Storage Details page.
  4. Click the Archive History tab.
  5. In the Archiving history list, check whether the status of the Archiving policy for which you want to cancel the job is Pending or In progress.
  6. Cancel button click. Cancel confirmation popup opens.
  7. Confirm Click the button. The corresponding Archiving task will be canceled.

Archiving How it works

The Archiving behavior according to the target is as follows.

Archiving targetdetailed description
Previous version/current version fileDepends on whether versioning is used in Archive Storage
  • Object Storage versioning: Enabled / Archive Storage versioning: Enabled
    • All versions of Object Storage are also managed by version in Archive Storage
  • Object Storage versioning: Enabled / Archive Storage versioning: Disabled
    • Archiving is performed for all versions of Object Storage, but Archive Storage only manages the Current version (file overwrite applied)
    • Since Archive Storage only manages the Current version, previous version files of Object Storage cannot be viewed in Archive Storage
  • Object Storage versioning: Disabled / Archive Storage versioning: Enabled
    • Object Storage only manages the Current version (overwrite applied) and Archive Storage manages by version
  • Object Storage versioning: Disabled / Archive Storage versioning: Disabled
    • Both Object Storage and Archive Storage only manage the Current version (overwrite applied)
Delete Marker version containing fileDelete Marker version cannot be archived
  • When the latest version is a Delete Marker
    • Object Storage Details page’s Folder List tab cannot view the file
    • Archive Storage Details page’s Folder List tab can be viewed
  • When an intermediate version is a Delete Marker
    • Cannot view that version in the file version list of Object Storage and Archive Storage
    • After archiving, only the Delete Marker version is retained in Object Storage
Empty folderFolder creation not possible in Archive Storage
Folder with filesDepending on whether the folder is an Object, the folder deletion in Object Storage after archiving differs
  • If the folder is an Object: the folder is not deleted and is retained
    • When the folder is created first and then files are uploaded
    • When the folder containing files is uploaded directly from Windows
  • If the folder is not an Object: folder deletion
    • When the folder containing files is uploaded directly from Linux
    • When the folder itself is restored from Archive Storage to Object Storage
When there is no target filePerform the Archiving schedule as is
  • Archiving size: 0 B
When the target Object Storage bucket is terminated
  • Keep display of Archiving target
  • When clicking the Archiving target (Object Storage) link, fail to retrieve the bucket
  • After deleting the bucket, handle archiving failure
  • When recreating the bucket with the same name, maintain archiving with the new bucket
Table. Archiving method according to archiving target
Reference
  • Archiving is performed based on the Etag value of the Object Storage file.
  • After archiving, Version ID and Modification Timestamp are changed. However, Etag value remains the same.

4.2.2 - Using Version Control

You can set versioning on the bucket to manage all versions of Object Storage in Archive Storage.
If you use version control, you can view the list of file versions, and from the version list you can select a previous version of the file to restore.

Version Control Setup

Follow the steps below to set up the version control feature.

  1. All Services > Storage > Archive Storage Click the menu. Navigate to Archive Storage’s Service Home page.
  2. Click the Archive Storage menu on the Service Home page. Go to the Archive Storage list page.
  3. Click the resource to use the version control feature on the Archive Storage List page. Navigate to the Archive Storage Details page.
  4. Archive Storage Details on the page, Version Management is Unused after confirming, click the Edit button. Edit Version Management popup window opens.
  5. After checking the use of version control, click the Confirm button. The Archive Storage Details page’s version control will be changed to use.
Note
  • If you set up version control for the first time, it may take some time for changes to be completed.
  • The time required varies depending on the size of the bucket, and version control may not be applied before the settings are completed.

Check version list

You can view and manage the version list of the file.
To view and manage the file’s version list, follow these steps.

  1. All Services > Storage > Archive Storage Click the menu. Go to the Service Home page of Archive Storage.
  2. Click the Archive Storage menu on the Service Home page. Go to the Archive Storage list page.
  3. Archive Storage list page, click the resource to view the version list. Archive Storage detail page, navigate to it.
  4. Archive Storage Details page, click the Folder List tab.
  5. Click the More > Version Management button of the file whose version list you want to check. The version list popup will open.
CategoryDetailed description
FilenameFile name under version control
Modification Date and TimeFile’s modification date and time
Version IDVersion ID assigned to each individual file
  • File before version control setting: null(-) displayed
  • File after version control setting: unique ID value displayed
Etagobject that can identify a file’s specific version
SizeVersion file size
MoreDelete or restore the version
  • Delete: Delete the version from the version list
Table. Version list item
Notice

From the point when version control is set, you can check and manage the version ID of archived files.

  • Before setting version control archived file: Version ID is displayed as null(-).
  • After setting up version control archived file: Version file is added and a unique version ID is generated and assigned.

Delete version file

To delete unused version files, follow the steps below.

  1. All Services > Storage > Archive Storage Click the menu. Navigate to the Archive Storage Service Home page.
  2. Click the Archive Storage menu on the Service Home page. Go to the Archive Storage list page.
  3. Archive Storage list page, click the resource to view the version list. Archive Storage details page will be opened.
  4. Archive Storage Details on the page Folder List Click the tab.
  5. Click the More > Version Management button of the file whose version file you want to delete. The version list popup opens.
  6. Click the More > Delete button for the version file to be deleted. The version file will be removed from the version list.
    • After selecting all version files to delete, you can click the Delete button at the top of the list to delete them all at once.
Caution
If you delete all version files, the original file will also be deleted. To keep the original file, leave at least one version.

4.2.3 - Archive Recover

Archive Recover

Note
  • Recovery can be performed on a per-file basis, and even after recovery, data stored in Archive Storage is not deleted.
  • When restoring the Archive file, select the bucket and folder of the Object Storage and restore to that location. Before starting the restoration, first verify the Object Storage you want to restore.

Recover from folder list

If you are not using the version control feature, you can recover by selecting the Archive file from the folder list.
To check and recover the Archive file, follow the steps below.

  1. All Services > Storage > Archive Storage Click the menu. Navigate to the Archive Storage Service Home page.
  2. Service Home page, click the Archive Storage menu. Go to the Archive Storage list page.
  3. Click the resource to view detailed information on the Archive Storage List page. It navigates to the Archive Storage Details page.
  4. Folder List Click the tab.
  5. Select the folder or file name to restore from the folder list. The Delete and Restore buttons appear at the top of the list.
  6. Recover Click the button. Archive Recover popup window opens.
  7. After selecting the recovery information, click the Confirm button.
    CategoryDetailed description
    Bucket NameObject Storage’s bucket name
    Original locationOriginal file or folder location
    Recovery targetSelect recovery target bucket
    OverwriteSelect whether to use the overwrite function
    • When selecting a bucket of Object Storage that is using versioning as the recovery target, using the overwrite function will store the existing file with the same name as a previous version
    Table. Archive Recovery Popup Items
Caution
  • Recovery may fail due to character count restrictions on files and folders. The character count restrictions on files and folders are File name creation rules, Folder name creation rules. Please refer.
  • After a recovery failure, if you use the overwrite function to perform recovery again, you may be charged duplicate fees.
Notice
If recovery fails, check whether the completed recovered files are present in the target Object Storage.

Recover from version list

If you use the version control feature, you can check the file’s version and restore it to the desired version.

Notice
  • To check the file’s version and recover it, you need to set the version control feature to use..
  • To set up version control features, please refer to Setting up version control.

Use the version file to recover the Archive file by following these steps.

  1. All Services > Storage > Archive Storage Click the menu. Move to Archive Storage’s Service Home page.
  2. Service Home on the page, click the Archive Storage menu. Navigate to the Archive Storage list page.
  3. Archive Storage List page, click the resource to view detailed information. Archive Storage Details page will be opened.
  4. Folder List Click the tab.
  5. In the folder list, click the More > Version Management button for the file whose version list you want to check. The version list popup will open.
  6. In the version list, click the More > Recover button of the version file to be restored. Archive Recover popup window opens.
  7. After selecting the recovery information, click the Confirm button.
    CategoryDetailed description
    Bucket nameObject Storage’s bucket name
    Original locationOriginal file or folder location
    Version ListModification date and time of the version to be restored, version ID, Etag, size information
    Recovery targetSelect recovery target bucket
    OverwriteSelect whether to use the overwrite function
    • When selecting a bucket of Object Storage that is using versioning as the recovery target, using the Overwrite function saves the existing file with the same name as a previous version
    Table. Archive Recovery Popup Items
Caution
  • Recovery may fail due to character count restrictions on files and folders. The character count restrictions on files and folders are File name creation rules, Folder name creation rules. Please refer to.
  • After a recovery failure, if you perform recovery again using the overwrite function, you may be charged duplicate fees.
Notice
If recovery fails, check whether the completed recovered files are present in the target Object Storage.

Cancel recovery operation

Notice
Only recovery tasks that are pending or in progress can be canceled.

To cancel the recovery operation, follow the steps below.

  1. All Services > Storage > Archive Storage Click the menu. Navigate to the Archive Storage Service Home page.
  2. Click the Archive Storage menu on the Service Home page. Go to the Archive Storage list page.
  3. Archive Storage List On the page, click the resource to cancel the recovery operation. Archive Storage Details Navigate to the page.
  4. Recovery History Click the tab.
  5. In the recovery history list, check whether the status of the recovery target to cancel the operation is Pending or In Progress.
  6. Cancel operation Click the button. A cancel operation confirmation popup will open.
  7. Confirm Click the button. The recovery operation will be canceled.

Archive Learn about recovery methods

The recovery methods according to the type of recovery are as follows.

Recovery TypeStatus Description
General Recovery
  • If some of the original locations are pending: Pending
  • If all original locations are in progress: In progress
  • Work possible only when In progress
When there is no file to recover (overwrite option not used)Not shown in the status check list
Table. Recovery method according to recovery type

4.3 - API Reference

API Reference

4.4 - CLI Reference

CLI Reference

4.5 - Release Note

Archive Storage

2025.10.23
FEATURE Version control feature added
  • You can manage archived folders or files by version.
    • The user can view archived folders or files by version and select the desired version to delete or restore.
2025.07.01
NEW Archive Storage Service Official Version Release
  • Archive Storage service has been launched.
    • Automatically transfer data stored in Object Storage to Archive Storage for storage, and easily recover it when needed.

5 - Backup

5.1 - Overview

Service Overview

Backup is a service that backs up and restores the user’s data in a safe way.
The backup policy includes the backup target, cycle, and retention period, so the user sets the backup plan according to the business environment and requirements.

Features

  • Backup scope: Provides optimal backup and recovery services suitable for various business purposes to safely preserve customers’ important data.
  • Flexible Policy Setting: The backup policy can be set according to the usage environment and data importance. The user can select the backup target and type, and specify the retention period and schedule.
  • Backup Network: The backup network connection has been designed to minimize the impact on services that may occur during backup. The backup system and network are restricted through access control to prevent unauthorized access.
  • Remote Backup: You can store backup copies in a different location. In the event of a disaster or failure at the backup location, you can use the backup copy stored in a different location to recover.

Composition

Configuration Diagram
Figure. Backup Configuration Diagram

Provided Features

Backup provides the following functions.

  • Backup target: The user can select the target server they want to secure the backup for.
  • Backup Save: You can select the storage location of the backup.
  • Encryption: You can choose whether to encrypt or not. If selected, AES-256 algorithm encryption will be applied.
  • Retention period: You can set the retention period for the backup. Backups that have exceeded the retention period will be automatically deleted.
  • Schedule: The cycle of automatic backup creation.
  • Recovery: You can recover resources by selecting a backup created at the desired point in time.

Component

Backup provides scheduling functionality to automatically create backups at predefined cycles and times. The user can set the retention period, etc. to secure the backup at the desired point in time, and Agent configuration may be required depending on the Backup target and type.

Backup Type

Agentless Backup, Agent Backup are provided, and can be selected according to the Backup target.

  • Agentless Backup: Without separate Agent configuration, backup can be performed through Backup service creation. Virtual Server, GPU Server’s VM Image backup corresponds to Agentless Backup.
  • Agent Backup: Before creating a Backup service, it is necessary to create and configure a Backup Agent for the server to be backed up. This includes Filesystem backup for Bare Metal Servers.

Backup classification

  • Full Backup: Performs a backup on the entire data.
  • Incremental Backup: Backs up data changed based on the previous Full Backup.

Schedule

It automatically generates a backup according to the generation cycle set by the user. Schedule setting is possible up to 1 Full Backup and 6 Incremental Backups.
When using the immediate Backup feature, you can create a backup at a specific point in time outside of the schedule. The backup cycle that can be set as a schedule is as follows.

  • Daily: Start Time selection

  • Every week: day of the week, start time selection

  • Every month: week, day of the week, start time selection

    • Start Time: hour (1~23), minute (00, 30) selection
    • Day of the week: Mon, Tue, Wed, Thu, Fri, Sat, Sun selection
    • Parking: 1, 2, 3, 4, last parking selection

Storage Period

You can set the retention period of the backup created through the Backup service. The retention period that can be set is as follows.

  • Agentless Backup: You can choose from 2 weeks (14 days), 1 month (31 days), 3 months (90 days), 6 months (180 days), or 1 year (365 days). It is applied based on the date, so if you set it to 1 month, it will be kept for 31 days.
  • Agent Backup: You can choose from 2 weeks, 1 month, 3 months, 6 months, and 1 year. It is applied based on the unit interval, so if you set it to 1 month, the backup on January 1st will be kept until January 31st, the day before February 1st, and the backup on February 1st will be kept until the day before March 1st.

Preceding Service

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

Service CategoryServiceDetailed Description
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeBare Metal ServerHigh-performance physical server without virtualization
Table. Backup Prerequisite Services

5.2 - How-to guides

The user can enter the required backup information and select detailed options through the Samsung Cloud Platform Console to create a service.

Creating Backup

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

To create a backup, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to Backup’s Service Home page.
  2. Click the Create Backup button on the Service Home page. You will be taken to the Create Backup page.
  3. Backup Creation page, enter the information required to create the service, and select detailed options.
    Category
    Required
    Detailed description
    Backup nameRequiredBackup name
    • Enter 3-30 characters using English letters and numbers
    • Cannot be modified after service creation
    Backup typeRequiredSelect backup type
    • (Agentless) VM Image: Perform backup by creating Backup service without Agent configuration
    • (Agent) Filesystem: Create Backup Agent service and configure Agent on target server, then perform backup by creating Backup service
    • Cannot modify after service creation
    Backup storageRequiredSelect storage location for Agentless Backup
    • One Backup service can be created per storage location
    • Servers in the South Korea (kr-south) region can only select the same location
    Backup replicationSelectSelect whether to replicate Agent Backup and its location
    • Replication can only be set when creating the Backup service
    • A Backup identical to the original (Backup name, schedule, retention period) is created at the replication location
    • South Korea (kr-south) region is not available
    Backup targetRequiredBackup target server
    • Agentless: select one pre-created server from the Virtual Server, GPU Server service
      • In the case of GPU Server, the target server location and the Backup storage location must be the same
    • Agent: select one pre-created server from the Bare Metal Server service/li>
    FilesystemRequiredEnter Backup target FileSystem
    • Accurate entry of the Filesystem used by the operating system is required. Backup not possible if entered incorrectly
    • /dev/zero, /dev/null entered: Backup not possible
    • Backup not possible if it contains the following special characters per operating system
      • Linux: : * < > |
      • Windows: / ? * < > |
    EncryptionRequired/OptionalEncryption status
    • Agentless: Default encryption applied
    • Agent: Encryption selection
    Retention PeriodSelectStorage period of recovery target (backup)
    • Select from 2 weeks (14 days), 1 month (31 days), 3 months (93 days), 6 months (186 days), 1 year (365 days)
    ScheduleSelectionBackup automatic creation cycle
    • Set 1 Full Backup, up to 6 Incremental Backups
    • Choose among Daily, Weekly, Monthly
    • Daily: Set Start Time
    • Weekly: Set Day of Week and Start Time
    • Monthly: Set Week Number, Day of Week, Start Time
      • Week Number: Choose among 1, 2, 3, 4, last week
      • Day of Week: Choose among Mon, Tue, Wed, Thu, Fri, Sat, Sun
      • Start Time: Choose in 30‑minute increments (00~23 hour, 00/30 minutes)
    Table. Backup 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 Backup List page.
Reference
  • Virtual, GPU Server creation or termination may take about 180 minutes to be reflected in the backup target list.
  • Virtual Server’s (Agentless) VM Image backup can be performed to a remote location by selecting a storage location (excluding GPU Server).
    • To create a remote backup, create the Backup service at the location where the Backup target server was created. Backup Save item, select the remote location.
    • Backup target can create one Backup service per region. By creating Backup services in two or more regions, stability against failures and disasters can be ensured.
    • To optimize backup and recovery speed, set the backup storage location to be the same as the target backup server’s location.
Caution
  • Agentless Backup has default encryption applied and cannot be modified.
  • Agent Backup applies server-side encryption based on the AES-256 algorithm when encryption is selected, and may cause a performance degradation of about 20 ~ 30%.
  • Agentless Backup is not possible to backup VM Image on servers with SSD_MultiAttach connected among Block Storage disk types.
  • The initial backup is created as a Full Backup regardless of the application details.
  • Backup storage, Backup replication If you select the location in a different region, data transfer fees will be added.

Backup Check detailed information

The Backup service allows you to view and edit the full resource list and detailed information. Backup Details page consists of Detailed Information, Schedule, Backup History, Recovery Target, Recovery History, Replication, Tags, Operation History tabs.

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

  1. Click the All Services > Storage > Backup menu. Navigate to the Service Home page of Backup.
  2. Service Home on the page click Backup menu. Go to the Backup List page.
  3. Click the resource to view detailed information on the Backup List page. You will be taken to the Backup Details page.
    • Backup Details page displays status information and additional feature information, and consists of Details, Schedule, Backup History, Recovery Target, Recovery History, Replication, Tags, Operation History tabs.
      CategoryDetailed description
      Backup statusBackup status information
      • Creating: In progress
      • Available: Creation completed
      • Deleting: Service termination in progress
      • Editing: Changing settings
      • Error: Abnormal state
      • Error Deleting: Abnormal state during deletion
      • Restoring: In progress
      Instant BackupInstantly create a backup copy at the time of creation
      Service cancellationButton to cancel the service
      Table. Status Information and Additional Functions

Detailed Information

Backup list page allows you to view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
serviceservice group
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
Resource NameResource Name
  • In the Backup service, it refers to the backup name
Resource IDUnique resource ID of the service
CreatorUser who created the service
Creation DateTimeDateTime when the service was created
EditorUser who modified the service
Modification DateTimeDate and time the service was edited
Backup nameBackup name
  • The copy’s backup name is the same as the original
CategoryOriginal status regarding duplication
Backup typeBackup type related to Agent configuration
EncryptionEncryption status
Backup targetBackup target server
FilesystemBackup target FileSystem
  • The replica’s Filesystem is the same as the original
Retention PeriodStorage period of recovery target (backup)
  • The retention period of the replica is the same as the original
  • If you need to modify the retention period, click the Edit button
Table. Backup Details - Detailed Information Tab Items

Schedule

You can view the automatic backup schedule of the selected resource on the Backup List page.

CategoryDetailed description
Schedule EditSchedule Edit Button
  • Schedule editing not allowed for copies
Schedule NameSchedule Name
  • Automatically set when creating a service or editing a schedule
Backup typeFull, Incremental Backup type
Backup cycleAutomatic backup generation cycle set by the user
Table. Backup Details - Schedule Tab Items
Reference
  • The schedule is based on Asia/Seoul (GMT +09:00).
  • The schedule can be set to 1 Full Backup and up to 6 Incremental Backups.
  • If it is in Available status, schedule can be modified.
  • The schedule of the replica is the same as the original, and can be checked in the original.
  • If the original is deleted, the replica’s schedule will be removed.

Backup History

On the Backup List page, you can view the immediate backup and scheduled backup execution history of the selected resources.

CategoryDetailed description
Schedule NameSchedule Name
  • Automatically set when creating a service or editing a schedule
Backup TimestampBackup Start Time
Completion Date and TimeBackup Completion Time
StatusBackup status information (Success/Failure/In progress)
Backup CancelCancel button while backup in progress
  • For detailed information about backup cancellation, refer to Cancel Backup
Table. Backup Details - Backup History Tab Items
Reference
  • Backup and completion date and time are based on Asia/Seoul (GMT +09:00).
  • Queries can be made based on backup timestamps within up to 30 days.
  • Notification on backup failure and can be checked in Management > Logging&Audit.
  • In the replica, the Cancel Backup button is not displayed.
  • The backup history of the original and the replica is provided by the original.
  • Click the Excel Download button at the top of the list to download the retrieved Backup history list as an Excel file.
Caution
  • Agentless Backup: Among Block Storage disk types, servers with SSD-MultiAttach attached cannot perform VM Image backup.

Recovery Target

On the Backup list page, you can view the recovery target (backup) of the selected resource.

CategoryDetailed description
ScheduleSchedule Name
  • Automatically set when creating a service or modifying a schedule
Backup TimestampBackup Start Time
Retention PeriodStorage period of recovery target
  • The retention period of the replica is the same as the original and can be verified from the original.
CapacityCapacity of the recovery target
Additional Features > MoreManagement button for recovery target
  • Recovery: Restore resources as recovery target
    • For detailed information about recovery, see Recover
Table. Backup Details - Recovery Target Tab Items
Reference
  • Backup date and time is based on Asia/Seoul (GMT +09:00).
  • You can query based on the backup date/time within up to 30 days.
  • Click the Excel Download button at the top of the list to download the retrieved recovery target list as an Excel file.

Recovery History

You can view the recovery execution history of the selected resource on the Backup list page.

CategoryDetailed description
ScheduleSchedule Name
  • Automatically set when creating a service or modifying a schedule
Recovery server nameName of the server created through recovery
Backup date/timeBackup start time of the recovery target used for recovery
Recovery date and timeRecovery start time
Recovery Completion DateTimeRecovery Completion Time
StatusRecovery status information (Success/Failure/In progress)
Table. Bacup Details - Recovery History Tab Items
Reference
  • Backup and recovery times are based on Asia/Seoul (GMT +09:00).
  • You can query based on the recovery date within up to 30 days.
  • By clicking the Excel download button at the top of the list, you can download the retrieved recovery history list as an Excel file.

Replication

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

Guide
  • Replication tab information is provided only when you set Agent Backup and Backup Replication to Use when applying for the Backup service.
  • In the case of Agentless Backup, the replication feature (replication tab) is not provided, and when applying for the service, you can select the backup storage location to store the backup copy in another location.
CategoryDetailed description
Replication PolicyUser-defined replication policy
Replication InformationOriginal and replica volume information
  • Distinction: Distinguish original status related to replication
  • Volume Name: Name of the original or replica volume
  • Location: Location where the volume was created
Table. Backup Details - Replication Tab Items

Tag

Backup 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
  • Tag’s Key, 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 created Keys and Values
Table. Backup Details - Tag Tab Items

Work History

Backup list page, you can view the operation history of the selected resource.

CategoryDetailed description
Work History ListResource Change History
  • Task date/time, resource type, resource ID, resource name, task details, event topic, task result, verify operator information
Table. Backup Details - Job History Tab Items

Backup Resource Management

If you need to modify the schedule or retention period of a created backup, cancel the backup, or delete a recovery target, you can perform the tasks on the Backup Details, Schedule, Recovery Target pages.

Edit retention period

You can modify the retention period of the backup. To modify the retention period, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to Backup’s Service Home page.
  2. Click the Backup menu on the Service Home page. Go to the Backup list page.
  3. Backup List page, click the resource to modify the retention period. Navigate to the Backup Details page.
  4. Click the Storage Period Edit button. The Storage Period Edit popup opens.
  5. Select the storage period and click the Confirm button.
    • 2 weeks (14 days), 1 month (31 days), 3 months (93 days), 6 months (186 days), 1 year (365 days) Please select.
  6. Backup Details page, check the modified retention period.
  7. Recovery Target Click the page. Check the modified retention period of the recovery targets.
Caution
  • Agentless Backup: When the retention period is modified, the retention period of all already created backup copies will be changed uniformly.
  • Agent Backup: After modifying the retention period, the changed retention period is applied to the generated backup.
Reference
If you modify the original, the same changes will be applied to the copy.

Filesystem Edit

You can modify the registered Filesystem. To modify the Filesystem, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Navigate to Backup’s Service Home page.
  2. Service Home on the page click the Backup menu. Go to the Backup list page.
  3. Click the resource to modify the retention period on the Backup list page. You will be taken to the Backup details page.
  4. Click the Edit button of Filesystem. Filesystem Edit popup window opens.
  5. Modify the Filesystem and click the Confirm button.
    • After entering the Filesystem to add, click the Add Target button. The Filesystem will be added to the list.
    • Click the X button of the Filesystem to delete from the Filesystem list. The Filesystem will be removed from the list.
Caution
  • Filesystem with the same name or a Filesystem registered in another Backup cannot be added.
  • /dev/zero, /dev/null cannot be added to the Filesystem.
  • If it includes the following special characters per operating system, recovery is impossible.
    • Linux: : * < > | not allowed
    • Windows: / ? * < > | not allowed

Edit Schedule

You can modify the backup schedule.

Guide
In the case of a copy, the schedule cannot be modified.

To modify the schedule, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to the Service Home page of Backup.
  2. Click the Backup menu on the Service Home page. Go to the Backup list page.
  3. Backup list page, click the resource to modify the schedule. You will be taken to the Backup details page.
  4. Click the Schedule page. You will be taken to the Backup Schedule page.
  5. Click the Edit Schedule button. The Edit Schedule popup window opens.
  6. Select the schedule and click the Confirm button.
    • Please choose among Daily, Weekly, Monthly.
    • Daily: Set the Start time.
  • Weekly: Set day, start time.
    • Monthly: Set the week, day, and start time.
      • Week: 1, 2, 3, 4, you can choose the last week.
  • Day: You can select from Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday. * Start Time: Can be selected in 30‑minute intervals (00~23h, 00/30 min).
Reference
  • The schedule is based on Asia/Seoul (GMT +09:00).
  • The schedule can be set to 1 Full Backup and up to 6 Incremental Backups, and at least one Full Backup schedule registration is required.
  • If the status is Available, the schedule can be modified.
  • After schedule modification, the initial backup is created as a Full Backup regardless of the application details.
  • If the original is edited, the same changes will be applied to the copy.

Backup Cancel

You can cancel an ongoing backup. To cancel the backup, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to the Service Home page of Backup.
  2. Click the Backup menu on the Service Home page. Go to the Backup list page.
  3. Click the resource to cancel the backup on the Backup List page. You will be taken to the Backup Details page.
  4. Click the Backup History page. Navigate to the Backup History page.
  5. Check the Backup you want to cancel. If the Backup status is in progress, Backup cancellation is possible.
  6. Backup Cancel Click the button. Backup Cancel popup window opens.
  7. After checking information such as Backup name, Backup date and time, click the Confirm button. The backup will be canceled.
Reference
If you cancel the backup, the backups of both the original and the copy will be canceled.

Delete recovery target

You can delete the generated recovery target (backup). To delete the recovery target, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to the Service Home page of Backup.
  2. Click the Backup menu on the Service Home page. Go to the Backup list page.
  3. Click the resource to delete the recovery target on the Backup list page. It moves to the Backup details page.
  4. Click the Recovery Target page. Navigate to the Backup Recovery Target page.
  5. After selecting all the items you want to delete, click the Delete button. Delete popup window opens.
  6. After checking Backup schedule name, Backup date and time, click the Confirm button.
    • If you delete two or more items, you can only see the count of items to be deleted in the popup window.
  7. Once deletion is complete, check on the Backup Recovery Target page whether the target has been deleted.
Reference
  • You can delete two or more recovery targets by using multi-select.
  • Even if you delete the recovery target of the original, the replica will not be deleted.

Backup Cancel

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

Caution
  • All saved backup data and history will be deleted. After termination, data cannot be recovered, so be careful.
  • If in the Available, Error, Error Deleting state, it can be terminated.
  • If you cancel the original Backup service, the replica’s schedule will be deleted, but the stored backup data will not be deleted.
  • Agent Backup that uses replication cannot be terminated. Change the replication policy to not used in the original, then terminate.

To cancel the backup, follow the steps below.

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

5.2.1 - Immediate Backup

You can perform an immediate backup of the current point in time, regardless of the schedule settings for the created backup. This task can be performed on the Backup Details page.

Immediate Backup

You can immediately create a backup of the current point in time. To perform an immediate backup, follow these steps:

  1. Click the All Services > Storage > Backup menu. You will be taken to the Service Home page of the backup.
  2. On the Service Home page, click the Backup menu. You will be taken to the Backup List page.
  3. On the Backup List page, click the resource to perform the backup. You will be taken to the Backup Details page.
  4. Click the Immediate Backup button. The Immediate Backup popup window will open.
  5. Click the Confirm button. The immediate backup will be performed.
  6. Click the Backup History page. You will be taken to the Backup History page.
  7. Check the backup in progress.
Note
  • Immediate backup is possible when the status is Available.
  • Immediate backup is performed as a Full Backup.

5.2.2 - Recover

You can perform a restore using the generated backup’s restore target (backup copy). You can perform the operation on the Backup Restore Target page.

VM Image Recover

You can restore using the backup copy to be restored.

To recover, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to the Service Home page of Backup.
  2. Click the Backup menu on the Service Home page. You will be taken to the Backup List page.
  3. Backup List page, click the resource to perform recovery. Navigate to the Backup Details page.
  4. Click the Recovery Target page. It navigates to the Backup Recovery Target page.
  5. After checking the Schedule and Backup date/time, click the More button of the target you want to recover.
  6. Click the Restore button. Backup Restore popup window opens.
  7. After checking the Backup target and Backup date/time, enter the recovery location, recovery server name, etc.
  • Recovery Location: For remote backup copies, select the recovery location (target server or backup location).
    • Recovery Server Name: Use English letters, numbers, spaces, and special characters (-_) within 63 characters.
    • Server Type: Set the server type.
    • Network Settings: If you are restoring to a different location than the backup target server, configure the network of the recovery server.
    • Security Group: Set the Security Group of the recovery server.
  1. After checking the entered information, click Confirm.
  2. Click the Recovery History page. Go to the Backup Recovery History page.
  3. Check the ongoing recovery tasks.
Caution
  • If it is in Available state, recovery is possible.
  • The original’s Security Group, NAT IP, Delete on termination settings are not restored, so set them after recovery.
  • The original server’s Server Group is not applied to the recovery server.
  • Restored servers cannot use the Rebuild function.
Reference
  • When restoring, a new server is created, and the Block Storage type and Keypair are set the same as the original.

Filesystem Recovery

You can restore using the backup copy of the recovery target. To restore, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to Backup’s Service Home page.
  2. Click the Backup menu on the Service Home page. It navigates to the Backup List page.
  3. Click the resource to perform recovery on the Backup list page. You will be taken to the Backup details page.
  4. Click the Recovery Target page. Navigate to the Backup Recovery Target page.
  5. After checking the Schedule and Backup time, click the More button of the target you want to recover.
  6. Restore Click the button. Backup Restore A popup window opens.
  7. Check the Backup target and Backup date and time, etc.
  8. Click the Server Selection button of the recovery target item. The Server Selection popup window will open.
  9. After selecting the server, click Confirm.
    • Only servers that have configured the Backup Agent can be selected among servers generated at the backup storage location.
    • Only servers that use the same Backup Master and OS as the target server can be selected.
  10. Filesystem After checking the Filesystem to recover from the list at the bottom of the item, enter the Recovery location.
    • Please enter the exact name of the Filesystem being used in the OS.
    • /dev/zero, /dev/null When entered, recovery is impossible.
    • If it includes the following special characters for each operating system, recovery is impossible.
      • Linux: : * < > |
      • Windows: / ? * < > |
    • When Overwrite is selected, files with the same type and name are overwritten. If not selected, those files are excluded from recovery.
  11. After verifying the entered information, click Confirm.
  12. Click the Recovery History page. Navigate to the Backup Recovery History page.
  13. Check the ongoing recovery work.

5.2.3 - Backup Agent Usage

Users can create and manage the agents required to use Filesystem backup in the Backup service.

Create Backup Agent

You can create and use the Backup Agent service in the Samsung Cloud Platform Console.

To create a Backup Agent, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to the Service Home page of Backup.

  2. Click the Backup Agent menu on the Service Home page. It moves to the Backup Agent List page.

  3. Backup Agent List page, click the Create Service button.Backup Agent Creation page will be opened.

  4. Backup Agent Creation page, enter the information required to create the service.

    Category
    Required
    Detailed description
    Target ServerRequiredSelect the target server to create the Backup Agent
    • Click the Select button to select the Bare Metal Server to create the Backup Agent
    Table. Backup Agent Service Information Input Items

  5. Summary Check the detailed information generated in the panel, and click the Complete button.

  • Once creation is complete, check the created resources on the Backup Agent List page.
Caution
  • After creating the Backup Agent, connect to the target server and install the Agent.
  • If the connection status on the Agent installation and Backup Agent detailed information screen is confirmed as successful, you can create a Backup service to backup the Filesystem.
Notice
  • After creating the Bacup Agent service, connect to the Backup target server and install the Backup Agent.
  • After installation is complete, check the connection status on the Backup Agent Details page.

Backup Agent View Detailed Information

Backup Agent service can view and edit the full resource list and detailed information. Backup Agent Details page consists of Details, Tags, Job History tabs.

To view detailed information of the Backup Agent service, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Navigate to the Service Home page of Backup.
  2. Service Home 페이지에서 Backup Agent 메뉴를 클릭하세요. Backup Agent 목록 페이지로 이동합니다.
  3. Click the resource to view detailed information on the Backup Agent List page. Move to the Backup Agent Details page.
  • Backup Agent Detail page displays status information and additional feature information, and consists of Detail Information, Tag, Job History tabs.
    CategoryDetailed description
    Backup Agent statusBackup Agent status information
    • Creating: Creating
    • Available: Created
    • Deleting: Deleting
    • Error: Abnormal state
    Service terminationButton to cancel the service
    Table. Status Information and Additional Functions

Detailed Information

Backup Agent list page allows you to view detailed information of the selected resources and, if necessary, edit the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
Resource NameResource Name
  • In the Backup Agent service, it refers to the Backup Agent name.
Resource IDUnique resource ID of the service
CreatorUser who created the service
Creation timeTime the service was created
EditorUser who modified the service
Modification Date/TimeDate/Time the service was modified
Backup Agent nameBackup Agent name
Backup Master nameBackup management server name
Number of Backup policiesNumber of Backup services connected to the target server
Backup Master IPBackup management server connection IP
Service CategoryService Category of Backup Agent Target Server
Target ServerBackup Agent Target Server Information
  • Server Name:Target Server Name
  • Connection Status: Connection status between Backup Master and server
    • Check Connection Status button click, reconfirm connection status
  • Backup IP: Backup IP information of the target server connected to Backup Master
  • Check Time: Last connection status check time
  • Gateway: Backup Gateway information of the target server connected to Backup Master
Table. Backup Agent detailed information items

Notice
  • After creating the Bacup Agent service, connect to the backup target server and install the Backup Agent.
  • After installation is complete, check the connection status on the Backup Agent Details page.

Tag

Backup Agent List page allows you to view the tag information of selected resources, 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 previously created Key and Value list
Table. Tag Tab Items

Work History

On the Backup Agent List page, you can view the operation history of the selected resource.

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

Backup Agent Cancel

You can cancel the unused Backup Agent.

Caution
  • Available, can only be terminated when in Error state.
  • If there is a Backup service connected to the Backup Agent, it cannot be terminated.
  • Backup policy count is the number of Backup services connected to the Backup Agent. After terminating all connected Backups, terminate the Backup Agent.

To cancel the Backup Agent, follow the steps below.

  1. All Services > Storage > Backup Click the menu. Go to the Service Home page of Backup.
  2. On the Service Home page, click the Backup Agent menu. It navigates to the Backup Agent List page.
  3. Backup Agent List On the page, select the resource to cancel, and click the Cancel Service button.
  4. If termination is completed, check on the Backup Agent List page whether the resource has been terminated.

5.2.4 - Backup Agent Install

Caution

To install the Backup Agent, you must first apply for the Backup Agent service. Please refer to Backup Agent Apply.

To use Agent-based Backup, you need to connect to the target server and install the Backup Agent. After installing the Backup Agent, register the backup through the Backup service.

Pre-preparation work

To install the Backup Agent, we check the installation space, download the Backup Agent file, verify Backup Master/Agent information, and perform other preparatory tasks.

Backup Agent Check Installation Space

The required capacity for installing the Backup Agent is as follows.

OS typePathRequired capacityRemarks
Linux/tmp (temporarily used during installation)3 GB/usr space shortage, possible through linking a separate space #ln -s separate space /usr/openv
Linux/opt3 GBWhen /usr space is insufficient, it is possible to link a separate space #ln -s separate space /usr/openv
Linuxopenv installation path (usually /usr)3~5 GBIf /usr space is insufficient, possible via linking separate space #ln -s separate space /usr/openv
WindowsVeritas installation path (usually C:)3~5 GBIf space on C:\ is insufficient, can be installed on another drive
-installation file10 GB
Table. Required capacity when installing Backup Agent

Backup Agent installation file download

To download the Backup Agent installation file, follow these steps.

  1. All Services > Storage > Backup Click the menu. Go to the Service Home page of Backup.
  2. Click the Backup Agent menu on the Service Home page. You will be taken to the Backup Agent List page.
  3. Click the resource to view detailed information on the Backup Agent list page. It navigates to the Backup Agent details page.
  4. Installation file URL After confirming, go to the URL. You can download the Backup Agent installation file.

Linux OS

If you are using Linux OS, refer to the following example and enter the command.

# cd [download location]
# curl -O installation file → Please insert the copied installation file download URL into the installation file.

Windows OS

If you use Windows OS, you can download using a web browser or Windows PowerShell.

When using an internet browser

After launching the internet browser, enter the copied installation file download URL into the address bar. After moving to the download screen, the download will start.

Reference
  • It may take some time until it moves to the download screen.
  • If you do not go to the download screen, download using Windows PowerShell.

When using Windows PowerShell

  1. Right-click the Windows Start icon, then run Command Prompt (Admin).
  2. Windows PowerShell in administrator mode.
  3. Please enter the command referring to the following example.
# wget "download URL" -OutFile "filename to save"

Check Backup Master and Agent information

To install the Backup Agent, routing settings and Backup Master and Agent information for host file registration are required. On the Backup Agent Details page, check the Backup Master IP, Backup IP, Gateway information. Backup Agent detailed information Please refer.

Setting up routing for communication with Backup Master

To communicate with Backup Master, you need to set up routing in the operating system.

Linux OS - CentOS/RHEL

Linux OS - To set up routing on CentOS/RHEL, follow the steps below.

Reference
  • The IP, Gateway, and Vlan ID information of the Backup Master and Agent used in the routing configuration example are as follows.
    • Backup Master IP: 10.242.8.4
    • Backup IP (Agent IP): 10.252.25.4
    • Gateway (Agent Gateway): 10.252.25.1
    • vlan: 100
  • vlan can be set in the Config file of the Bare Metal Server. For more details, see Local Subnet Setup.
  1. Use the following command to check the backup network Interface information.
    • ip a
    • bash /usr/local/bin/ip.sh
  2. Set up routing using the nmcli command.
    # nmcli con mod "Vlan bond-srv.100" +ipv4.routes "10.252.8.0/24 10.252.25.1"
    # nmcli device reapply bond-srv.100
    
  3. Check that the routing settings have been applied correctly.
    # telnet [Backup Master name] 1556
    

Linux OS - ubuntu

Linux OS - To set up routing on Ubuntu, follow the steps below.

Reference
  • The IP, Gateway, and Vlan ID information of the Backup Master and Agent used in the routing configuration example are as follows.
    • Backup Master IP: 10.242.8.4
    • Backup IP (Agent IP): 10.252.25.4
    • Gateway (Agent Gateway): 10.252.25.1
    • vlan: 100
  • vlan can be set in the Config file of the Bare Metal Server. For more details, see Local Subnet Setup.
  1. Use the following command to check the backup network Interface information.

    • ip a
    • bash /usr/local/bin/ip.sh
  2. 50-cloud-init.yaml Open the file and set up routing.

    # vi /etc/netplan/50-cloud-init.yaml (Add routes to existing content)
      network:
      bonds:
      ...................... omitted
      ethernets:
      ...................... omitted
      vlans:
      bond.srv.100:
      addresses:
      ...................... omitted
      routes:
      - to:10.252.8.0/24
      via:10.252.25.1
      # netplan apply
    
  3. Check that the routing settings have been applied correctly.

    # telnet [Backup Master name] 1556
    

Windows OS

To set up routing in Windows OS, follow the steps below.

Reference
  • The IP, Gateway, and Vlan ID information of the Backup Master and Agent used in the routing configuration example are as follows.
    • Backup Master IP: 10.242.8.4
    • Backup IP (Agent IP): 10.252.25.4
    • Gateway (Agent Gateway): 10.252.25.1
    • ifindex: 100
  • ifindex can be set in the Config file of a Bare Metal Server. For more details, see Setting Local Subnet.
  1. Right-click the Windows Start icon, then run Command Prompt (Admin).

  2. Run Windows PowerShell in administrator mode.

  3. Using the ipconfig, Get-NetAdapter commands, check the backup network interface index (ifindex) setting.

    # ipconfig /all → Check the interface name assigned to the Agent IP.
    # Get-NetAdapter → Refer to the interface name checked above to find the interface index.
    
  4. Set up routing using the NetRoute command.

    # Get-NetRoute -ifindex 100
    # New-NetRoute -ifIndex 100 -DestinationPrefix 10.252.8.0/24 -NextHop 10.252.25.1
    
  5. Check that the routing settings have been applied correctly.

    # telnet [Backup Master name] 1556
    

Register Backup Master information in the hosts file

To register Backup Master information in the hosts file, follow these steps.

  1. Open the host file using a file editing tool.
    • Linux operating system: /etc/hosts
    • Windows operating system: C:\Windows\System32\drivers\etc\hosts
  2. Open the hosts file and register the Backup Master and Backup Agent information (IP, name).
  • After the Backup Agent name, you must add .scpbackup as shown in the following example.
    10.252.8.4 takre1p1bkm1
    10.252.25.4 agent_tgdrhw.scpbackup
    

Add port for Backup Agent (when using Windows firewall)

If you are using the Windows firewall, you need to add the port for the Backup Agent, which communicates with the Backup Master, to the Windows firewall.

The ports and settings to add to the Windows firewall are as follows.

  • Inbound Rule: (TCP) 443, 1556, 13720, 13724, 13782 port
  • Action: allow the connection
  • Profile: domain, private, public select all

Check whether the package is installed (when using RHEL 8)

If you are using RHEL 8, the libnsl package must be installed to install the Backup Agent.

  • Check if the libnsl package is installed using the following command.
    # rpm -qa | grep libnsl
    
  • If the libnsl package is not installed, install the package using the following command.
    # yum install libnsl
    

Backup Agent Install

Install the Backup Agent suitable for the operating system.

Linux OS

To install the Backup Agent on Linux OS, follow the steps below.

  1. Backup Agent 10.1.1 Move to the path where the installation file was extracted and change the permissions of the installation-related files.
    # chmod 755 installs
    # chmod –R 755 NBClients
    
  2. ./install을 실행하세요.
    • [root@bkclientlin ~]# ./install
  3. After the Install description, when confirming whether to proceed with the installation, enter y and press the Enter key.
    Do you wish to continue? [y,n] (y) y
    
  4. When checking the installation progress of Software on the client, enter y and press the Enter key.
    Do you want to install the ~~~~~~~~~~~~ software for this client? [y,n] (y) y
    
  5. When checking the Backup master server name, enter Backup Master name and press the Enter key.
    Enter the name of the ~~~~~~ master server : bkmaster
    
  6. When checking the client server configuration name, enter n and then enter the Agent information.
    • Agent information input required: Backup Agent name.scpbackup (e.g., agent_tgdrhw.scpbackup)
    Would you like to use "bkclientlin" as the configured
    name of the ~~~~~~~ client? [y,n] (y) n
    agent_tgdrhw.scpbackup
    
  7. Check the Master Server information and if there are no issues, enter y.
    Master server [bkmaster] reports the following CA Certificate fingerprints:
    SHA-256 Fingerprint: [BB:38:~~~~~~~~]
    SHA-1 Fingerpritn: [0D:E6:~~~~~~~]
    
    Is this correct [y,n] y
    
  8. When selecting the Java GUI and JRE option, enter 2. Java GUI and JRE package installation will be excluded.
    Choose an option from the list below.
      1) Include the Java GUI and JRE
      2) Exclude the Java GUI and JRE
    
    Java GUI and JRE option: [1,2] (2) :2
    Excluding the installation of Java GUI and JRE packages
    
  9. Verify that the installation was completed correctly.

Windows OS

To install the Backup Agent on Windows OS, follow these steps.

Guide
Backup Agent installation must be performed with the Default Administrator account. If you are not using the Default Administrator account, log in with the Default Administrator account and then proceed with the installation.
  1. After moving to the folder where the Backup Agent 10.1.1 installation file has been extracted, run the Setup.exe file with administrator privileges.
Guide
  • If the installation zip file contains an EEB directory in the format NB_10.4.0.1_ETXXXXXX_1, after installing the Backup Agent, you must proceed with the patch work according to the following procedure.
    1. When the Backup Agent installation is finished, go to the NB_10.4.0.1_ETXXXXXX_1 folder.
    2. eebinstaller_XXXXXXX_1_AMD64.exe Run the file with administrator privileges.
      • If there are multiple files, install all of them.
  1. After selecting the client to install in the client selection popup, click the OK button.
  2. Select Yes in the Vertias NetBackup popup window. The installation popup window opens, and the installation steps are displayed on the left side of the popup.
  3. Welcome When the step description is displayed, click the Next button.
  4. License Agreement When the step description is displayed, select the Agree with the veritas Software License Agreement item, then click the Next button.
  5. Install Type when the step description is displayed, confirm that Install to the computer only is checked, then select Custom installation. When selection is finished, click the Next button.
Notice
If any item other than Install to the computer only is checked, verify whether the program is already installed.
  1. Option When the step description is displayed, verify the installation path and click the Next button. Client option information is displayed.
  • Change… You can click the button to change the installation path.
  1. After checking the Client Options information, click the Next button. Log on information will be displayed.
  2. After checking the Log on information, click the Next button.
    • Safe Abort Option: If a system restart is required, this is an option to halt the installation (optional).
  3. System Name If the step description is displayed, enter the server environment information and click the Next button. Master Server information will be displayed.
    • Client Name: Enter the Agent information. Backup Agent name.scpbackup (e.g.: agent_tgdrhw.scpbackup)
    • Master Server Name: Enter the Backup Master name.
  4. After checking the Master Server information, I recognize the fingerprint for this host. Proceed with the certificate deployment. select the item. When selection is finished, click the Next button.
  5. Security When the step description is displayed, confirm that the certificate deployment succeeded, then click the Next button.
  6. Install When the step description is displayed, after checking the Installation Summary content, click the Install button.
  7. When installation is complete, click the Finish button.

Backup Agent Check Status

When the installation of Backup Agent is finished, perform a communication test with Backup Master and check the status.

Linux OS

To conduct a communication test with the Backup Master on Linux OS, follow the steps below.

  1. After entering the following command, conduct a communication test with Backup Master and check the results.
    • Command: # /usr/openv/netbackup/bin/bpclntcmd -pn
    • The example of the communication test inspection results is as follows.
      # /usr/openv/netbackup/bin/bpclntcmd -pn
      expecting response from server takre1p1bkm1
      agent_tgdrhw.scpbackup agent_tgdrhw.scpbackup 10.252.25.4 52096
      
  2. Samsung Cloud Platform Console에서 All Services > Storage > Backup 메뉴를 클릭하세요. Backup의 Service Home 페이지로 이동합니다.
  3. Click the Backup Agent menu on the Service Home page. You will be taken to the Backup Agent List page.
  4. Click the resource to check the communication test on the Backup Agent List page. You will be taken to the Backup Agent Details page.
  5. Click the Check Connection Status button in the Connection Status item. If it communicates normally with Backup Master, Success is displayed.
  6. Verify that the result values of the Backup Master communication test performed on the OS and Samsumg Cloud Platform Console are the same.
Reference
If the result values of the Backup Master communication test performed on the OS and Samsung Cloud Platform Console differ, please contact the Support Center. Please refer to Inquiry.

Windows OS

To conduct a communication test with Backup Master on Windows OS, follow the steps below.

  1. After entering the following command, perform a communication test with Backup Master and check the results.
    • Command: # [Installation Path]\Vertitas\NetBackup\bin\bpclntcmd.exe -pn
    • The example of the communication test inspection results is as follows.
      # C:\Vertitas\NetBackup\bin\bpclntcmd.exe -pn
      expecting response from server takre1p1bkm1
      agent_tgdrhw.scpbackup agent_tgdrhw.scpbackup 10.252.25.4 52096
      
  2. Click the All Services > Storage > Backup menu in the Samsung Cloud Platform Console. Go to the Backup Service Home page.
  3. Click the Backup Agent menu on the Service Home page. Navigate to the Backup Agent List page.
  4. Click the resource to verify the communication test on the Backup Agent List page. It navigates to the Backup Agent Details page.
  5. Click the Check Connection Status button in the Connection Status item. If it communicates properly with Backup Master, Success is displayed.
  6. Verify that the result values of the Backup Master communication test performed on the OS and the Samsumg Cloud Platform Console are the same.
Reference
If the result values of the Backup Master communication test performed on the OS and Samsung Cloud Platform Console differ, please contact through the Support Center. See Inquiry

Backup Agent Delete

If you do not use the Backup Agent, you must delete the Backup Agent installed on each operating system.

Linux OS

To delete the Backup Agent on Linux OS, follow the steps below.

  1. Stop the Backup Agent service.
    # /usr/openv/netbackup/bp.kill_all
    # /opt/VRTSpbx/bin/vxpbx_exchanged stop
    # /usr/openv/netbackup/bin/vxlogcfg -r -p 51216
    
  2. Delete the Backup Agent installation file.
    # rpm –qa | grep –i VRTS → Backup Agent package check
    # rpm –e VRTSnbcfg
    # /opt/pdde/pddeuninstall.sh –forceclean
    # rpm -e VRTSnbjava
    # rpm -e VRTSnbjre
    # rpm -e VRTSnbclt
    # rpm -e VRTSpbx
    # rpm -e VRTSnbpck
    # rpm -qa | grep -i VRTS → Backup Agent package after confirming, delete remaining package
    # rm -rf /usr/openv
    

Windows OS

To delete the Backup Agent on Windows OS, follow the steps below.

  1. Stop the Backup Agent service.
    # [Installation Path]\Vertitas\NetBackup\bin\bpdown.exe -f -v
    # [Installation Path]\Vertitas\NetBackup\bin\bpps.exe → Check remaining Process and then perform kill
    
  2. Control Panel > Programs and Features: remove the Backup Agent program.
  3. Delete the Backup Agent installation folder.

5.2.5 -

5.3 - API Reference

API Reference

5.4 - CLI Reference

CLI Reference

5.5 - Release Note

Backup

2025.12.16
FEATURE Copy tab and additional features added
  • Backup replication tab added
    • In the Backup detailed page, you can view the original and replica information in the Replication tab.
  • Add download feature for related backup information
    • In the Backup detail page, you can download the Backup history, recovery target, and recovery history list as an Excel file.
2025.07.01
FEATURE Expanded recovery location
  • Expand recovery scope
    • When restoring with an agentless remote backup copy, you can select the restore location (target server or backup copy location).
2025.04.28
FEATURE Backup location and target expansion
  • Expand backup location and target
    • Agentless-based remote backup: You can backup and restore to a different location from the backup target server.
    • Backup Agent feature added: By configuring the Agent, you can back up the filesystem of a Bare Metal Server.
2025.02.27
FEATURE Common Feature Change
  • Samsung Cloud Platform Common Feature Change
  • Account, IAM and Service Home, tags, etc. have been reflected in common CX changes.
2024.12.23
NEW Backup service official version launch
  • We launched the Backup service to provide a service that safely backs up and restores data.
  • Since backup policies include targets, frequency, retention period, etc., users can set backup plans according to their business environment and requirements.

6 - Parallel File Storage

Service Overview

Parallel File Storage is a All NVMe-based high-performance parallel file storage that can process large amounts of data quickly and efficiently.
Storage that can be used in various fields such as AI/ML and big data analysis, distributes data across multiple storage nodes to improve data processing speed and reduce analysis time.

Features

  • High Performance and Reliability: Distributes data across multiple NVMe-based nodes to provide high performance and reliability. High-performance processing is possible regardless of file size, and even if a single node fails, data is safely maintained through other nodes.
  • Large-capacity volume: It can be reliably expanded while online, and its scalability is excellent, allowing use without capacity limits.
  • Snapshot Backup: Through the image snapshot feature, recovery of changed and deleted data is possible. Recovery is performed by using the snapshot created at the point in time you want to recover.

Diagram

Diagram
Figure. Parallel File Storage diagram

Provided Features

Parallel File Storage provides the following features.

  • Volume Name: Users can set names for each volume.
  • Capacity: Volumes can be created with capacities ranging from a minimum of 1TB to a maximum of up to 1,000TB.
  • Connected Resource: Can be connected and used in a Multi-node GPU Cluster.
  • Snapshot: Through the image snapshot feature, recovery of changed and deleted data is possible. Users select a snapshot created at the point in time they wish to recover from the list to perform the recovery.

Components

Volume

Volume (Volume) is the basic creation unit of the Parallel File Storage service and is used as data storage space. Users create a volume by entering a name and capacity, then connect it to one or more Multi-node GPU Clusters for use.
The volume name creation rules are as follows.

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

Snapshot

A snapshot is an image backup of a volume at a specific point in time. Users can view the snapshot name and creation date in the snapshot list to select the snapshot they want to restore, and can recover data that was changed or deleted using that snapshot.
The notes for using snapshots are as follows.

Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00).
  • You can create up to 50 snapshots.
  • Snapshot capacity is included in File Storage usage and incurs charges, so please delete unnecessary snapshots.

Preceding Service

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

Service CategoryServiceDetailed Description
ComputeMulti-node GPU ClusterService providing many GPUs for large-scale high-performance AI computation
Table. Parallel File Storage Preceding Service

6.1 - Overview

Service Overview

Parallel File Storage is a high-performance parallel file storage based on All NVMe that can process large amounts of data quickly and efficiently.

Features

  • Data Processing Speed Improvement: By distributing file data across multiple storage nodes, it improves data processing speed and reduces analysis time.
  • Various Field Utilization: Through fast data processing speed and analysis time, it can be used in various fields such as AI/ML analysis, big data analysis, etc.

Diagram

Diagram
Figure. Parallel File Storage diagram

Provided Features

Parallel File Storage provides the following features.

  • Volume Name: Users can set names for each volume.
  • Snapshot: You can create a snapshot to restore to a specific point in time.
  • Connection Resource: Can be connected and used in a Multi-node GPU Cluster.

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 is the basic creation unit of the Parallel File Storage service and is used as data storage space. Users select a name and capacity to create a volume, then connect and use it in a Multi-node GPU Cluster.
The volume name creation rules are as follows.

  • Starts with a lowercase English letter and can be set to 3 to 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 function, you can recover changed or deleted data. The user selects the snapshot created at the point in time they want to recover from the snapshot list and performs the recovery.

Reference
  • Snapshots can be created up to a maximum of 50.
  • You can recover by selecting a specific snapshot from the snapshot list and creating a new volume based on the snapshot.
Notice
The snapshot recovery feature will be provided later.

Pre-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
ComputeMulti-node GPU ClusterPhysical GPU servers for large-scale high-performance AI computation
Table. Parallel File Storage Preliminary Service

6.2 - How-to guides

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

Parallel File Storage Create

You can create and use the Parallel File Storage service from the Samsung Cloud Platform Console.
To create Parallel File Storage, follow the steps below.

  1. All Services > Storage > Parallel File Storage Click the menu. Go to the Service Home page of Parallel File Storage.
  2. Click the Create Parallel File Storage button on the Service Home page. You will be taken to the Create Parallel File Storage page.
  3. Parallel File Storage creation On the page, enter the information required to create the service.
Category
Required
Detailed description
Volume NameRequiredEnter volume name
  • Start with a lowercase English letter
  • Use lowercase letters, numbers, special character (_) to input 3 ~ 21 characters
  • Generated in the form ‘user input value+{6-character UUID composed of lowercase English letters and numbers}’
  • Cannot be modified after service creation
CapacityRequiredEnter the capacity to use
  • 1 ~ 1000 TB available
  • Only expansion is possible after service creation
TagSelectAdd Tag
  • Up to 50 can be added per resource
  • After clicking the Add Tag button, enter or select Key, Value values
Table. Parallel File Storage Service Creation Information Input Items
  1. Check the detailed information and estimated billing amount generated in the summary panel, and click the Complete button.
  2. When the popup notifying creation opens, click the Confirm button.
    • When creation is complete, check the created resources on the Parallel File Storage list page.
Reference
Parallel File Storage creation can take more than several tens of minutes depending on the service scale.

Parallel File Storage Check Detailed Information

Parallel File Storage service can view and edit the full resource list and detailed information.
Parallel File Storage If you want to check the detailed information of the service, follow the steps below.

  1. All Services > Storage > Parallel File Storage Click the menu. Go to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Navigate to the Parallel File Storage list page.
  3. Parallel File Storage List page, click the resource to view detailed information. It navigates to the Parallel File Storage Details page.
    • Parallel File Storage Details page displays status information and additional feature information, and consists of Details, Snapshot List, Tags, Operation History tabs.
      CategoryDetailed description
      Volume StatusRepresents the status of the volume
      • Creating: In creation
      • Available: Creation complete, server connection possible
      • Extending: Capacity expansion in progress
      • Deleting: Service termination in progress
      • Error Deleting: Abnormal state during deletion
      • Error: Abnormal state during creation
      • Error Extending: Abnormal state during capacity expansion
      Snapshot CreationImmediately create a snapshot at the time of creation
      • Up to 50 can be created
      Service cancellationButton to cancel the service
      Table. Parallel File Storage status information and additional features

Detailed Information

On the Parallel File 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 Parallel File Storage service, it refers to a volume SRN
Resource NameResource Name
  • In the Parallel File Storage service, it refers to the volume name
Resource IDService’s unique resource ID
CreatorUser who created the service
Creation timeDate/time the service was created
Volume nameVolume name
CapacityVolume Capacity
  • Click the Edit button to change the capacity
Mount InformationMount Information
  • Mount Name: Mount name per volume for server connection
    • {Storage IP}:/{Volume Name} is created
  • Mount Account: View button after clicking, entering the password allows you to view the account information and verify the password
Connected ResourcesList of connected resources (Multi-node GPU Server)
  • Resource Type: Service type of the connected resource
  • Resource Name: Name of the connected resource
  • IP: Connected resource IP information
  • Resource Status: Status of the connected resource
  • Connection Status: Connection status of the resource
    • If the connection status is partially successful, verify that the two N/W interfaces for Parallel File Storage connection in the Multi-node GPU Cluster are functioning properly, then disconnect and reconnect in Parallel File Storage to check the status
  • Resources can be added up to a maximum of 300
Table. Parallel File Storage Details - Detail Tab Items

Snapshot List

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

Reference
  • How to create and manage snapshots, please refer to Using Snapshots.
  • You can restore data on a per-file basis using snapshots. For more details, see File-level Restore.
CategoryDetailed description
Snapshot usageTotal capacity of stored snapshots
Snapshot NameSnapshot Name
CapacitySnapshot Capacity
Creation date and timeSnapshot creation date and time
StatusSnapshot status
  • Available: Creation completed, recoverable
  • Creating: Creating
  • Error: Abnormal state
  • Deleting: Deleting
  • Error Deleting: Abnormal state while deleting
  • Restoring: Restoring
MoreSnapshot Management Button
  • Delete: Delete Snapshot
Table. Parallel File Storage Details - Snapshot Tab Items
Reference
Snapshots can be created up to a maximum of 50.

Tag

Parallel File Storage List on the 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, Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the existing list of created Keys and Values
Table. Parallel File Storage Details - Tag Tab Items

Work History

On the Parallel File Storage List page, you can view the operation history of the selected resource.

CategoryDetailed description
Work History ListResource Change History
  • Task date/time, resource type, resource ID, resource name, task details, event topic, task result, verify operator information
Table. Parallel File Storage Details - Job History Tab Items

Parallel File Storage Resource Management

If you need to modify settings in Parallel File Storage or add or delete a connected server, you can perform the operation on the Parallel File Storage Details page.

Edit Capacity

You can expand the capacity of Parallel File Storage.

To modify the capacity, follow the steps below.

  1. All Services > Storage > Parallel File Storage Click the menu. Navigate to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Go to the Parallel File Storage list page.
  3. Parallel File Storage List page, click the resource to modify the capacity. Parallel File Storage Details page, navigate.
  4. Click the Edit button of the Capacity item. The Capacity Edit popup window opens.
  5. After entering the capacity to be expanded, click the Confirm button.
    • You can expand up to a maximum of 1000 TB, including the existing capacity.
  6. When a popup notifying capacity expansion opens, click the Confirm button.

Edit Connected Resources

You can connect resources to Parallel File Storage or disconnect the connected resources.

Notice
  • You cannot modify the linked resource while the linked resource modification is in progress.
  • If communication with the target resource is lost or the connection is impossible, you cannot modify the connection resource.
  • When connecting resources, you can connect up to 300 resources at the same location. If you exceed 300, use the API.

To modify the connection resource, follow the steps below.

  1. All Services > Storage > Parallel File Storage Click the menu. Navigate to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Navigate to the Parallel File Storage list page.
  3. Parallel File Storage List page, click the resource to edit the connected resource. Move to the Parallel File Storage Details page.
  4. Click the Edit button of the Connected Resource item. The Select Connected Resource popup window opens.
  5. After selecting the resource to connect or unchecking the resource to disconnect, click the Confirm button.
    • You can select multiple resources at the same time.
Caution
  • Multi-node GPU Cluster server is connected to Parallel File Storage through two N/W interfaces. To optimize storage performance, please check that both N/W are properly connected.
    • Parallel File Storage Details page, if the resource’s connection status is Partial Success, follow the steps below to verify.
      1. Verify that the 2 N/W interfaces for connecting Parallel File Storage in the Multi-node GPU Cluster are functioning properly.
      2. After disconnecting from Parallel File Storage, reconnect.
      3. Parallel File Storage Details Check the connection status of the resource on the page.
  • When disconnecting, you must first access the server and perform the disconnect operation (Umount, disconnect network drive).
    • If you disconnect without OS operation, a status error (Hang) may occur on the connection server.
    • For detailed information about the server unmount operation, please refer to Unmount Server.
  • When adding a connected server, you must first perform the connection tasks (Mount, network drive connection) on the server.

Parallel File Storage Cancel

You can cancel unused Parallel File Storage to reduce operating costs.
However, if you cancel the service, the service currently in operation may be terminated immediately, so you should proceed with the cancellation after fully considering the impact that may occur when the service is discontinued.

Caution
  • Be careful because data cannot be recovered after termination.
  • If there are resources connected to Parallel File Storage, you cannot cancel. Remove all connected resources before canceling the service.
  • You can only delete when the volume status is Available or Error.

To cancel Parallel File Storage, follow the steps below.

  1. All Services > Storage > Parallel File Storage Click the menu. Go to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Go to the Parallel File Storage list page.
  3. Parallel File Storage list On the page, select the resource to cancel, and click the Cancel Service button.
    • You can go to the Parallel File Storage Details page of the resource to be terminated and delete it individually.
  4. If a popup notifying termination opens, click the Confirm button.
  5. When the termination is completed, check on the Parallel File Storage list page whether the resource has been terminated.

6.2.1 - Using Snapshots

You can create, delete, or recover using snapshots of Parallel File Storage.

Guide
The snapshot recovery feature will be provided later.

Create Snapshot

You can create a snapshot of Parallel File Storage.
To create a snapshot, follow the steps below.

  1. All Services > Storage > Parallel File Storage Click the menu. Move to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Navigate to the Parallel File Storage list page.
  3. Parallel File Storage List page, click the resource to create a snapshot. Go to the Parallel File Storage Details page.
  4. Parallel File Storage Details page, click the Create Snapshot button.
  5. If a popup notifying snapshot creation opens, click the Confirm button.
  6. Snapshot List Click the button. Navigate to the File Storage Snapshot List page.
  7. Check the generated snapshot.
Caution
Snapshot fees are included in the File Storage usage fees.
Reference
You can create up to 50 snapshots.

Delete Snapshot

You can delete the snapshot of Parallel File Storage.
To delete a snapshot, follow these steps.

  1. All Services > Storage > Parallel File Storage Click the menu. Navigate to the Service Home page of Parallel File Storage.
  2. Service Home on the page click the Parallel File Storage menu. Navigate to the Parallel File Storage list page.
  3. Parallel File Storage List on the page, click the resource to delete the snapshot. Parallel File Storage Details navigate to the page.
  4. Click the Snapshot List tab on the Parallel File Storage Details page.
  5. In the snapshot list, click the More > Delete button at the far right of the snapshot to be restored.
  6. Click the Confirm button when the popup notifying snapshot deletion opens.

6.2.2 - Install Agent

To use the Parallel File Storage service, you need to connect to the target server and install the Agent. After installing the Agent, mount on the server and use Parallel File Storage.

Install Agent and Connect to Server (Mount)

Agent installation and server connection consist of six steps. Follow the next procedure.

  1. Agent installation
  2. Account Login
  3. Mount Point Creation
  4. Filesystem Mount
  5. Mount check
  6. fstab registration

Agent Installation

Install the Agent using Mount IP.

Reference
Mount IP can be found in the Mount name item on the detail page of the Samsung Cloud Platform Console.
  1. All Services > Storage > Parallel File Storage Click the menu. Go to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Navigate to the Parallel File Storage list page.
  3. Parallel File Storage List page, click the resource to be used on the connected server. Move to the Parallel File Storage Details page.
  4. Connection Server After checking the server in the item, please connect.
  5. Refer to the following example to install the Volume Agent and proceed with server connection (Mount).
curl <Mount IP>:14000/dist/v1/install | sh
root@RESD-s4sr3h:/# curl http://10.102.160.254:14000/dist/v1/install | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1424  100  1424    0     0  1978k      0 --:--:-- --:--:-- --:--:-- 1390k
Downloading WekaIO CLI 4.2.4.29-hcsf
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 58.7M  100 58.7M    0     0  1079M      0 --:--:-- --:--:-- --:--:-- 1088M
Installing...
Installing agent of version 4.2.4.29-hcsf
The agent is configured to detect cgroups - cgroups v1 not found, cgroups are disabled
Waiting for agent service to be ready
Installation finished successfully
WekaIO CLI 4.2.4.29-hcsf is now installed


## Account Login

Log in using the mount information for server mount.



Reference
You can check the Mount name, Mount account, and password in the Mount information item of the detail page of Samsung Cloud Platform Console.

#weka user login -H root@RESD-s4sr3h:/# weka user login -H 10.102.160.254 Organization (enter name or ID, default: 0) admin_org Username: admin_reg Password: ########### +——————————+ | Login completed successfully | +——————————+


## Mount Point creation

Create a mount point on the server for the filesystem mount.

#mkdir /mnt/weka


## Filesystem Mount

Follow the steps below to mount the filesystem.

1. Use the #ip a command to check the IP and Interface Name information for Mount.

root@RESD-s4sr3h:/# ip a |grep 10.102 inet 10.102.160.248/23 brd 10.102.161.255 scope global ibs4f0.8010 inet 10.102.160.249/23 brd 10.102.161.255 scope global ibP1s8f0.8010


  

Note

The IP information and Interface Name that can be confirmed in the above example are as follows.

  • IP: 10.102.160.10, 10.102.160.11
  • Interface Name: ibs4f0.8010, ibP1s8f0.8010
2. Execute the mount command using the verified IP and Interface Name.

mount -t wekafs / -o net=//mask -o mgmt_ip= /mnt/weka root@RESD-s4sr3h:/# mount -t wekafs -o num_cores=8 -o net:ha=ibs4f0.8010,net:ha=ibP1s8f0.8010,mgmt_ip=‘10.102.160.10+10.102.160.11’ 10.102.160.254/wekafs /mnt/weka Mounting 10.102.161.254/bmtfs on /weka_fs Basing mount on container client Downloading [1/21] http://10.102.160.254:14000/dist/v1/image/envoy-fe-e6b882a6bce3c0de8cd9c7833df1a567.squashfs Downloading [2/21] http://10.102.160.254:14000/dist/v1/image/weka-driver-1.0.0-d10ca9cff59b98778b4314014569e00f.squashfs Downloading [3/21] http://10.102.160.254:14000/dist/v1/image/weka-driver-igb-uio-4.0.0-7eee7dc5b7f1d85a1be0e448d5e97312.squashfs Downloading [4/21] http://10.102.160.254:14000/dist/v1/image/container-s3-tmp-1.57f-9cb61c7e0ae3ca9e2b476c191e4e84ab.squashfs Downloading [5/21] http://10.102.160.254:14000/dist/v1/image/container-smbw-weka-4.7.12.3-9b67132a85a950260f048955dc33c7a9.squashfs Downloading [6/21] http://10.102.160.254:14000/dist/v1/image/weka-drain-tools-2d01044c641816d9002ca594a6ae9d90.squashfs Downloading [7/21] http://10.102.160.254:14000/dist/v1/image/container-ganesha-dev-weka-5-11becf16b21c9635daa23a247340a7bd.squashfs Downloading [8/21] http://10.102.160.254:14000/dist/v1/image/dependencies-1.0.0-9b64fdba87a4d6e6efa9ab5250169ec8.squashfs Downloading [9/21] http://10.102.160.254:14000/dist/v1/image/weka-container-2.3.0-be66bcc7c9739b15cacd910d7cac031e.squashfs Downloading [10/21] http://10.102.160.254:14000/dist/v1/image/weka-hostside-faf9aa30ec9ac7521ffbc9589ac23deb.squashfs Downloading [11/21] http://10.102.160.254:14000/dist/v1/image/api-6f501306831ff9a223a7f706c5a661e1.squashfs Downloading [12/21] http://10.102.160.254:14000/dist/v1/image/weka-s3-3508f2f1afb4900ab11c4772e327b1ac.squashfs Downloading [13/21] http://10.102.160.254:14000/dist/v1/image/weka-ganesha-5c6ef6d08e31f80580f50bab7d1b8134.squashfs Downloading [14/21] http://10.102.160.254:14000/dist/v1/image/dashboard-dfb78995154ab40fb274037ac9fe8a45.squashfs Downloading [15/21] http://10.102.160.254:14000/dist/v1/image/container-samba-weka-4.7.12.3-69835f740573b7ded6faed1dfe737bed.squashfs Downloading [16/21] http://10.102.160.254:14000/dist/v1/image/weka-smbw-8a1430e5f0f2cca6d2a4af603d630882.squashfs Downloading [17/21] http://10.102.160.254:14000/dist/v1/image/ui-1.0.0-5bc747765d326e6e1c3488285822f459.squashfs Downloading [18/21] http://10.102.160.254:14000/dist/v1/image/weka-samba-8102bcf3d3a81f02755cb2e75b1b8d16.squashfs Downloading [19/21] http://10.102.160.254:14000/dist/v1/image/weka-node-fbd17baa570969b6da7e5561f1eb652f.squashfs Downloading [20/21] http://10.102.160.254:14000/dist/v1/image/ofed-b643ca3e4fa06d84416d463afe74a66a.squashfs Downloading [21/21] http://10.102.160.254:14000/dist/v1/image/driver-uio-pci-generic-1.0.0-322a3daa84c41eeb6f0cafd0802fbf50.squashfs Finished getting version 4.2.4.29-hcsf Creating Weka container ‘client’ in version 4.2.4.29-hcsf Preparing version 4.2.4.29-hcsf of container client Base port was not explicitly provided, the container will use 14000 Applying resources Starting container ‘client’ Waiting for container ‘client’ to join cluster Container “client” is ready (pid = 392216) Calling the mount command Cgroups v1 not found, running without cgroups Mount completed successfully



## Mount Check

<code>#df -h</code> Run the command to check the mount status of the filesystem.
root@RESD-s4sr3h:/# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           202G  3.8M  202G   1% /run
/dev/nvme2n1p2  3.5T   37G  3.3T   2% /
tmpfs          1008G     0 1008G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/nvme2n1p1  511M  6.1M  505M   2% /boot/efi
tmpfs           202G  4.0K  202G   1% /run/user/0
/dev/loop0      2.0G   47M  2.0G   3% /opt/weka/logs
tmpfs          1008G   12K 1008G   1% /opt/weka/data/agent/tmpfss/cleanup
tmpfs          1008G  2.0G 1006G   1% /opt/weka/data/agent/tmpfss/client-persistent-tmpfs
tmpfs          1008G     0 1008G   0% /opt/weka/data/agent/tmpfss/cross-container-rpc-the-tmpfs
tmpfs          1008G  4.0K 1008G   1% /opt/weka/data/agent/tmpfss/cleanup_before_stop_and_delete
bmtfs           1.9T  537G  1.3T  29% /weka_fs

## fstab registration

Register fstab so that it automatically mounts on server reboot.<br>
To register fstab, run the <code>#vi /etc/fstab</code> command, then add the following command.

root@RESD-s4sr3h:/# cat /etc/fstab

/etc/fstab: static file system information.

Use ‘blkid’ to print the universally unique identifier for a

device; this may be used with UUID= as a more robust way to name devices

that works even if disks are added and removed. See fstab(5).

/ was on /dev/nvme2n1p2 during curtin installation

/dev/disk/by-uuid/8683a4fb-ee21-47c2-938e-2be0beea2089 / ext4 defaults 0 1

/boot/efi was on /dev/nvme2n1p1 during curtin installation

/dev/disk/by-uuid/92ED-55CC /boot/efi vfat defaults 0 1 /swap.imgnoneswapsw00 10.102.160.254/wekafs /mnt/weka wekafs num_cores=8,net:ha=ibs4f0.8010,net:ha=ibP1s8f0.8010,mgmt_ip=10.102.160.10+10.102.160.11,x-systemd.requires=wekaagent.service,x-systemd.mount-timeout=infinity,_net dev 0 0


# Disconnect server (Umount)

To disconnect the server, first connect to the server and perform the disconnect operation (Umount), then you must disconnect the server from the Console.<br>
To disconnect the server, follow the steps below.

1. **All Services > Storage > Parallel File Storage** Click the menu. Go to the **Service Home** page of Parallel File Storage.
2. Click the **Parallel File Storage** menu on the **Service Home** page. You will be taken to the **Parallel File Storage** list page.
3. **Parallel File Storage List** page, click the resource to disconnect the server. Move to the **Parallel File Storage Details** page.
4. **Connection Server** after checking the server information in the item, connect to the server.
5. Refer to the commands shown in the following example and proceed with the unmount operation (Umount).

umount /mnt/weka

vi /etc/fstab

6.2.3 - File-level recovery

You can restore data on a per-file basis using the generated snapshot.

Use file-level recovery

You can connect to the server and select and recover data.
To perform file-level recovery, follow the steps below.

  1. All Services > Storage > Parallel File Storage Click the menu. Go to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Navigate to the Parallel File Storage list page.
  3. Click the resource to recover the file on the Parallel File Storage List page. Navigate to the Parallel File Storage Details page.
  4. After checking the connected server in the Connected Resources item, access that server.
  5. Check the mount name of File Storage on the server.
    • Mount name is the same as the Mount Point set on the server for the Filesystem’s mount.
  6. Go to the snapshot location under the Mount name.
    # cd /MountName/.snapshots/snapshotName
    
  7. After checking the recovery target file at the Snapshot location, recover it to the required path.
    # cp -arp /MountName/.snapshots/snapshotName/file/{recovery directory}/
    
Notice
If needed, restart or create the container according to the application type.

6.3 - API Reference

API Reference

6.4 - CLI Reference

CLI Reference

6.5 - Release Note

Parallel File Storage

2025.12.16
NEW Parallel File Storage Official Version Release
  • Parallel File Storage service has been officially launched.
    • File data can be distributed across multiple storage nodes to process large-scale data quickly and efficiently.
    • Through fast data processing speed and reduced analysis time, it can be used in various fields such as AI/ML analysis and big data analysis.