Minecraft server backups give you a recovery point if a world becomes damaged, a plugin or mod update causes problems, files are accidentally changed, or you need to roll back your server.

This guide explains how to safely back up and restore a Down Side Hosting Minecraft Java server.

Creating regular backups is a good idea, especially before making major changes.

Create a backup before:

• Updating Minecraft
• Updating Paper, Purpur, Spigot, Forge, Fabric, or NeoForge
• Installing or updating plugins
• Installing or removing mods
• Updating a modpack
• Uploading or replacing a world
• Changing major configuration files
• Removing player or world data
• Troubleshooting a serious server problem

Important: A backup is most useful when it was created before the problem occurred.

For a complete server backup, keep copies of important files such as:

• World folders
• Player data
• server.properties
• Plugin files and plugin data
• Mod files and configuration
• Modpack files
• Whitelist and operator information
• Server configuration
• Databases stored inside the server files
• Other custom files used by your server

A full backup is usually safer than copying only one or two files.

For the safest manual backup, stop the Minecraft server first.

Open your Down Side Hosting server panel and click:

Stop

Wait until the server has completely stopped.

This helps make sure Minecraft finishes writing world and player data before you copy the files.

If the Backups section is available for your server, you can use it to create a server backup through the Down Side Hosting panel.

Open your server and locate:

Backups

Create a new backup and give it a useful name.

For example:

Before Plugin Update

or:

Before Minecraft Upgrade

Use names that make it easy to identify why the backup was created.

Instead of:

backup1

consider using:

Before-1.21-Update
Before-Modpack-Update
Before-New-Plugins
Working-Server-Backup

A clear name can save time when you need to restore an older version later.

Do not assume a backup is complete immediately after starting it.

Wait until the panel reports that the backup has completed successfully.

Avoid making major server changes while an important backup is still being created.

You can also make a manual copy of your Minecraft server files.

Open the Files section of your Down Side Hosting server panel.

For a complete manual backup, copy or archive the files you want to preserve.

Depending on your server, these may include:

world/
world_nether/
world_the_end/
plugins/
mods/
config/
server.properties
whitelist.json
ops.json

Your server may contain additional files that are important to its specific configuration.

If you only need to preserve the Minecraft world, back up the world folder configured by:

level-name=

in:

server.properties

For example:

level-name=world

normally means the primary world folder is:

world/

Paper, Purpur, Spigot, and related server software may use separate folders for dimensions.

For example:

world/
world_nether/
world_the_end/

If you want a complete world backup, preserve all required dimension folders.

Do not back up only world/ and assume the Nether and End are automatically included.

For Forge, Fabric, NeoForge, and modpack servers, backing up only the world may not be enough.

Modded worlds can depend on:

• Mods
• Mod versions
• Configuration files
• Scripts
• Custom dimensions
• Mod-specific data

For a modded server, a complete server backup is strongly recommended before changing the mod list or modpack version.

Plugins may store important information in:

plugins/

This can include:

• Permissions
• Economy data
• Player homes
• Claims
• World protection
• Configuration
• Local databases

If you are backing up an important Paper, Purpur, or Spigot server, preserve the plugin data along with the world.

Some plugins use an external MySQL or MariaDB database.

A normal server-file backup may not contain data stored in an external database.

If your server depends on an external database, that database should have its own backup plan.

Examples can include:

• Economy information
• Permissions
• Player statistics
• Network-wide plugin data

If your Down Side Hosting server has a backup available through the panel, open the Backups section.

Choose the backup you want to restore.

Before restoring:

• Confirm you selected the correct backup
• Stop the Minecraft server
• Understand that current files may be replaced by the older backup

Then use the available restore option for that backup.

Suppose you create a backup on Monday and restore it on Friday.

Anything that happened after the Monday backup may be lost.

That can include:

• New builds
• Player inventories
• Plugin data
• Configuration changes
• Mod changes

Only restore when you understand which version of the server you are returning to.

If possible, create a backup of the current server before restoring an older one.

For example:

Current-Before-Restore

