Hyper Layer Game Panel | Understanding How Game Server Backups Work
Introduction
Keeping your game server's data safe is important, so we run backups at a few different levels. This guide explains the difference between the snapshot you can trigger yourself in the game panel and the automated backups we run behind the scenes on our nodes for both your game server files and your databases, so you know exactly what protection is in place and what to expect if you ever need a restore.
Panel Snapshots (Customer-Triggered)
Every game server includes the ability to take 1 snapshot directly from the game panel.
- This snapshot only captures your game server files — it does not include node-level system data, and it does not back up your database.
- It is stored offsite via FTP, with a completely separate provider and data centre from the hot/cold S3 backups described below.
- You can trigger it yourself at any time by pressing the snapshot button, for example before making a risky change to your server.
- You can also automate it by setting up a Scheduled Task in the game panel to run the snapshot for you on a recurring basis, instead of pressing the button manually each time.
The panel snapshot only covers your game server files. It does not back up your database — your database is protected separately by the automated Database Backups described below.
Use the panel snapshot as your own personal "just in case" backup before major changes, such as installing new plugins/mods or upgrading your server version.
Automated Node Backups
In addition to the panel snapshot, we automatically back up every server at the node level. These automated backups are split into two tiers: hot storage and cold storage.
Hot Storage (Daily)
- A backup is taken every day at 3 AM.
- Backups are retained for 7 days on a rolling basis (contention).
- Once a backup is older than 7 days, it is removed to make way for newer daily backups.
- Stored offsite with one S3 provider, in its own data centre.
Cold Storage (Weekly)
- A backup is taken once a week, every Wednesday.
- Backups are retained for 90 days (3 months).
- This gives you a longer-term archive point in case you need to recover something further back than the 7-day hot storage window.
- Stored offsite with a different S3 provider to hot storage, in a separate data centre.
Database Backups
Your game server's databases are backed up separately from your game server files, but follow the exact same hot/cold tiers described above.
Hot Database Backups (Daily)
- A backup is taken every day at 3 AM.
- Backups are retained for 7 days on a rolling basis.
- Stored offsite with the same dedicated S3 provider and data centre as your hot game server file backups.
Cold Database Backups (Weekly)
- A backup is taken once a week, every Wednesday.
- Backups are retained for 90 days (3 months).
- Stored offsite with the same separate S3 provider and data centre as your cold game server file backups.
Where Backups Are Stored
All of your backups are stored offsite, separate from the physical node your server runs on — and each tier is kept with a different provider in a different data centre, so a problem with one location or provider doesn't put every copy of your backups at risk:
- Panel snapshot — stored with a completely separate provider, in its own data centre, via FTP.
- Hot storage (daily) — stored with one S3 provider, in its own data centre.
- Cold storage (weekly) — stored with a different S3 provider, in a separate data centre from hot storage.
This means your backups remain safe even in the event of an issue with the underlying server hardware, or an outage at any single storage provider.
Requesting a Restore
To restore a hot or cold backup (game server files or database), log a support ticket letting us know the date and time of the backup you'd like restored.
- Active services: If your server is still active and in good standing (i.e. you're a paying customer), restores are free.
- Cancelled or terminated services: If your service has been terminated or cancelled, we can still provide you with your backed-up files or restore them for you, at a charge of R200 per game server, since retrieving and restoring data from a cancelled service requires manual work from our team.
Summary
| Backup Type | Trigger | Frequency | Retention | Storage Location | Restore Cost (Active) | Restore Cost (Cancelled) |
|---|---|---|---|---|---|---|
| Panel Snapshot | Customer (manual or scheduled task) | On demand / scheduled (1 snapshot) | Until replaced | Offsite via FTP — separate provider & data centre | N/A — self-service | N/A |
| Hot Storage | Automatic | Daily at 3 AM | 7 days | Offsite via S3 (dedicated provider & data centre) | Free (log a ticket) | R200 per game server |
| Cold Storage | Automatic | Weekly (Wednesday) | 90 days | Offsite via S3 (different provider & data centre to hot) | Free (log a ticket) | R200 per game server |
| Hot Database Backup | Automatic | Daily at 3 AM | 7 days | Offsite via S3 (same as hot storage) | Free (log a ticket) | R200 per game server |
| Cold Database Backup | Automatic | Weekly (Wednesday) | 90 days | Offsite via S3 (same as cold storage) | Free (log a ticket) | R200 per game server |
Conclusion
Between the customer-triggered panel snapshot and our automated daily, weekly, and database backups, your game server data is protected at multiple levels. If you ever need a restore, just log a support ticket with the date and time you need — it's free while your service is active, or R200 per game server if your service has since been cancelled or terminated.