Reboot, rebuild, and snapshot — VPS lifecycle operations.
When to reboot, when to rebuild, and how snapshots save you when you break something.
Three operations you'll do regularly on your VPS. Each has a specific purpose.
Reboot
Soft restart — OS shuts down cleanly, then starts again. Same data, same OS.
When to do:
- After kernel update
- After installing certain packages that require restart
- When the system feels stuck and
systemctl restartof individual services doesn't help - Quarterly anyway, just to flush state
How: Panel → VPS → [your VPS] → Reboot. Or via SSH: sudo reboot.
Takes 30‑60 seconds. The VPS is unreachable during that window.
Hard reboot (force power-cycle)
Like pulling the power cord. Use only when soft reboot fails (kernel hung, OOM killer storms).
Panel → VPS → [your VPS] → Power Off → wait 5 seconds → Power On. Or Force Reboot as a single action.
Risk: unsaved data in OS write buffers gets lost. Filesystems should be journaled (ext4 / xfs / zfs) and recover on boot.
Snapshot
Frozen image of the entire VPS — disk + OS state — taken in seconds.
When to take:
- Before every risky operation (kernel upgrade, configuration change you might want to undo)
- Before every production deploy
- Periodically as offsite-style backup (move snapshot to backup region if needed)
How: Panel → VPS → [your VPS] → Snapshots → Create.
Naming tip: include the date and what you're about to do. 2026-05-03-pre-php-upgrade is much more useful than snapshot-7.
Restoring a snapshot
Panel → VPS → [your VPS] → Snapshots → [your snapshot] → Restore.
Restore wipes current state and reverts to the snapshot. Anything written between snapshot and restore is lost.
Restore takes 30‑120 seconds depending on disk size.
Snapshot retention and cost
- Each snapshot uses storage proportional to your VPS disk
- We charge per GB-month for snapshot storage (small — usually pennies per snapshot per month)
- No automatic deletion; clean up via panel when no longer needed
Rebuild
Wipes the VPS completely and reinstalls from a fresh OS image.
When:
- Switching to a different OS
- Recovering from severe corruption
- Resetting a VPS for a new project
How: Panel → VPS → [your VPS] → Rebuild → pick OS → confirm.
Everything is gone. No undo. Snapshot first if you have anything worth keeping.
Network reset
If networking broke (you locked yourself out via firewall rules, etc.):
Panel → VPS → [your VPS] → Console opens a browser-based console that bypasses SSH. Log in with root, fix iptables / ufw / firewalld, save.
If console is unreachable too: Panel → VPS → [your VPS] → Network → Reset Networking restores default network config.
Resize disk / RAM / CPU
Panel → VPS → [your VPS] → Resize.
Resizing requires a brief reboot (~60s). Disk can only grow, never shrink. RAM and CPU change in both directions.
Resize timings:
- Vertical (more RAM/CPU on same box): ~60s reboot
- Disk grow: ~60s reboot, then
resize2fsruns automatically - Migration to bigger box (when current physical host can't fit): 5‑15 min, with downtime