Skip to content

Volumes

A disk you buy on its own, that outlives any server and can move between your servers on the same host.

Built, not open to the public yet

This feature is built and has been tested against simulated hosts and a test database. It has not yet been proven on real hardware, and nothing here can be ordered today.

Not there yet

  • A volume lives on one host. Volumes that follow a server to another host are planned, not built.
  • Real-hardware testing is still to come.

What a volume is

  • A block disk owned by your organisation, from 1 GiB up to a maximum the panel shows when you add one.
  • It is a separate file on the host, outside any server's own directory. Rebuilding, restoring or destroying a server does not touch it.
  • The first time you attach it, the host that server runs on is fixed. After that it can attach only to servers of your organisation on that same host. Detach it and attach it somewhere else on that host and the data is still there.
  • It takes one of the server's four extra-disk slots, shared with the plan's own extra disks. A plan that sells no extra disks still takes volumes.

Working with volumes

  • Add. Name, size and the server that pays for it. You see the charge first.
  • Attach and detach. The volume then shows up as a new disk inside the server.
  • Make larger. Volumes only grow. A volume on a running server grows while it runs; you still extend the file system inside the server yourself.
  • Delete. The data goes to the host's trash for 72 hours, then is removed. No credit is given.

Every change that writes needs a recent password check. There is a limit on volumes per organisation, which the panel shows.

Price

Billed per GiB each month, at the price in force when you bought it. A later price change reaches new volumes only. Prices: see pricing. Adding charges the rest of the period you have paid for, plus tax, after showing you the amount.

A volume is billed on the server it was bought for, wherever it is attached. If that server is destroyed, the volume is deleted after a grace period, because nothing renews it any more. You are emailed first. Moving the billing to another server is planned, not built.

Before you destroy a server with a volume

Detach the volume first. Restoring a destroyed server from trash while a volume was attached is not proven and may fail until the volume is detached.