Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsFor a server that must run on both Forge and Fabric, start with FTB Backups 2 and match its file to your exact Minecraft version; it supports Forge, Fabric and NeoForge through Minecraft 1.21.5 and is now in long-term support. Choose FastBack instead when incremental Git snapshots and lower storage use matter more than a simple install. For current NeoForge 1.21.1 or newer, evaluate FTB Backups 3, while Simple Backups is the low-complexity choice for Forge or NeoForge. Fabric administrators who want conventional compressed archives should look at Textile Backup.
For a hosted modded-Minecraft server, Godlike.Host supports modded Minecraft with a built-in mod installer and updater, one-click modpacks, custom server-pack uploads, and SFTP/FTP access.
As an Amazon Associate I earn from qualifying purchases.
Which backup mod should you choose?
Your loader and Minecraft version are the deciding factors. A backup mod built for Fabric will not load on Forge, and a jar for one Minecraft minor release can fail on another even when the loader name matches. Check the project file’s game-version and loader labels before copying anything into the server.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Forge and Fabric through Minecraft 1.21.5: FTB Backups 2 is the broadest established option. It has configurable timers, retention, extra-directory backups, JSON metadata and disk-space checks. The project is in long-term support, so treat it as mature rather than rapidly evolving.
- NeoForge on Minecraft 1.21.1 or newer: FTB Backups 3 is the newer FTB line. Its current listing shows NeoForge releases, so do not assume a Forge or Fabric build exists for your particular version. Its documented restore and delete operations are singleplayer-only.
- Any of Forge, Fabric or NeoForge when storage efficiency is the priority: FastBack stores incremental Git snapshots and records only changed world parts. It requires native Git and Git LFS on the machine running the server.
- Simple scheduled backups on Forge or NeoForge: Simple Backups lets you set a backup count and storage limit, removes the oldest files, and provides the server command
/simplebackups backup start. - Fabric-only with compression and detailed pruning: Textile Backup automatically archives worlds, supports multiple compression formats, can delete by age, number or size, and requires a server restart for restoration.
- Asynchronous backups and idle-server pauses: Simple Backup (spoorn) supports configurable intervals, pausing when no players are online, ZIP or tar.lz4 output, retention limits and disk-space guards. Verify its exact Minecraft release support before deployment.
What a Minecraft backup mod protects—and what it does not
These projects run inside or alongside the dedicated server and copy the world data that would otherwise be lost after corruption, an operator mistake or a failed update. Depending on the mod, a snapshot can include the overworld, Nether and End, player data, region files, datapacks and selected extra directories. A backup is useful only if it completes, remains readable and can be restored.
#1 Best Overall
A mod normally writes its files to the same machine and often the same disk as the live world. That protects against a bad command or a broken mod update, but not against disk failure, ransomware, theft, a hosting outage or an administrator deleting the entire server directory. Keep a second copy on another volume or machine, and preferably an off-server copy, as part of your own disaster-recovery process.
Backups made while a server is actively changing chunks are not automatically a complete disaster-recovery design. Test a restore with your modpack, dimensions and player data before you trust a schedule. A backup that exists but cannot be opened after a crash is not a successful backup.
Loader and version compatibility comes first
Identify the running server
- Read the startup log or launcher command to confirm whether the server is running Forge, Fabric or NeoForge.
- Record the complete Minecraft version, including the minor release such as 1.20.1 or 1.21.1. Do not rely on the modpack’s marketing name.
- Check the backup project’s file list for both labels. A project page can support several loaders while an individual jar supports only one.
- Install the server-side file in the same instance that owns the world. You generally do not need to install a server backup utility on every player’s client unless the project explicitly says otherwise.
Why a close version is not close enough
Loader APIs and world-storage formats change between Minecraft releases. A jar marked 1.21.1 may be rejected by a 1.21.4 server, or it may start and fail later when a backup task touches a changed API. Keep the old backup mod available when upgrading a world so you can restore a pre-upgrade copy if the new build misbehaves.
Feature comparison
| Project | Loader and version coverage | Scheduling and retention | Storage method | Restore notes | Safeguards and dependencies | Maintenance status |
|---|---|---|---|---|---|---|
| FTB Backups 2 | Forge, Fabric and NeoForge; Minecraft up to 1.21.5 | Configurable timers and retention; can include extra directories | Conventional backup archives with JSON metadata | Use the saved archive and test the pack’s restore procedure; an exact server restore command is not stated | Disk-space checks | Long-term support |
| FTB Backups 3 | Minecraft 1.21.1+; current listing is NeoForge-focused | Configurable timing and command-triggered backups | ZIP plugin system | Restore and delete are documented as singleplayer-only | In-game progress display | Newer FTB line; verify the exact loader release |
| FastBack | Forge, Fabric and NeoForge | Snapshot history is controlled through its Git-based workflow | Incremental Git snapshots; only changed world parts are saved | Restore from a selected snapshot according to the project’s procedure; exact command is not stated | Native Git and Git LFS are required | Project is presented as an actively maintained option; check the current release |
| Simple Backups | Forge and NeoForge | Choose how many backups and how much storage to keep; oldest files are deleted | Standard scheduled backup files | Restore by replacing the world with a verified backup; no dedicated restore command is documented | Server-side utility; manual start command available | Simple, low-complexity project |
| Textile Backup | Fabric server-side | Delete by age, number or total size | Automatic world archives with multithreaded compression and multiple formats | Restore requires a server restart | Configurable access controls | Feature-rich Fabric alternative |
| Simple Backup (spoorn) | Verify the exact Minecraft release before use | Configurable intervals and retention; can pause when no players are online | ZIP or tar.lz4; asynchronous operation | Use a verified archive; release-specific restore details are not stated | Disk-space guards | Repository is less version-specific than the listings above |
FTB Backups 2: the broad compatibility choice
FTB Backups 2 is the practical starting point for a mixed-loader pack or a long-lived Forge server. CurseForge lists Forge, Fabric and NeoForge builds and reports 30,449,365 downloads on its 2025 listing. That number indicates widespread use, not a guarantee that a particular modpack will work without testing.
The project notice says it is available only through Minecraft 1.21.5 and is now in long-term support. For a server on a later Minecraft release, do not force the 1.21.5 jar; move to a compatible project or wait for a supported build.
Useful controls
- Set a timer that reflects how often players change the world.
- Set a retention count and, where available, a storage ceiling so a busy server cannot consume the entire disk.
- Add important directories beyond the main world when your pack stores configuration, scripts or custom data outside the world folder.
- Keep the generated JSON metadata with each archive so you can identify when it was made and what it contains.
- Leave disk-space checks enabled. A failed backup that is reported early is safer than a server that silently fills its volume.
Best use case
Choose FTB Backups 2 when loader breadth and a familiar archive workflow matter more than the newest feature set. It is particularly suitable for Forge/Fabric packs that will remain on a supported release while the project is in LTS.
FTB Backups 3: newer FTB workflow for current releases
FTB Backups 3 is described as a backup solution for Minecraft 1.21.1 and newer. The current project listing shows NeoForge releases, so a Forge or Fabric administrator must verify that a file exists for the exact combination of loader and game version before planning a migration.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →It adds in-game progress display, command-triggered backups, configurable timing and a ZIP plugin system. Progress reporting is useful on large worlds because an operator can see that work is still proceeding rather than assuming the server has stalled.
Its documented restore and delete functions are singleplayer-only. On a dedicated server, plan to stop the server, preserve the current world, unpack the chosen archive manually and then start the server for verification. Do not promise operators a one-command in-game restore until the project documents that capability for your build.
FastBack: incremental Git history
FastBack is designed for administrators who want many historical snapshots without storing a complete copy of every unchanged region. Its description calls it a fast, incremental Minecraft world backup system powered by Git. Each snapshot saves only world parts that changed since the previous snapshot, which can reduce storage growth on worlds where players touch a small area between backups.
Required host software
The usage guide explicitly requires native Git and Git LFS. Install both on the operating system that runs the server, not merely on an administrator’s laptop. Confirm that the server account can execute them and write to the repository location before enabling an aggressive schedule.
When incremental storage helps
FastBack is attractive for active servers that need a long history or frequent snapshots and have limited disk space. Git history also gives you a clear sequence of points to inspect. The trade-off is operational complexity: Git, Git LFS, repository permissions and snapshot maintenance become part of the backup system. If your staff wants a single archive folder with minimal dependencies, choose a conventional utility instead.
Simple Backups: scheduled Forge or NeoForge utility
Simple Backups focuses on the basic job: create scheduled server backups and retain only what the administrator has allowed. You define how many backup files and how much storage to keep; when those limits are reached, the oldest files are removed. It runs server-side and exposes /simplebackups backup start for an immediate manual backup.
Why it suits small installations
- There is no Git repository to administer.
- Retention rules are easy to explain to volunteer moderators.
- The manual command lets you create a known-good point before installing a mod or changing a configuration.
- Forge and NeoForge support covers many conventional modpacks.
Its simplicity means you should supply the missing disaster-recovery pieces yourself: verify archives, copy them to another storage location and document the restore procedure for your world layout.
Textile Backup: Fabric-focused compression and pruning
Textile Backup is a Fabric server-side utility for administrators who want more control than a basic scheduled copy. It automatically archives worlds, uses multithreaded compression and supports multiple compression formats. Its cleanup rules can be based on backup age, the number of backups or their total size, so you can express a policy such as keeping recent daily files while removing older snapshots when a quota is reached.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Access controls can restrict who is allowed to invoke backup operations. Restoration requires a server restart, which is appropriate for a controlled maintenance window but should be included in the server’s incident runbook. Test that the chosen compression format can be opened on the machine where you will perform recovery.
Simple Backup (spoorn): asynchronous and player-aware scheduling
The spoorn project offers configurable intervals, asynchronous backup work, pausing when no players are online, ZIP or tar.lz4 output, retention limits and disk-space guards. Pausing during empty periods can reduce unnecessary files on a private server, while asynchronous operation can reduce visible pauses during routine work.
The repository description is less specific about Minecraft releases than the Modrinth and CurseForge listings for the other projects. Treat version support as an unresolved deployment check: locate a release that names your exact game version and loader, install it on a copy of the server and perform a restore test before enabling it on production.
How to install and validate a backup mod
- Make a safety copy first. Stop the server and copy the complete instance, including worlds, configuration and existing backups, to separate storage. This gives you a fallback if the new mod fails during startup.
- Match the file. Select the jar whose loader and Minecraft version exactly match the server. Read the dependency notes; FastBack requires native Git and Git LFS.
- Install server-side. Place the jar and required dependencies in the instance’s
modsdirectory. Keep a record of the file name and version so you can reproduce the installation. - Start without players. Watch the console for dependency errors, mixin failures, permission problems or a message that the mod was disabled. Do not proceed while the server is reporting an incompatible version.
- Configure the schedule. After the first successful start, inspect the mod’s generated configuration. Set the interval, destination, retention and disk limits. Avoid placing the destination inside a directory that your host’s cleanup job deletes.
- Create a test backup. Use the documented manual command where one exists, such as
/simplebackups backup start, or wait for the first scheduled run. Confirm that the job reports completion rather than merely creating an empty directory. - Inspect the result. Check the archive or snapshot size, timestamp and readable contents. For FastBack, verify that the Git repository and LFS objects are present; for compressed archives, open one file with a standard extractor.
- Test recovery on a clone. Duplicate the server instance, restore the test backup there and start it on an isolated port. Join with an operator account, visit several dimensions and verify player inventories, claims, machines and modded blocks.
Choose a schedule and retention policy
Set frequency according to how much progress players can afford to lose. A public server with constant building may need frequent snapshots; a private server used on weekends can use a wider interval. The correct value is the longest rollback the community accepts, not the shortest interval a mod permits.
| Server pattern | Practical starting policy | What to monitor |
|---|---|---|
| Small private world | Scheduled snapshots during play sessions, with several recent copies | Whether the pause-when-empty option is appropriate |
| Active modded community | Frequent snapshots plus daily and weekly copies retained separately | Archive duration, CPU impact and disk growth |
| Large exploratory world | Incremental history or compression with a defined quota | Repository or archive integrity and available free space |
Retention should cover more than the latest failure. Keep short-term copies for accidental changes, a longer-lived copy before major updates and at least one copy that is not mounted on the live server. If a utility offers count, age and size limits, use the limit that reflects your real storage budget and document which rule removes files first.
A restore procedure that works under pressure
- Announce maintenance and stop new connections.
- Stop the server cleanly so region and player files are no longer being written.
- Rename the damaged world directory instead of deleting it. Preserve it for forensic review or a second recovery attempt.
- Copy the selected archive or snapshot into a temporary location and verify that it opens before replacing production data.
- Restore the world, dimensions and any extra directories your modpack requires. Keep the backup metadata with the restored files.
- Start the restored copy on an isolated port. Check spawn areas, inventories, chunk loading, machines, permissions and scheduled commands.
- Only after validation, move the restored world into the production path and restart the public server.
- Record which backup was used and why. This prevents operators from repeatedly restoring an older point after a later failure.
FTB Backups 3’s documented restore and delete support is singleplayer-only, and the other listings do not promise a universal dedicated-server restore command. A manual, tested procedure is therefore the safest common denominator.
Protect backups from the failures they are meant to survive
- Use separate storage. A second disk protects against a bad update but not a fire or theft; an off-server copy addresses that larger risk.
- Restrict permissions. Let the server account write backups but limit who can delete them. Protect archives if they contain player data or private coordinates.
- Monitor free space. Configure disk guards where available and alert when the destination crosses a threshold. Do not wait for the filesystem to reach zero bytes.
- Verify regularly. Open a recent archive and perform a full test restore on a schedule, especially after changing the loader, modpack or storage path.
- Keep versioned copies before upgrades. Make a separate, clearly named backup before updating Minecraft, the loader or a large group of mods.
Troubleshooting common failures
The server refuses to start after installation
Remove the new jar from the test instance and read the first error, not only the final crash summary. A mismatched Minecraft version, wrong loader build or missing dependency is more likely than a corrupt world. Reinstall the exact file for the server’s version and test again.
FastBack reports Git or LFS errors
Install native Git and Git LFS on the server host, ensure they are available to the service account and check write permissions for the repository. A Git client installed only for your desktop account will not satisfy a service launched under another user.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Backups stop when the disk fills
Free space immediately, lower retention or archive older copies elsewhere, then run a manual test. Enable the project’s disk-space guard where available. Never solve a full disk by deleting the newest backup before confirming an older copy is readable.
An archive exists but the restored world is incomplete
Check whether the mod was configured to include extra directories and dimensions. Compare the archive contents with the live instance, then repeat the test while the server is stopped. If player data or mod configuration lives outside the main world path, add those directories to the backup scope.
Players report lag during scheduled work
Move heavy compression or repository maintenance to quieter periods, reduce frequency, or use an incremental approach. Textile Backup’s multithreaded compression and FastBack’s changed-parts snapshots address different bottlenecks, so measure server tick time and storage growth on a clone before changing production settings.
Final decision framework
Pick FTB Backups 2 for broad Forge/Fabric/NeoForge coverage through 1.21.5 and a mature conventional workflow. Pick FTB Backups 3 only after confirming a NeoForge build for your exact 1.21.1-or-newer release and accepting that documented restore and delete actions are singleplayer-only. Pick FastBack when incremental Git history justifies installing and maintaining Git plus Git LFS. Pick Simple Backups when a straightforward scheduled utility is the priority on Forge or NeoForge. Pick Textile Backup for a Fabric server that needs compression choices, detailed pruning and controlled restoration. Consider Simple Backup (spoorn) when asynchronous operation, idle-player pauses and ZIP or tar.lz4 output fit your deployment, but verify release support first.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
