> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ibee.ai/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.ai/docs/_mcp/server.

# Block Storage

> Persistent NVMe volumes you can attach to IBEE Solutions servers — create, attach, mount, expand, and detach block storage volumes.

Block Storage volumes are persistent NVMe disks you can attach to any IBEE Solutions server. They live independently of the server, so the data survives if the server is rebuilt, resized, or deleted. Use them for databases, application state, file shares, or anywhere you need durable storage that outlives the compute.

Volumes are managed under **Products → Block Storage** in the portal.

## Key concepts

| Concept              | What it means                                                                                                        |
| -------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Volume**           | A single NVMe block device with a fixed provisioned size.                                                            |
| **Storage type**     | The performance class — **NVMe (High Performance)**.                                                                 |
| **Storage location** | The region the volume is provisioned in (e.g. `AMR 1`). A volume can only be attached to servers in the same region. |
| **Class**            | Storage tier shown on the volume — `Balanced` for the standard NVMe tier.                                            |
| **Replicas**         | Number of replicas the platform keeps for durability. Default: `2`.                                                  |
| **Volume label**     | The display name. Lowercase letters, numbers, and hyphens only.                                                      |
| **Status**           | `Ready` (idle), `In Use` (attached to a server).                                                                     |
| **Attachment**       | Which server the volume is currently attached to (if any), and the device path inside the guest (e.g. `/dev/vdc`).   |

## What you can do

#### [Create a volume](/docs/infrastructure/block-storage/create-a-volume)

Provision a new NVMe volume — pick size, location, and label.

#### [Attach and detach](/docs/infrastructure/block-storage/attach-and-detach-a-volume)

Connect a volume to a server, format and mount it, and safely detach when done.

#### [Resize a volume](/docs/infrastructure/block-storage/resize-a-volume)

Grow a volume online and extend the filesystem without downtime.

#### [Volume backups](/docs/infrastructure/block-storage/volume-backups)

Snapshot a volume and restore it to a new volume.

## Limits and behavior

* **Maximum size:** 5 TB per volume.
* **Minimum size:** 10 GB per volume.
* **Region-bound:** A volume can only be attached to servers in the same region as the volume.
* **One server at a time:** A volume can be attached to a single server; detach before reattaching elsewhere.
* **Delete on Termination:** `No` by default — volumes survive when their attached server is deleted.
* **Data path:** Inside the guest the volume appears as `/dev/vdb`, `/dev/vdc`, … — the exact path is shown on the volume's **Mount Instructions** tab once attached.

## Typical workflow

1. **Create** the volume in the same region as your server.
2. **Attach** the volume to the server — the portal assigns a device path.
3. **Mount** it inside the guest (format on first use, then mount and add to `/etc/fstab`).
4. **Use** it — read, write, snapshot.
5. When you no longer need it, **unmount** in the guest, **detach** in the portal, and optionally **delete** the volume.

## Related pages

* [Create a volume](/docs/infrastructure/block-storage/create-a-volume)
* [Attach and detach a volume](/docs/infrastructure/block-storage/attach-and-detach-a-volume)
* [Resize a volume](/docs/infrastructure/block-storage/resize-a-volume)
* [Performance tiers](/docs/infrastructure/block-storage/performance-tiers)