BLAZINGFAST — VPS BACKUPS AND SNAPSHOTS
Reviewed: 5 October 2026. Setup: 00-index.txt.
Production release: SDK/CLI 0.1.17; contract 2026-10-07.1. Check GET /v1/version and GET /v1/capabilities before using optional workflow features. Strict response validation is enforced.

PURPOSE
Recover supported VPS services using backups or snapshots. They are different
recovery mechanisms; check availability, quota, schedule and actual saved copies.
Do not assume dedicated-server or cPanel backups use the VPS API.

PUBLIC API
GET/POST /v1/vps/{serviceId}/snapshots; snapshot progress and name-specific
rollback/delete endpoints. RAM inclusion depends on supported configuration.
GET /v1/vps/{serviceId}/backup and /backup/schedule; PUT schedule.
POST /backup/run, /backup/cancel, /backup/restore; DELETE /backup.
GET /backup/progress and /backup/restore/progress.
When a write returns operation_url, poll that URL until it finishes. Restore
polling performs the originally requested auto_start and OS synchronization.
An older operation receipt cannot advance a newer restore on the same VPS.
Check guest readiness and application data separately after task completion.
Permissions: vps.read / vps.write and the service's backup/snapshot eligibility.

CLI
bf vps snapshot list SERVICE_UUID
bf vps backup get SERVICE_UUID
bf vps backup schedule-get SERVICE_UUID
bf vps backup progress SERVICE_UUID
Use bf vps snapshot --help and bf vps backup --help for writes.
Only after authorizing it: bf vps backup run SERVICE_UUID
Follow progress instead of launching a second backup.

MCP
Hosted: list_vps_snapshots, get_vps_backup, get_vps_backup_schedule,
get_vps_snapshot_progress, get_vps_backup_progress, get_vps_restore_progress;
request_vps_snapshot, request_vps_snapshot_rollback, request_vps_snapshot_delete,
request_vps_backup_run, request_vps_backup_cancel, request_vps_backup_delete,
request_vps_backup_restore and request_vps_backup_schedule.
Local: bf_vps_snapshot_list/progress and backup get/schedule/progress/restore
progress reads. No snapshot/backup write tools in local MCP.

LIMITS AND SAFETY
Rollback/restore overwrites data; snapshots may pause a VM or consume storage.
Deleting a backup/snapshot removes a recovery option. Do not run a destructive
restore without a verified target and explicit authorization.
Per-VPS backup size/count, shared-pool size/count and quota are different values.
A configured schedule is not evidence a backup completed or can be restored.
Discover retention/limits from the actual service; no universal policy is promised.