Conditional takeaway. A snapshot on the same provider account can speed rollback and still fail your recovery goal if the account, region, or disk is gone. Off-box copies, retention length, and who can click Restore are procurement fields—not vibes. AiXVPS does not promise restore time objectives.
Working definitions (buyer language)
| Term | Typical meaning on VPS product pages | Still verify |
|---|---|---|
| Snapshot | Point-in-time image of a disk/instance, often same-provider storage | Crash-consistency, app flush, whether volumes attached to Docker are included |
| Backup (product feature) | Scheduled copies with stated retention; sometimes billed per GB | Location (same site vs other site), encryption, restore UI, exclusions |
| Your export | Application-level dump (n8n export, SQL dump, object storage sync) | Schedule owner, secrets handling, test restore |
Providers use these words differently. Copy the vendor’s definition with date—do not rely on this glossary alone.
Checklist before you pay
- Is the feature a snapshot, a billed backup product, or marketing copy for neither?
- What is retained (days/versions) and what is the restore self-service path?
- Are extra disks, attached volumes, and marketplace image layers included?
- Does restore create a new instance, overwrite in place, or require support?
- Is pricing flat, per GB, or tiered with the disk that holds models/DB data?
- If the account is suspended, can you still export?
- Do you also keep an application export (n8n workflows/credentials strategy)?
Cost field to carry into totals
On the total cost tool and n8n cost walkthrough, treat backup/snapshot fees as their own line. For local AI disks, backup price often scales with provisioned storage—missing that line makes the total incomplete.
Community reports
User threads about “backup didn’t include Docker volume” are prompts to re-read the current provider doc for your SKU. They are not a measured restore-success rate for AiXVPS.