This gives you another recovery point in case you later discover that the current files contained something you still needed.

If you have a manual world backup:

1. Stop the server.
2. Back up the current world.
3. Upload the saved world.
4. Make sure the folder name is correct.
5. Check level-name in server.properties.
6. Start the server.
7. Verify that the correct world loaded.

For more information:

How to Upload a Minecraft World to Your Down Side Hosting Server

For a full manual restore, the safest method is generally to restore the complete set of files that belonged together.

This is especially important for:

• Modpacks
• Heavily modded servers
• Plugin-heavy servers
• Servers with custom configuration

Mixing old and new files can introduce compatibility problems.

For example, avoid restoring:

Old world

while keeping:

New incompatible modpack files

unless you know the versions are compatible.

A world may depend on blocks, items, entities, dimensions, and data provided by particular mods.

Check the server console.

Possible causes include:

• Wrong Java version
• Different Minecraft version
• Missing plugin
• Missing mod
• Missing dependency
• Incorrect startup configuration
• Incomplete restore
• Wrong server software

If the backup previously worked, compare the current server environment with the environment that existed when the backup was created.

Check:

server.properties

and locate:

level-name=

For example:

level-name=survival

means Minecraft expects a world folder named:

survival/

Also check for accidental extra folders such as:

survival/
    survival/
        level.dat

instead of:

survival/
    level.dat

Player information is normally stored with the world data.

If player inventories or locations are missing, make sure the correct:

playerdata/

was restored with the correct world.

Also verify that you are using the expected Minecraft account and world.

If the world restored correctly but plugin information is missing, the plugin may store its data separately inside:

plugins/

or in an external database.

Restoring only the Minecraft world does not necessarily restore all plugin data.

Stop the server before continuing.

This can happen if a modded world is opened without all of the mods it previously used.

Restore the required:

• Mod files
• Correct mod versions
• Loader version
• Configuration

from the same working server backup when possible.

See:

Minecraft Mod and Modpack Troubleshooting Guide

There is no single schedule that fits every server.

A server that changes constantly should generally be backed up more often than a rarely used test server.

Consider how much progress you would be willing to lose.

For an active server, losing several days of builds and player activity may be unacceptable.

When possible, keep multiple recovery points instead of relying on one backup.

For example:

Recent Backup
Before Update
Known Good Backup

If the newest backup already contains a problem, an older known-good copy can be extremely useful.

A backup helps you recover, but you should still carefully test changes.

Before a major update:

1. Create a backup.
2. Make the change.
3. Start the server.
4. Check the console.
5. Connect to the server.
6. Verify the world.
7. Test important plugins or mods.
8. Restart the server once more.

For a manual file backup, stopping the server first is the safest approach because it allows Minecraft to finish writing world and player data.

If you are using an automated backup feature provided through the hosting panel, follow the behavior provided by that system.

Yes, but keep in mind that plugins and mods may store important data outside the world folder.

For a complete server recovery, a full server backup is often preferable.

Not if you only copied the world folder.

Plugin data is normally stored separately under:

plugins/

Not necessarily.

A file backup generally cannot be assumed to contain information stored on a separate MySQL or MariaDB server.

If your server panel provides an option to download a completed backup, keeping an additional copy outside the server can provide another layer of protection.

For manual backups, you can also download the necessary files or archive.

• How to Upload a Minecraft World
• How to Update Minecraft Plugins
• Minecraft Plugin Troubleshooting Guide
• How to Install a Minecraft Modpack
• Minecraft Mod and Modpack Troubleshooting Guide
• Minecraft server.properties Configuration Guide

If you need help with a restore, tell Down Side Hosting support:

• Which backup you want to restore
• Minecraft version
• Server software or mod loader
• What happened to the current server
• Whether you need the entire server or only a world restored

Contact Down Side Hosting Support

Down Side Hosting provides Minecraft Java hosting with server panel access, file management, console controls, backups, and support.

Minecraft Java hosting starts at $2/month.

View Minecraft Java Server Hosting

← Back to Minecraft Java Server Guides