What is a backup?

A backup is a complete snapshot of your server's files at a single moment in time. If something goes wrong later, a bad plugin update, a corrupted world, a griefer who slips through, or a config you edited into a broken state, you can roll the whole server back to exactly how it was when the backup was taken. This page is where you create those snapshots, keep the ones that matter, and restore them when you need to.

What is actually inside a backup?

A backup captures the files that live in your server's own directory. That is nearly everything that makes your server what it is: the world, your installed plugins or mods, every config file, player data, and the logs. What it does not include is anything that lives outside that directory, and the biggest example is a MySQL database. If your plugins store data in a database rather than in flat files, that data sits on a separate database server and is not part of a file snapshot, so it needs its own backup.

Creating a backup

Press create, and the panel packs your current files into a single snapshot. You can give it a name so you remember why you made it, and you can list files or folders to leave out, one pattern per line, the same way a .gitignore works. Skipping a huge world folder or a chunky log directory keeps a backup smaller and faster to make. There is also a "lock" option, which is worth understanding before you use it, so it has its own section below.

Your plan sets how many backups you can keep at once, and the counter at the top of the tool shows where you stand. When you hit the limit, deleting an older snapshot is what frees a slot, so download that one first if you want to keep a copy before it goes. Good moments to take one before you do anything risky:

• Before updating your server version, a major plugin, or a modpack
• Before a large build, a world reset, or bulk file changes
• Before opening the server to the public or a new group of players
• After a milestone you never want to lose, like a finished spawn

Restoring from a backup

Restoring rewinds your server to the state saved in a snapshot. The server is stopped for the duration, and while it runs you cannot control the power, use the file manager, or take new backups, so it is not something to do mid-event. When you start a restore you get one important choice.

Delete all files before restoring wipes the current files first, then lays the backup down on a clean slate. Leave it off and the backup is unpacked over what is already there. Use the clean option when the current files are broken or half-deleted; leave it off when you only want to bring back a few things.

Locking a backup so it is never lost

A locked backup cannot be deleted, by you or by the panel, until you unlock it. Because new backups eventually push against your limit, an unlocked snapshot can be removed to make room. Locking your known-good ones, the clean install, the finished spawn, the state right before a big update, keeps them safe no matter how many backups you make afterwards.

Keeping a copy off the server

Every snapshot on this page still lives on the same infrastructure as your server. That is convenient for quick rollbacks, but a real backup strategy keeps at least one copy somewhere else, so a single failure cannot take out both your server and its backups at the same time. The download button hands you the snapshot as a compressed archive you can save to your own computer or upload to cloud storage.

The habit worth borrowing from the professionals is the 3-2-1 rule, and it is simpler than it sounds:

• 3 copies of anything you care about
• 2 different types of storage
• 1 of those copies kept off-site, away from the server

For most Minecraft servers that is as easy as: the live world, a backup here on the panel, and one downloaded copy sitting in your Google Drive or on your PC. It costs nothing and it is the difference between a bad afternoon and losing months of work.

Backing up to Google Drive

To make that off-site copy automatic, this panel can back up straight to your own Google Drive. You connect your Google account once, and from then on the panel compresses your files and uploads them into your personal Drive, where they count against your Drive storage rather than the server's, and stay fully under your control. It is the cleanest way to keep snapshots somewhere completely separate from the machine your server runs on.

There is also an in-game route worth knowing about. DriveBackupV2 is a plugin you install on the server itself, and it runs its own scheduled backups and uploads them to Google Drive, Dropbox, OneDrive, or an FTP target from inside the game. The panel's snapshots and a plugin like this are not either-or; running both means one backup system does not depend on the other.

Building a backup routine

The best backup is the one you never have to remember to make. Rather than relying on yourself to click create before every risky change, set a schedule to take one automatically on a regular cadence, lock the milestones you cannot lose, and keep one copy off the server. Done once, that routine quietly protects everything you build from then on.