Volume Storage Built Beyond a Single VM
Account-level NVMe volumes survive rebuilds. Reattach, clone, or save a backup as a new volume without rebuilding storage.
Walkthrough: hero animation transcript
- Create: A new account-level NVMe volume appears in the dashboard, labeled and unattached, ready to use independently of any VM.
- Attach: The operator selects a running VM and attaches the volume without a reboot or rebuild. The volume binds to the instance and becomes available as a block device.
- Resize: While the VM keeps running, the operator increases the volume’s capacity. The block grows live; the filesystem is then extended inside the VM with no downtime.
- Detach: The volume is unbound from the VM and returns to the account inventory. The VM continues running; the volume retains all its data and identity.
- Restore: From inventory, the volume is attached to a different VM. All data is intact on the new host, with no rebuild of the storage layer required.
Create, rename, clone, delete, and toggle persistence from a single management surface.
Move volumes between VMs without copying data. The pointer moves; the bytes stay put.
Take point-in-time backups of any volume and roll back without touching other disks.
Turn VM disks, backups, and DR recovery points into reusable account-level volumes.
Move data without rebuilding storage
An account-level volume belongs to your account, not to any one VM. Storage and compute are billed and managed separately, so the volume keeps its data and identity when compute is rebuilt or replaced. Each row of the ledger below names a recovery or move action, what it does to the volume, what it costs, and what the operator must do first.
The volume recovery ledger
| Action | Source | Destination | Destructive | Billing | Operator prerequisite |
|---|---|---|---|---|---|
| Revert in place | Volume backup | Same volume rolled back to the backup point | Yes: overwrites target volume If current state must survive, use Save as new volume instead. | No new charge; backup retained per slot retention | Attached VM quiesced; data loss between backup and now is acceptable |
| Save as new volume | Volume backup, saved image, or DRaaS recovery point | New unattached account volume | No: creates a new volume | New volume billed from creation; the source backup, image, or recovery point is unchanged | Sufficient datastore quota; a saved image must still be in the saved-images inventory; a DRaaS point requires DRaaS active on the source VM If the whole workload must move, a DRaaS point can drive a full DRaaS failover instead. |
| Clone a volume | Account volume (detached) | New independent copy, ready to attach | No: original volume unchanged | Clone billed from creation as its own volume | Volume detached from every VM, with no backups held on it |
| Promote to volume (detach & save) | VM data disk | Account-level volume; original VM disk slot freed | No: creates a new volume | Volume now bills independently of the VM | VM stopped or disk detached cleanly |
| Detach & reattach to a different VM | Account volume (live) | Same volume, attached to new compute | No: data preserved | No billing change; volume billed independently | Volume unmounted in source VM; target VM has free slot |
Volumes are priced per GB of NVMe capacity. Drag the storage slider in the Cloud VPS configurator to see the rate at any size. Pair with Backups for point-in-time rollback before a risky disk operation.
Live disk operations on a running VM
- Hot-attach / hot-detach
- Add or move account-level volumes on a running VM with no rebuild required. Filesystem must be unmounted before detach to avoid cache corruption.
- Live resize
- Grow capacity without reboot. One-way: blocks can only grow. After the block grows, extend the filesystem inside the VM.
- Boot order swap
- When a VM has multiple disks, choose which one to boot from. Test OS changes and recovery scenarios without touching the production disk.
- ISO mount
- Attach ISO media for installs or recovery, then detach cleanly when done. Scriptable via the Cloud VPS API.
Move data to replacement compute without rebuilding storage
Detach the account-level volume from one VM and attach it to another so the instance can change while the data stays intact.
Walkthrough steps
- Detach the account-level volume from the source VM.
- Attach the same volume to a different VM in the account.
- Mount the volume on the new host with all existing data intact.
Best fit
Persistent app data that must outlive the VM (databases, content stores, user uploads) where the operator wants to detach, clone, or promote storage without rebuilding it. Also fits migration rehearsal: clone a production volume into a staging VM.
Not a fit
Whole-VM disaster recovery, ransomware rollback that needs OS state, or workloads that need replicated cross-region storage. Volume backups restore one disk at a time; an OS-level failure requires redeploying from a base image and reattaching the data volume.
Better route
DRaaS for replicated recovery points and whole-workload failover. Cloud VPS Backups for point-in-time disk rollback. Cloud VPS overview for whole-VM resilience patterns.
Chat about volume sizingReviews from the Businesses We Keep Online
Cloud VPS Volume Questions
Can I manage volumes independently of VMs?
Volumes are account-level objects. Create, rename, clone, tag, and delete them from a dedicated volumes view, whether or not a VM is attached.
How do I convert a backup into a reusable volume?
Open the backup row in your backup or DR inventory and choose save-as-volume. The platform creates a new volume from the backup data, ready to attach to any VM.
What happens to volumes when I delete a VM?
Persistent volumes survive VM deletion. Non-persistent volumes are removed with the VM. The control panel shows persistence state clearly so there are no surprises.
Can I take backups of individual volumes?
Volume backup lists, statistics, and revert controls are on the volume management surface. Roll back a single volume without touching the rest of the VM.
How does the platform prevent accidental data loss on volumes?
The control panel requires explicit confirmation for destructive actions and blocks deletion when a volume is still attached to a VM or referenced by a backup. You won't accidentally delete a volume that's still in use.
Can I tag volumes for organizational workflows?
Volume tags are readable and editable, so you can label volumes by project, team, or environment and filter them later.
What volume lifecycle operations are available?
Create, rename, clone, delete, and type change. You can toggle a volume between persistent (survives VM deletion) and non-persistent (removed with the VM). Attach, detach, and resize operations are also available, along with boot disk selection when multiple disks exist.
How does volume naming work in the control panel?
Stored names use an internal prefix convention. The control panel strips that prefix automatically, so you see clean, human-readable names in every list and form.
No matching questions found.
How Your VPS Stays Up
- 3×-replicated NVMe: keeps your data on three independent storage servers
- Host failure recovery: restarts affected VPSs on healthy hosts after hardware failure
- Performance Guard: detects congestion and rebalances the cluster automatically
- 24/7 engineer support: reach real people around the clock
Ready to deploy?
Volumes are priced per GB: size yours in the configurator. No long-term contracts.