Skip to main content

Protecting Your Game Server with Backups

Backups are the safety net every game server needs. They capture your server files — worlds, configurations, plugins, mods, player data — and package them into a downloadable snapshot you can restore at any time. The FREAKHOSTING Game Panel at games.freakhosting.com makes this easy through the Management > Backups section, where you can create manual backups, set retention policies, schedule automatic backups, and restore from any previous backup with a few clicks. Whether you are running a Minecraft survival world, a modded Garry’s Mod server, or a Terraria adventure map, backups are what stand between you and disaster.

Difficulty

Beginner

Time

5 Minutes

Real-World Scenario: Why Backups Matter

Here is a situation that happens more often than you might think:
You are running a Minecraft survival server with a thriving community. A player suggests a new economy plugin, so you install it and restart the server. Instead of loading cleanly, the server crashes on startup — and when you check, the world files are corrupted. Weeks of builds, redstone contraptions, and player progress are at risk.
With a recent backup in place, recovery takes less than two minutes. Without one, you are looking at a very difficult conversation with your players. The lesson: Create backups before every major change — plugin installs, mod updates, configuration edits, version upgrades. It takes seconds and can save you hours of heartache.

Understanding the Backups Page

To access backups, log in to the Game Panel, select your server, then navigate to Management > Backups in the left sidebar. The Backups page is split into two sections:

File Backups

The main backup area where your server file backups are listed. Each backup row shows the Name, Size, Creation date, and Checksum. At the top you will find the File Backup Retention dropdown and a green Create Schedule button.

Database Backups

A separate section for database backups. If your server does not use databases (most game servers do not), you will see the message: “No databases available for this server.” This is completely normal for the majority of game server types.
If your backup limit is set to 0, you will see the message: “Backups cannot be created for this server because the backup limit is set to 0.” This means your current plan does not include backup slots. Contact support or upgrade your plan to enable backups.

Creating a Manual Backup

Manual backups let you take a snapshot of your server files whenever you want — before a big update, after finishing a build, or just as a regular safety measure.
1

Navigate to Backups

Log in to the Game Panel, select your server, and click Management > Backups in the left sidebar.
2

Check Your Backup Limit

Before creating a backup, make sure your plan includes backup slots. If you see the message about the backup limit being set to 0, you will need to contact support or upgrade your service to enable backups.
3

Create the Backup

Click the backup creation button in the File Backups section. You may be prompted to enter a name for the backup — use something descriptive like “Before plugin update” or “Weekly backup March 2026” so you can easily identify it later.
Get into the habit of naming your backups with the date and reason. “Pre-1.20.4-update-March25” is far more useful than “backup1” when you are scrolling through a list trying to figure out which one to restore.
4

Wait for Completion

The backup will begin processing. Depending on the size of your server files, this can take anywhere from a few seconds to several minutes. Once complete, the backup appears in the File Backups table with its Name, Size, Creation date, and Checksum.
Creating a backup while your server is running is generally safe, but for the most consistent results — especially on servers with active world saves like Minecraft — consider stopping the server briefly or running a save command (save-all in Minecraft) before creating the backup. This ensures all world data is flushed to disk.

Setting Backup Retention

The File Backup Retention dropdown at the top of the Backups page controls how long your backups are kept before being automatically cleaned up. This helps you manage storage without manually deleting old backups. Available retention options include:

Forever

Backups are never automatically deleted. They stay until you remove them manually or hit your backup slot limit.

1 Week

Backups older than 7 days are automatically removed. Good for servers with frequent changes where you only need recent snapshots.

1 Month

Backups older than 30 days are cleaned up. A balanced option for most game servers that do not change drastically day to day.
If you are not sure which retention to pick, start with Forever and manage backups manually. Once you have a feel for how often you create backups and how many slots your plan includes, you can switch to a timed retention to automate cleanup.

Scheduling Automatic Backups

Instead of remembering to create backups manually, you can set up a schedule that runs them automatically. This is done through the green Create Schedule button on the Backups page.
1

