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

# Block Storage

> Persistent NVMe volumes you can attach to IBEE Solutions servers — create, attach, mount, detach, and delete 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 **Infrastructure → Block Storage** in the portal.

## Key concepts

| Concept              | What it means                                                                                                      |
| -------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Volume**           | A single NVMe block device with a fixed provisioned size.                                                          |
| **Storage type**     | **NVMe SSD**. (**Standard HDD** is listed as coming soon.)                                                         |
| **Site**             | The location the volume is provisioned in. A volume can only be attached to servers in the same location.          |
| **Performance tier** | Set by the volume's size — **Standard** for smaller volumes, **High Performance** for larger ones (above 500 GB).  |
| **Class**            | Storage class shown on the volume — `Balanced` for the standard NVMe tier.                                         |
| **Replicas**         | Number of replicas the platform keeps for durability. Default: `2`.                                                |
| **Volume name**      | The display name. At least 3 characters; 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 a site, size, and name. Also covers deleting a volume.

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

Connect a volume to a server, format and mount it (Linux or Windows), and safely detach when done.

The portal has no resize action for volumes, so choose a size with room to grow when you create one.

## Limits and behavior

* **Maximum size:** set by the storage plan for the site — currently up to 2,000 GB 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)
* [Snapshots](/docs/tools/snapshots)