Volume Storage That Outlives Any Single VM
Account-level volumes live outside any single VM. Attach them where needed, detach when not, and keep data intact through rebuilds and instance replacements.
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 snapshots into reusable account-level volumes.
Keep data alive across VM rebuilds
Persistent volumes outlive any single VM. Rebuild the instance, swap the OS, or decommission the host, and your data stays intact and ready to reattach.
Provision on Demand
Create a volume with the size and type your workload needs. Attach it to any VM in your account.
Clone Volumes Instantly
Rename volumes in place or clone them to stand up staging and test copies fast.
Organize by Team or Project
Label volumes by project, team, or environment. Filter and audit by tag as your inventory grows, which helps when multiple teams share the same account.
Grow and move disks without downtime
Add disks, expand disk size, or move volumes between VMs while the VM stays online. No rebuild, no downtime. Manage volumes programmatically via the API for larger fleets.
Expand or Reclaim Live
Add disks to a running VM or remove ones you no longer need. No rebuild, no downtime.
Grow Without Rebooting
Grow a disk’s capacity without rebooting the VM. The resize takes effect on the running instance.
Attach & Detach Volumes
Attach an account-level volume to any VM, or detach it to reuse elsewhere. Data stays intact, and reattaching is instant because no data is copied.
Test OS Upgrades Safely
When a VM has multiple disks, pick which one to boot from. Example: boot from a test disk to evaluate a new OS version without risking the production boot disk.
ISO Attach & Detach
Mount ISO media for OS installs or recovery tasks, then detach when the job is done.
Turn any backup or disk into a reusable volume
VM disks, backups, and DR snapshots can all become reusable volumes you attach to any instance.
Disk to Volume
Detach a VM’s data disk and promote it to an account-level volume. Useful for migrating data between instances or archiving a disk before decommissioning.
Backup to Volume
Turn any VM backup into a standalone volume. Clone production data into a test environment, or freeze a known-good state before a major migration.
Saved Image to Volume
Convert a saved VM image into a reusable volume. Recover data from legacy or decommissioned images without rebuilding the original VM.
DR Snapshot to Volume
Recover data from your DR snapshot inventory into a new volume. After an incident, attach it to a fresh VM and resume operations. See Disaster Recovery for the full DR workflow.
- Any source, whether backup, image, or disk, becomes a mountable volume
- Reattach is instant; no data copy is needed because the volume mounts in place
Choose the right volume workflow
Different volume workflows for different recovery and migration scenarios.
Move data to new compute
Detach a volume from one VM and attach it to another when you are rebuilding compute but keeping data. Ideal for OS replacements, hardware changes, and migration cutovers.
Export a known-good state
Turn a disk, image, backup, or DR snapshot into a reusable volume before a risky change. Attach it to staging, archive it, or bring it back to production later.
Protect and recover one disk
Use volume-level backups when only the data disk needs a rollback. The rest of the VM stays untouched, and tenant-isolation checks apply before any storage action.
For scheduled VM backups and retention policy, see Backups.
Common 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 snapshot into a reusable volume?
Open the snapshot row in your backup or DR inventory and choose save-as-volume. The platform creates a new volume from the snapshot 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 snapshots of individual volumes?
Volume snapshot 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.
Ready to deploy?
$200 in credit for new accounts. Deploy in under 60 seconds.
Need a custom quote? Talk to an engineer.