Click Create Schedule

On the Backups page, click the green Create Schedule button. This takes you to the schedule creation interface where you can define when and how often backups should run.
2

Configure the Schedule

Set up your preferred schedule — daily, weekly, or at custom intervals. Choose a time when your server is least active for the best results. For example, a Minecraft server that is busiest in the evenings might benefit from a 4:00 AM backup schedule.
3

Save and Activate

Save the schedule and it will begin running automatically at the configured times. Each scheduled run creates a new backup entry in your File Backups table, subject to your retention settings and backup slot limits.
Scheduled backups follow the same retention policy you set in the File Backup Retention dropdown. If you have limited backup slots and your retention is set to Forever, older backups may need to be manually deleted to make room for new scheduled ones.

Downloading a Backup

Every backup in the File Backups table can be downloaded to your local computer. This is useful for keeping an off-panel copy of important server states, archiving milestone builds, or transferring server data to a different host.
1

Find the Backup

In the File Backups table, locate the backup you want to download. Each row shows the backup Name, Size, Creation date, and Checksum.
2

Click the Download Action

On the right side of the backup row, click the download action. Your browser will begin downloading the backup archive file.
3

Store It Safely

Save the downloaded file somewhere safe — an external drive, cloud storage, or a dedicated backups folder on your computer. Label it clearly so you know which server and date it corresponds to.
The Checksum shown in the backup table is a unique fingerprint for each backup file. If you ever need to verify that a downloaded backup was not corrupted during transfer, compare the checksum shown in the panel against the checksum of the file on your computer using a tool like sha256sum (Linux/Mac) or CertUtil (Windows).

Restoring from a Backup

Restoring a backup replaces your current server files with the contents of the selected backup. This is the recovery tool you reach for when something goes wrong — a bad plugin, a corrupted world, an accidental file deletion, or any situation where you need to roll back.
1

Stop Your Server

Before restoring, stop your game server from the console or power controls. Restoring while the server is running can cause conflicts or data corruption.
Restoring a backup overwrites your current server files. Any changes made after the backup was created will be lost. If there is anything on your current server you want to keep, create a new backup first before restoring an older one.
2

Select the Backup to Restore

In the File Backups table, find the backup you want to restore. Check the Name and Creation date to make sure you are picking the right one.
3

Click Restore

Click the restore action on the backup row. Confirm the restoration when prompted. The panel will begin replacing your server files with the backup contents.
4

Start Your Server

Once the restore completes, start your server back up. Check the console output to confirm everything loaded correctly — worlds, plugins, configurations, and player data should all be back to the state they were in when the backup was created.

Deleting a Backup

If you need to free up a backup slot or remove an outdated backup, each row in the File Backups table includes a delete action. Click it, confirm the deletion, and the backup is permanently removed. This cannot be undone — if you think you might need the backup later, download it to your computer first.

Backup Best Practices for Game Servers

Installing a new plugin, updating your server version, changing world settings, or modifying configuration files? Create a backup first. This gives you a clean rollback point if the change causes problems.
Name your backups with the date and context: “Pre-1.20.4-update”, “After-spawn-rebuild”, “Before-modpack-change”. When you have multiple backups, descriptive names save you from guessing which one to restore.
The panel stores backups on the server infrastructure, but keeping a local copy of critical backups (major milestones, end-of-season saves) gives you an extra layer of protection.
If your server has active players making progress daily, a scheduled backup ensures you always have a recent restore point — even if you forget to create one manually.
A backup you have never tested is a backup you are only hoping works. Every few weeks, try restoring a backup to confirm the process works and your data is intact. You can always create a fresh backup of the current state before testing.

Need Extra Help?

If you encounter any issues, our support team is ready to assist:

Save on Your Hosting

Ready to spin up a new game server? Use code KB20 at checkout for 20% off your first month!

Last Updated: March 2026 | Game Panel Support: Backup management simplified.