For running servers

Reliable offsite backups for your Minecraft server

Set up automated backups, restore workflows, and Discord feedback without spending hours in docs and trial-and-error.

This guide shows you step by step how to integrate itzg/mc-backup into an existing Docker-based server and configure it for Google Drive, OneDrive, Dropbox, S3, SFTP, and more.

For operators with a running itzg/minecraft-server setup.
For anyone who wants backups, restore, retention, and offsite storage configured properly.
For teams who want successful and failed backups visible in Discord immediately.
For admins who prefer proven Compose examples over raw documentation.
Go to checkout

Pay once, get instant access, and receive all future updates.

Based on the public itzg/mc-backup image – we provide the practical implementation and ready-to-use configurations.

What you are buying

Not the image. The finished workflow.

The public Docker image stays free. You pay for the curated implementation, tested examples, and a structure that gets you operational quickly.

Concrete integrations

Configurations for cloud storage, Discord notifications, and typical Docker-based server setups.

Less research

Skip scattered documentation, trial-and-error, and unnecessary misconfiguration.

Better operations

Treat backups, restore, and retention as a reliable process instead of disconnected one-off commands.

Automated backups

for Google Drive, OneDrive, Dropbox, WebDAV, S3, SFTP, and local storage

Step-by-step setup

with practical configuration examples instead of dry reference text

Discord feedback

so you immediately know whether backups succeeded or failed

Proof

What the workflow looks like in practice

What matters is visible outcomes and a structure you can move into your setup right away.

Backup notifications on Discord
Backup status directly in Discord so you can immediately see whether everything worked.
GitHub repository
All guides clearly structured in the GitHub repository and ready to use right away.

Included

What is included with access

You do not just get isolated snippets. You get a usable repository with clear paths for operations and restore.

Provider-specific guides

Google Drive, OneDrive, Dropbox, S3, SFTP, WebDAV, and local targets.

Compose and env examples

Directly adaptable configurations that you can merge into your setup.

Discord feedback

Templates for success, failure, and status messages in day-to-day operation.

Restore and operations guidance

How to think about recovery, schedules, and retention as one workflow.

Why this guide

Why this guide?

The value is not the image itself. It is the time saved, the clarity, and the operational result.

Save valuable time

Instead of digging through documentation for hours, you get ready-made, tested configurations.

Transparent & honest

The Docker image is public. Our guide saves you the research and gives you solutions you can use immediately.

Updated regularly

We keep the guide current so you benefit from future updates as the workflow evolves.

Checkout

Secure checkout

After purchase you get immediate access to the guide repository. If checkout does not load right now, you can retry directly or contact us.

FAQ

Frequently Asked Questions

Transparency

About the Docker image

Transparency is part of the offer: the underlying backup image is public. The value of our guide is the curated implementation.

The Docker image itzg/mc-backup is publicly available on GitHub. The official documentation shows all available configuration options.

Our guide bundles the practical implementation: cloud storage, Discord notifications, operational workflows, and examples you can use immediately in one place.

These Docker images are developed and maintained by itzg. If you appreciate his work, you can support him on GitHub Sponsors.

setupmc.com is not affiliated with itzg's "Minecraft on Docker" project.