How ManaBucket works
Run one command on your server's machine. We back up your worlds on your schedule and keep them as long as you choose.
What happens in a backup
Your server
-
1. Pause saves
Over RCON or the server console. Players stay connected.
-
2. Read the world
Only what changed since the last backup gets sent.
-
3. Encrypt
AES-256 with this world's own key, before anything leaves your server.
ManaBucket storage
-
4. Stored encrypted
Kept on Cloudflare R2, which only ever sees encrypted data.
-
5. Checked weekly
Every stored piece is re-read and verified over 7 weeks.
-
6. Restore anytime
Roll back in place, or move the world to another machine.
Where the keys live
Our master key
Your account key
- Never stored unlocked. The ManaBucket agent holds a key only in memory, during a job.
- Uploads use one-time, exact-size links - the agent can't overwrite or delete backups.
- We can unlock backups, which is how browser restore works. Privacy Policy
Where we look for worlds
Only the usual server folders, and only folders shaped like a Minecraft world.
Folders we check
Somewhere else? Add the folder from your dashboard. We never scan your whole machine.
Machine status
Your machine checks in every few minutes.
Checked in recently.
Missed a check-in or two. Usually a sleeping PC or a network blip.
Silent for a while. After 24 hours we flag it on your Overview.
Pausing saves
Before each backup we pause autosave, then turn it back on once the files are read. Players stay connected.
- Java needs RCON. Without it we still back up, but flag the backup as unpaused.
- Bedrock needs no setup. We pause through the server console when we can reach it, otherwise we take a verified crash-safe copy.
Turn on RCON (Java)
Set these in server.properties, then restart the server. We pick them up automatically. Keep the RCON port closed to the internet - we connect locally.
Who the agent runs as
The agent runs as your server folder's owner, never root. Install needs sudo once.
| Folder owner | Add to the install command | Notes |
|---|---|---|
| Normal user | None | The agent runs as that user. |
| root | --server-user=minecraft | Stop the server first. Steps below. |
| Different users | --user=<name> | Give that user all server folders first. |
| No server yet | None | Re-run with --user=<name> once it's set up. |
If your server runs as root
- 1
Stop your Minecraft server
The game server, not ManaBucket. Type stop in its console, or stop its service, e.g.:
sudo systemctl stop minecraft - 2
Run the install command with --server-user
Copy it from your dashboard. It creates the minecraft user and gives it your server folder.
curl -fsSL …/install.sh | sudo sh -s -- --server-user=minecraft --key=… - 3
Start the server as minecraft
In its systemd unit, add User=minecraft under [Service], then start it. Without systemd, start it with sudo -u minecraft. E.g.:
sudo systemctl daemon-reload && sudo systemctl start minecraft
Backup failed: "files couldn't be read"
Something other than the folder's owner - usually a server still running as root - wrote files the agent can't read. Nothing incomplete is stored. Run the server as the folder's owner, then give it back any files root wrote:
Security
No open ports
Your machine calls us, never the other way round. Nothing on it listens for connections.
Encrypted in transit and at rest
TLS on the wire, AES-256 in storage. Every world has its own repository and key.
Hands off your world
We only change your world files during a restore you start.
Never runs as root
Installing needs sudo once. After that the agent runs as its own limited user and can't run commands we send it.
Common questions
Does it work if I rent from a Minecraft host? +
Not yet. You need to run a command on the server's machine - a VPS, dedicated server, or home PC. A host's control panel isn't enough.
Will backing up lag my server? +
No. Players stay connected; only autosave pauses, and only while we read the files. After the first backup, only changes are uploaded.
What if my machine is off when a backup is due? +
It runs once as soon as the machine is back. If it stays off, Overview flags it as disconnected.
Can I move a world to a new machine? +
Yes. Restoring onto another machine creates a new world there with its own history; the original is untouched. We warn you first if player inventories might reset.
How long are backups kept? +
Your choice per world. By default: daily for a week, weekly for a month, monthly for 3 months. "Back up now" backups are kept until you delete them.
What does the integrity check do? +
Each week your machine re-downloads a seventh of your stored backup data and checks every piece. After 7 weeks the world shows "Verified" and the cycle restarts. It never touches your server, and we email you if anything's wrong.
What happens to my backups if I cancel? +
Nothing is deleted for 30 days. No new backups run, but you can still restore. After that, everything is removed unless you resubscribe.
Do mods and plugins get backed up too? +
Yes, by default the whole server folder is backed up, so a restore brings back a working server. You can switch a world to world-only.
What's the difference between pausing and revoking a machine? +
Pause stops backups until you resume. Revoke disconnects the machine for good; reconnecting needs a fresh install. Existing backups are kept either way.