Cloud VPS Backups for Fast Disk Recovery
Every Cloud VPS includes 1 volume backup. Capture a disk before a risky change, restore it in place, or export the recovery point into reusable volume storage.
-
Capture
Take a block-level point-in-time image of any attached volume from the control panel or API.
-
Choose path
Restore in place to roll back that disk, or export to a reusable volume for staging or archive.
-
Recover
Volume returns to its captured state. Other disks and the VM are unaffected.
Every VM includes 1 backup. Create point-in-time restore points on demand or set a recurring schedule.
Back up any attached volume independently. Restore that disk to a prior point without rolling back the rest of the VM.
Set daily, weekly, or monthly backup schedules. Choose how many of each to keep and pick your preferred hour and day.
Export any backup as a standalone volume — ready to attach to a different VM or keep as an archive.
Choose the recovery job first
Match the failure to the narrowest restore that solves it. Each next step links to the mechanism behind it. Time estimates assume typical disk sizes (50–200 GB); larger volumes scale roughly linearly.
| Recovery job | Use this when | Setup effort | Operational control | Next step |
|---|---|---|---|---|
| Recommended Capture before a risky change | Running maintenance, a migration, or a config edit where you want a rollback point.Included slot on every VM. | None. One click in the control panel. | Full. You choose when to capture and when to restore. | Capture · seconds |
| Restore one disk in place | One attached volume has bad or corrupted data; the rest of the VM is healthy.Other disks and the VM stay running throughout. | None. Trigger restore from the control panel. | Per-volume. Only the restored disk changes. | In-place restore · minutes |
| Export a copy for staging or archive | You need a clean copy for staging, migration rehearsal, or long-term archive without touching the source.For a permanent archive, converting the backup to a volume frees its slot for the next capture. | Low. Export creates a new billable volume. | Full. Source backup remains intact; the exported volume is independent. | Export · ~10–30 min |
| Whole VM compromised or unbootable | The system disk is corrupt or the VM will not boot from its current state. | None. Redeploy from a base image, then restore the data volume from backup. | Data-volume scope. Reattach the restored volume after the OS is back online. | Redeploy + reattach · 15–60 min |
| Keep data independent of any VM | Data must outlive the VM or be shared across multiple VMs. | Low. Provision a Volume Storage resource. | Full. Volumes persist independently of any VM. | Compare Volume Storage |
What the included backup covers
Every VM ships with one backup slot — reserved space for one captured recovery point. Here is what it covers, what it does not, and where the edges sit.
- Included slot
- One volume backup per Cloud VPS, attachable to any single attached disk; add more from the control panel.
- Where backups live
- Separate from the source volume’s storage. A backup survives the failure of the host running your VM and stays available for restore.
- Retention
- A captured backup persists until you replace or delete it — slots never expire on their own. Enable a backup schedule (daily, weekly, or monthly) to rotate captures automatically and choose how many of each to keep.
- Restore overwrite scope
- Restore replaces the entire target volume. Other attached volumes and the VM itself are unaffected. The previous content of the target volume is gone after restore.
- Export billing
- Exporting a backup creates a new volume billed at standard Volume Storage rates while it exists. The original backup keeps its slot until you replace it.
- Application consistency
- Block-level capture of the disk at the moment of the call. For databases or transactional services, pause writes first with an application-level flush (e.g.
FLUSH TABLES WITH READ LOCKfor MySQL,fsfreezefor the filesystem) before capture, or restore from a logical dump. - Scheduling
- The control panel includes both on-demand manual backup actions and controls to enable and configure automatic backup scheduling (daily, weekly, or monthly). Policy-driven and programmatic capture is also available through the Cloud VPS API.
- “Near-instant” qualified
- The control-panel backup call returns in seconds and the recovery point is logically captured immediately. Background data movement to the recovery target completes shortly after, depending on volume size; the captured point is consistent regardless of when the background work finishes.
How restore and export work
Volume backups capture one disk at a specific moment. Restore the disk in place when production needs rollback, or export the backup to a reusable volume when you need a clean copy for staging, migration, or archive.
- Included backup usable on any attached volume
- Block-level, near-instant capture per volume
- Restore in place from the control panel
- Export a backup into reusable account-level volume storage
Each row describes one backup recovery path and the result it creates.
Return one attached disk to the captured state while the VM and other volumes stay untouched.
Create an account-level volume you can attach to another VM for staging, migration, or archive.
The exported copy lives independently, so you can test recovery without consuming the original point in time.
Cloud VPS Backup Questions
Is a backup included with every Cloud VPS?
Yes. Every Cloud VPS includes 1 backup at no extra cost. You can configure it on any schedule (daily, weekly, or monthly) or use it as a manual on-demand backup. If you need more than 1 backup, additional backups are available as an add-on.
Does the control panel support both manual and scheduled backups?
Yes. The control panel includes both on-demand manual backup actions and controls to enable and configure automatic backup scheduling (daily, weekly, or monthly). Every Cloud VPS includes one backup slot. Additional slots are available as an add-on. Backups are near-instant because they capture data at the block level.
How do volume backups differ from disaster recovery storage?
Volume backups capture the state of an individual disk at the moment of the call and let you revert that disk independently of other volumes or the VM itself. Disaster recovery storage (DRaaS) adds atomic whole-server snapshots with hourly and daily recovery points on isolated backup nodes, restored for you on request, for broader resilience goals. They serve different recovery scenarios.
Can backups be converted into reusable volumes?
Backup rows include a save-as-volume action that creates a new account-level volume from the backup data, ready to attach to any VM.
How do I recover from a failed Cloud VPS?
Volume backups use the revert action from the volume management surface to roll an individual disk back to its captured state. If the system disk is unbootable, redeploy from a base image, then reattach the restored data volume. Togglebox does not sell VM-level backups; recovery is composed from volume backups plus a base-image redeploy when needed.
What controls exist for backup retention and cleanup?
You can delete individual volume backups from the backup list to reclaim space and stay within quota as your backup inventory grows.
Does automatic backup scheduling replace disaster recovery?
No. Scheduled backups are a continuity aid that complements explicit DR architecture. Align your backup cadence with environment criticality and pair it with DR for full resilience.
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?
Deploy in under 60 seconds. No long-term contracts.