Default schedule
| Service tier | Frequency | Retention | Storage |
|---|---|---|---|
| Managed Hosting / VPS | Daily | 14 days | Off-site, EU |
| Managed Cloud (production) | Hourly | 7d hourly + 30d daily | Off-site, EU |
| Game Servers | Daily auto + on-demand | 7 days | Off-site, EU |
| VitalSpark / SparkTranscript | Hourly | 30 days | Off-site, EU |
| Docker Containers (basic) | None default | — | Customer-managed |
For self-managed services (basic Docker, DNS), backup is your responsibility. We can add managed backups as a paid add-on — open a ticket.
Requesting a restore
Open a ticket marked "Restore request" with:
- Service ID.
- Target restore point (date, time, UTC).
- Restore over current state, or to a side-by-side instance for inspection.
Restore times:
- Up to 100 GB — 30 minutes from ticket creation.
- 100 GB – 1 TB — within 2 hours.
- Over 1 TB — call ahead, restoration is staged.
Emergency restores
If production is down and a restore is the fix, mark the ticket Sev-1 and ping us on Discord. Emergency restores skip the queue and start within 15 minutes regardless of plan tier.
Test restores
Exercise a test restore once a quarter so you know procedure and timing. No charge — open a ticket and pick a quiet window.
What is not backed up
- Files you excluded (node_modules, cache directories).
- Data in services you self-manage on top of our infrastructure.
- Anything on ephemeral / scratch disks.