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

Return to the regular view of this page.

Overview

Service Overview

File Storage enables servers connected via a network to easily store and share data, making it a storage solution suitable for application environments that use multiple servers.
You can choose the disk type according to the required performance level, and it will automatically expand or shrink based on the user’s data volume without any capacity limits.

Features

  • Free volume usage: The volume capacity automatically expands or contracts based on data creation and deletion without any user configuration. There is no cost for creating the volume; only usage fees for the stored data capacity are incurred.
  • Various Disk Types Available: Users can select a disk type based on their usage purpose. They can use HDDs that store large amounts of data cost‑effectively, SSDs that provide reduced response times and high IOPS performance, and high‑performance SSDs.
  • Snapshot Backup: The image snapshot feature enables recovery of modified or deleted data, and when performing disk backup, snapshots can be stored in a location different from the original. Users select a snapshot created at the desired point in time from the list to perform the recovery.
  • Replication: Creates an identical replica volume at a different location, and users can set the data replication interval. If the original volume becomes unavailable 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 a name for each volume.
  • Disk type: You can select a disk type based on the user’s performance requirements.
    • HDD: Standard volume
    • SSD: high‑performance general volume
    • High‑Performance SSD: Performance‑optimized volume that can be attached to a Multi-node GPU Cluster
  • Protocol: You can select the protocol based on the user’s OS image.
    • NFS: Primarily used on Linux operating systems
    • CIFS: Primarily used on Windows operating systems
  • Flexible Volume Usage: Provides flexible volume sizing based on the amount of stored data without requiring user capacity settings.
  • Connected Resources: can be connected and used from Virtual Server, Bare Metal Server, and Multi-node GPU Cluster.
  • Encryption: Regardless of disk type, all volumes are encrypted with the XTS-AES-256 algorithm.
  • Snapshot: The image snapshot feature allows immediate or scheduled snapshot creation.
    • Retention Count: The number of snapshots retained that are automatically created by the schedule
    • Schedule: Snapshot auto-creation interval
    • Recovery: restore the original volume to the latest snapshot, or select a snapshot at a specific point in time to create a recovery volume
  • Replication: It replicates the volume to another location, and the user can set the replication schedule.
  • Disk Backup: You can store snapshots on a backup-dedicated HDD storage and select the backup location.
  • VPC Endpoint connection: File Storage can be used via a Private Network connection from an external network.
  • Monitoring: usage, IOPS, Throughput, and other monitoring data can be viewed through the Cloud Monitoring service.
  • ServiceWatch Service Integration: You can monitor data using the ServiceWatch service.

Component

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 desired point in time.

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 Server for use.
The volume name generation rules are as follows.

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

Snapshot

Snapshot is an image backup taken at a specific point in time. Using the image snapshot feature, you can recover changed or deleted data or store snapshots in a location different from the original when performing disk backups. Users select the snapshot created at the desired point in time from the snapshot list to perform a recovery.
The following are considerations when using snapshots.

Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00). Snapshots can be created up to a maximum of 800, excluding those generated by schedule. (Automatic creation via schedule is limited to a maximum of 128)
  • Select the snapshot recovery button to restore the File Storage volume to the latest snapshot.
  • If you select a specific snapshot from the snapshot list, you can recover by creating a new volume based on that snapshot.
  • Automatic creation is possible through snapshot schedule configuration.
  • Since snapshot storage is included in File Storage usage and incurs charges, adjust the storage capacity by setting the snapshot retention period.

Preceding Service

This is a list of services that must be pre-configured before creating the service. Refer to the guide provided for each service for details 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 Pre-service

1 - Monitoring Metrics

Cloud Monitoring service termination notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, after the September 2026 release, resource monitoring of the Samsung Cloud Platform via Cloud Monitoring will no longer be possible.

With the new alternative service, you can continuously perform resource monitoring by using ServiceWatch, released in October 2025.
ServiceWatch provides more modern and powerful features, replacing Cloud Monitoring to deliver a smooth monitoring environment.

Detailed information about ServiceWatch: see the ServiceWatch Overview.

File Storage Monitoring Metrics

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

Performance Item NameExplanationunit
Instance StatusFile Storage Volume Statusstatus
Volume UsedUsagebytes
Volume UsageUtilization%
Volume TotalTotal byte countbytes
IOPS [Total]iops(total)iops
IOPS [Read]iops(read)iops
IOPS [Write]iops(write)iops
IOPS [Other]iops(other)iops
Latency Time [Total]Latency (total)usec
Latency Time [Read]Read latencyusec
Latency Time [write]Latency (write)usec
Latency Time [Other]Latency (Other)usec
Throughput [Total]Throughput (total)bytes/s
Throughput [Read]Throughput (read)bytes/s
Throughput [Write]Throughput (write)bytes/s
Throughput [Other]Throughput (Other)bytes/s
Table. File Storage Monitoring Metrics

2 - ServiceWatch Metrics

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

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

Basic Metrics

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

The indicators whose names are displayed in bold below are the indicators selected as major metrics among the basic metrics provided by File Storage. Key metrics are used to configure service dashboards that are automatically generated for each service in ServiceWatch.

Each metric indicates, via the user guide, which statistical value is meaningful when viewing that metric, and among the meaningful statistics, the values shown in bold are the primary statistics. In the service dashboard, you can view key metrics using these primary statistical values.

Indicator NameDetailed descriptionunitMeaningful statistics
statusFile storage volume statusNone-
total_byteTotal bytes of file storageBytes
  • Total
  • Average
  • Maximum
  • Minimum
iops_readIOPS (read)-
  • Total
  • Average
  • Maximum
  • Minimum
iops_writeIOPS (write)-
  • Total
  • Average
  • Maximum
  • Minimum
latency_readRead latencyMicroseconds
  • Total
  • Average
  • Maximum
  • Minimum
latency_writeLatency (write)Microseconds
  • Total
  • Average
  • Maximum
  • Minimum
throughput_readThroughput (read)Bytes/Second
  • Total
  • Average
  • Maximum
  • Minimum
throughput_writeThroughput (write)Bytes/Second
  • Total
  • Average
  • Maximum
  • Minimum
Table. File Storage Basic Metrics