---
title: "File Storage Product Description"
sidebar_label: "Description"
sidebar_position: 1
description: "How File Storage works, types and limits of File Storage"
---

import Formbricks from '@theme/MDXComponents/Formbricks'
import {CustomTable} from '@selectel/docux/components'

# File Storage Product Description

Selectel File Storage is a fault-tolerant, scalable file system for data storage. It can be connected to:

* [to cloud servers](/cloud-servers/);
* [dedicated servers](/dedicated/) (except for the Chipcore Line);
* [Managed Kubernetes cluster nodes](/managed-kubernetes/).

File Storage can be connected to several products simultaneously, including those in different [pools](/infrastructure/locations.mdx#pool). For example, you can connect the storage to a dedicated server in the SPB-2 pool and a cloud server in a segment of the ru-7a pool. Both servers will be able to use the storage simultaneously.

File Storage is powered by [cloud platform network volumes](/cloud-servers/volumes/about-network-volumes.mdx) with triple replication of disk volumes.

You can work with File Storage in the [control panel](https://my.selectel.ru/vpc/default/file-storage/), via [OpenStack CLI](/cloud-servers/tools/openstack-cli/) or [Terraform](/terraform/providers/).

The product supports [user types and roles](/access-control/access-management.mdx), [projects](/access-control/projects/about-projects.mdx), and [project limits and quotas](/access-control/projects/quotas.mdx).

Records of File Storage operations are saved in [audit logs](/audit-logs/about-audit-logs.mdx).

## Protocols \{#protocols}

Supported protocols:

* NFSv4 — for connecting the storage to servers running Linux and other Unix systems;
* CIFS SMBv3 — for connecting the storage to Windows servers.

## Limits and restrictions \{#limits-and-restrictions}

The minimum File Storage size is 50 GB and the maximum is 50 TB.

Throughput values and read/write IOPS limits depend on the File Storage type.

File storages of the same type in different [pool segments](/infrastructure/locations.mdx#pool) may have different limits. For example, if two File storages with the SSD Universal type are in different segments (the first in ru-1c and the second in ru-8a), their limits will differ.

You can [test File Storage performance](/file-storage/manage/benchmark-storage.mdx).

<CustomTable>
  <table data-sticky>
    <thead>
      <tr>
        <th />

        <th>HDD<br />Basic<br />(all available<br />pool segments)</th><th>SSD<br />Universal</th><th>SSD<br />Fast</th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <th>Throughput<br />throughput<br />(read,<br />4 MB blocks)</th><td>40 MB/s<br />(for NFSv4)<br /><br />100 MB/s<br />(for CIFS<br />SMBv3)</td><td>200 MB/s</td><td>300 MB/s</td>
      </tr>

      <tr>
        <th>Throughput<br />throughput<br />(write,<br />4 MB blocks)</th><td>100 MB/s</td><td>200 MB/s</td><td>500 MB/s</td>
      </tr>

      <tr>
        <th>Number of<br />operations<br />(read,<br />4 KB blocks)</th><td>320 IOPS</td><td>7000 IOPS</td><td>25000 IOPS</td>
      </tr>

      <tr>
        <th>Number of<br />operations<br />(write,<br />4 KB blocks)</th><td>120 IOPS</td><td>4000 IOPS</td><td>15000 IOPS</td>
      </tr>
    </tbody>
  </table>
</CustomTable>

## File Storage types \{#file-storage-types}

* HDD Basic — storage for large amounts of data that do not need to be frequently read or overwritten, such as backups, archives, or documents;
* SSD Universal — primary storage for data if you cannot connect a disk. Also suitable for storing data sets and models in machine learning clusters and storing (raw) data for high-performance computing. Can be used in Kubernetes as a Persistent Volume with the ReadWriteMany access mode (mounting the volume to multiple nodes);
* SSD Fast — storage with increased I/O performance. Also intended for storing data sets and models in machine learning clusters and for storing (raw) data for high-performance computing. Can be used in Kubernetes as a Persistent Volume with the ReadWriteMany access mode (mounting the volume to multiple nodes).

File Storage types differ in throughput values and number of read and write operations. See the [Limits and restrictions](#limits-and-restrictions) table for details.

Different File Storage types are available in different [pool segments](/infrastructure/locations.mdx#pool). You can check type availability in the [File Storage](/infrastructure/product-availability-by-location.mdx#file-storage) availability matrix.

<Formbricks />