Media volumes

Product images and everything else under pub/media live on a block volume attached to your application server, mounted at shared/pub/media and symlinked into each release.

It is created on your first deploy at 20 GB.

Why a separate volume

Two reasons, and both matter:

• Releases come and go. pub/media is symlinked out of the release into shared storage, so it is not re-uploaded or lost each deploy.
• The volume outlives the server. When you tear down an environment, the servers are destroyed but the volume is kept. The next deploy re-attaches and re-mounts it, and your product images are still there.

The volume is deleted only when you delete the site.

Growing it

Overview → Storage → Grow storage. Pick a new size, up to 1000 GB. Nautvia resizes the volume and expands the filesystem while the store keeps running — no downtime, no deploy needed.

Volumes only grow. There is no way to shrink one; the provider does not support it. If you over-provision, the only route back is a new environment.

What it costs

Storage is metered hourly at the rate on the pricing page, for the size you provisioned rather than the space you used — it is a disk, and the disk is reserved whether or not it is full. It is billed whether or not it is attached to a running server, which is the trade for surviving a teardown.

See Plans and billing.

Checking usage

The Metrics tab shows how full the media volume is alongside the server's own disk. If it is filling up, the usual culprits are cached image resizes and old imports:

bin/magento catalog:images:resize
du -sh pub/media/* | sort -h | tail -20

Run these from the Commands tab.

Backups do not cover media

Nautvia backs up your database daily. It does not back up the media volume.

If your product images only exist here, they exist in one place. Keep your own copy — sync pub/media somewhere over SSH on a schedule you control. This is stated plainly in the Terms too, because it is the gap most likely to hurt.