What to include
At minimum: the server identity/save data, Oxide or Carbon data, server config/cmdline, and any custom maps or plugins not reinstallable in one click. Prefer whole-directory archives over hand-picking files under stress.
Cadence
Daily backups are a common baseline for public servers; increase frequency before wipe day or large plugin changes. Keep multiple generations so a corrupt overnight backup is not your only copy.
Off-box copies
Panel scheduled backups are useful, but also download a recent archive periodically. One disk dying should not erase both live data and backups.
Restore drill
On a spare instance or temporary hostname: stop services, replace data with the archive, start, join, and confirm map + plugins. Do this once before you need it.
Monolith note
Managed plans include scheduled backups in the panel workflow. Still run a restore drill for wipe-critical communities—the panel feature is a tool, not a substitute for verification.
Related: Wipe-day checklist · Rust hosting
Plan calculator · Migration wizard · Free trial
Monolith runs game servers on a verified Ryzen 9 9950X production node with panel, SFTP and scheduled backups.
Share an honest review to help other server owners.