Resizing and migrating servers

Resizing

vCPU, memory and disk can all be increased from the control panel. The change is applied at the next reboot and billed pro rata against your current term.

curl -X POST https://api.nimbusvps.com/v1/servers/SERVER_ID/resize \
  -H "Authorization: Bearer $NIMBUSVPS_TOKEN" \
  -d '{"vcpu":6,"ram_gb":16,"disk_gb":360}'

Expect 30–90 seconds of downtime for the reboot.

Growing the filesystem

Adding disk grows the block device. The partition and filesystem inside it need extending too — most templates do this automatically on boot via cloud-init, but if yours does not:

growpart /dev/vda 1
resize2fs /dev/vda1        # ext4
# xfs_growfs /             # xfs

Disk cannot be shrunk

This is a limitation of live filesystem resizing rather than a policy choice — shrinking risks data loss in ways that cannot be made safe automatically. If you need a smaller disk, deploy a new server and migrate.

Migrating between locations

Supported, free, and performed as a snapshot transfer. Open a ticket or use the API:

curl -X POST https://api.nimbusvps.com/v1/servers/SERVER_ID/migrate \
  -H "Authorization: Bearer $NIMBUSVPS_TOKEN" \
  -d '{"location":"iceland"}'

Downtime depends on disk size and the link between sites — roughly 10–20 minutes for a 90 GB server, longer for multi-terabyte storage instances.

Changing jurisdiction mid-term

If the new location has a different price index, the difference is prorated over your remaining term — credited if you move somewhere cheaper, invoiced if you move somewhere dearer. There is no penalty either way.