Skip to main content

​
Why Downgrades Are Disabled

Shrinking a virtual disk is just as risky as shrinking a physical drive—partitions must be resized perfectly or data can be lost. To avoid accidental corruption, EDBB only allows upgrades.
  • VPS storage is provisioned at the plan’s full size.
  • Shrinking an allocated disk can lose data or leave the filesystem inconsistent.
  • Other resources (CPU/RAM) are tied to the plan profile, so rolling back would require reprovisioning anyway.

​
Safe Path to a Smaller Footprint

1

Deploy the new plan

Order the smaller VPS tier alongside your current service.
2

Migrate workloads

Move data using file backups, rsync or application-level exports. Test the new instance thoroughly.
3

Retire the original VPS

Once satisfied, cancel the old service. This avoids disk resizing risks and keeps downtime minimal.
Keep routine backups (or qcow2 exports) so you can revert quickly if the smaller plan doesn’t meet expectations. Verify that the data and applications fit the smaller destination. A full disk image from a larger VPS is not automatically restorable onto a smaller disk. Test applications, DNS, monitoring and backups before cancelling the original service.