Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.suji.fr/llms.txt

Use this file to discover all available pages before exploring further.

A snapshot is a full point-in-time copy of your VM’s disk: OS, apps, app data, configs. Stored encrypted, in the EU, away from the live VM.

​
Taking a snapshot

From the Snapshots tab on the instance page:
  1. Click Take snapshot.
  2. Optionally name it (e.g. “before db migration”). If you leave the name blank, we use a timestamp.
  3. The snapshot runs in the background. Status: pending → creating → available.
A snapshot of an active VM is live — apps continue to run while it’s being taken. For absolute consistency on a database-heavy install, stop the app first, snapshot, start it back up.

​
Restoring

Click Restore on any available snapshot. The VM is rebuilt from the snapshot disk; everything that came after the snapshot is lost. There’s a confirm dialog with a “type the VM name to confirm” prompt to prevent accidents. Status flow: running → restoring → running. Takes 2–5 minutes depending on disk size.

​
Retention

WhatRetained
Snapshots you take manuallyUntil you delete them
Termination snapshots (taken automatically when credit balance reaches €0)7 days from creation, then deleted
Snapshots count toward your monthly storage charge — small (GB-scale) but non-zero.

​
Quotas

Default: up to 10 snapshots per VM. Reach the limit and the dashboard refuses to take a new one until you delete an old one. Org admins can raise the cap on request.

​
What snapshots cover

  • ✅ OS, packages, system config
  • ✅ Docker images, containers, networks
  • ✅ App volumes (everything under /var/lib/docker/volumes)
  • ✅ Anything else on the VM’s disk
  • ❌ External resources (Cloudflare tunnel ID — recreated on restore; webhooks pointed at the old subdomain still work since subdomain is unchanged)
  • ❌ Pending app jobs in Suji’s queue (they may run again after restore)

​
Pricing

Snapshot storage is billed monthly per GB. The exact rate is shown on the Snapshots tab and on Billing → Top up. Small VMs typically cost a few cents/month for a couple of snapshots.

​
Best practices

  • Snapshot before risky changes: schema migrations, big version bumps, manual edits to system files.
  • Name them clearly — “pre upgrade to v2”, not “snap1”.
  • Don’t rely on a single snapshot for archival — if you need permanent backups, also export app data (e.g. pg_dump) to off-VM storage on your own schedule.
  • Test restores occasionally — a snapshot you never tested is a guess, not a backup.

​
Next

Resize

Change VM size — auto-snapshots before risky resizes.

VM management overview

Full lifecycle and limits.