Backups are the boring, unglamorous task that saves your server when disaster strikes — a bad update, a corrupted database, a compromised script, or plain human error. If you're not backing up, you're one bad moment away from losing everything. Here's how to do it right.
Why backups are non-negotiable
Things that can wipe out or break your server:
- A bad artifact or update that breaks everything
- Database corruption losing all player data
- A backdoored script compromising your server
- Accidental deletion or a botched config edit
- Hosting failure
Without a backup, any of these can mean starting over and losing your community's progress. With one, you restore and move on. Backups turn catastrophes into inconveniences.
What you need to back up
Two things matter most:
1. Your server files — the whole server folder: resources, configs, everything that makes your server *your server*. This captures your scripts, settings, and structure.
2. Your database — arguably even more critical. Your database holds all player data: characters, money, inventory, properties, progress. Losing this means losing your players' investment in your server, which is community-ending. Back up the database regularly and often.
How to back up your server files
- Copy the full server directory to a safe location — ideally somewhere separate from the server itself (another drive, cloud storage).
- Do this before any major change — updating artifacts, adding significant scripts, big config edits.
- Keep multiple versions so you can roll back to a known-good state, not just the most recent (which might already be broken).
How to back up your database
The database changes constantly as players play, so it needs regular backups:
- Export/dump your database regularly using your database tools (phpMyAdmin, mysqldump, HeidiSQL, or your host's tools).
- Automate it if possible — scheduled database backups mean you don't rely on remembering.
- Store dumps safely, ideally off the server machine.
- Back up frequently — the more active your server, the more you lose between backups. Daily is sensible for an active server.
Best practices
- The 3-2-1 idea: keep multiple copies, in more than one location. A backup on the same drive that fails is no backup.
- Back up before every risky change. Updates and big edits are exactly when things break.
- Test your backups. A backup you can't restore is worthless — occasionally verify you can actually recover from one.
- Keep some history. Multiple dated backups let you go back past a problem you didn't notice immediately.
- Automate what you can. Manual backups get forgotten; scheduled ones don't.
Backups and updates go together
The safest update workflow is: back up → update → test → keep the backup until you're sure it's stable. If the update breaks something, you roll back instantly. This single habit prevents most "my server is ruined" disasters.
Recovery peace of mind
Running reliable, well-maintained scripts reduces how often you'll *need* your backups — but you should always have them. At Viper Development, our scripts are stable and actively maintained, and if an update ever causes trouble, our support is there to help. Browse our scripts → or join our Discord.