Every Discord bot hosting plan includes a free weekly backup of the container. There is nothing to switch on and nothing to configure.
How it runs
A schedule is created on your container automatically and takes a backup once a week in the early hours. The day of the week and the minute are chosen per container rather than being the same for everybody, so a node is not trying to archive every container it holds at the same moment.
What happens when the slots are full
Your plan has room for a fixed number of backups. The game panel's own behaviour, when a scheduled backup needs room, is to delete the oldest unlocked one. And that rule, left alone, would eventually delete a snapshot you took by hand before an upgrade.
So we do not leave it alone. Our automation never deletes a backup, yours or ours. When the slots are full and the backup the panel would remove is not the one our own last run created, the weekly schedule is switched off instead, and switched back on by itself as soon as a slot frees. A pause is not a failure and nothing is lost; it means your own backups are occupying the space.
Your service page in the client area shows the state directly: slots used against the limit, when the last backup was taken, when the next one is due, and whether the schedule is currently paused.
What we suggest
- Lock a backup you want to keep. A locked backup is never a candidate for deletion by anyone.
- Download one before anything destructive. Reinstall may remove files and changing the runtime rebuilds the container from scratch. A backup that exists only inside the thing you are about to rebuild is not a backup.
- Keep your source in a repository and let the backups carry the data.
The free weekly backup in the knowledge base sets out exactly what the archive contains and, more importantly, what it does not: a database outside the container's filesystem and your environment variables are both excluded.