NovaVPSVPS Backup and Restore — The 3-2-1 Pattern on a Root Server
What to back up on a VPS, where copies should live, how snapshots fit in, and the restore test that decides whether your scheme works.
Der Artikeltext ist auf Englisch. Header, Katalog und Kasse sind übersetzt.
Decide what is state
On a typical server the irreplaceable state is small: databases, uploaded files, certificates, configs. The OS is reproducible; restore speed comes from automating its setup (a short Ansible/Cloud-init script beats a golden image you forget to update).
VPS from $8.50/mo. Email, a 12-character password, then a crypto invoice.
Launch nowThe pattern
- 3 copies: live data + on-box snapshot + off-box backup.
- 2 media: local NVMe snapshot for fast rollback; off-box copy on a different account/provider or cold storage.
- 1 tested restore: a calendar entry that actually restores into a scratch directory and diffs.
On NovaVPS
- Snapshots are an add-on at checkout on VPS/Storage — good for pre-change safety, not a backup strategy by themselves.
- For the off-box copy, a Storage VPS ($30/mo for 1 TB NVMe) as a Borg/Restic target keeps backups inside the same no-KYC rails.
- Encrypt at the source (restic/Borg do this natively) — the backup target never needs your plaintext.
Are snapshots backups?
They are fast rollbacks stored on the same platform. For provider-level or ransomware events you want an off-box, encrypted copy too.
How often should I back up?
Databases: continuous archiving or daily at minimum. Files: daily. Test the restore at least quarterly.
Can I back up to NovaVPS Storage from another provider?
Yes — any server can push to your Storage VPS over SSH/SFTP with Borg or Restic.
Ready to launch?
Configure a VPS or dedicated server, set a password, then pay the invoice.
Network
Edge RTT
Uptime · 36h
Complaints · 36h