This repository has been archived on 2022-12-03. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
Magnus Walbeck 6b518fd6f7 Replace screen with tmux 2019-12-11 17:40:02 +01:00
LICENSE Initial commit 2016-09-06 23:01:15 -07:00
README.md Replace screen with tmux 2019-12-11 17:40:02 +01:00
backup.sh Replace screen with tmux 2019-12-11 17:40:02 +01:00
test.sh Command line flags, better thinning 2017-08-10 22:18:04 -07:00

README.md

This fork is a drop in replacement for tmux instead of GNU Screen.

Minecraft Backup

Backup script for Linux servers running a Minecraft server in a tmux session

Disclaimer

Backups are essential to the integrity of your Minecraft world. You should automate regular backups and check that your backups work. While this script has been used in production for several years, it is up to you to make sure that your backups work and that you have a reliable backup policy.

Please refer to the LICENSE (MIT License) for the full legal disclaimer.

Features

  • Create backups of your world folder
  • Manage deletion of old backups
    • "thin" - keep last 24 hourly, last 30 daily, and use remaining space for monthly backups
    • "sequential" - delete oldest backup
  • Choose your own compression algorithm (tested with: gzip, xz, zstd)
  • Able to print backup status and info to the Minecraft chat

Requirements

  • Linux computer (tested on Ubuntu)
  • Tmux (running your Minecraft server)
  • Minecraft server (tested with Vanilla 1.10.2 only)

Installation

  1. Download the script: $ wget https://raw.githubusercontent.com/nicolaschan/minecraft-backup/master/backup.sh
  2. Mark as executable: $ chmod +x backup.sh
  3. Use the command line options or configure default values at the top of backup.sh:

Command line options:

-a    Compression algorithm (default: gzip)
-c    Enable chat messages
-d    Delete method: thin (default), sequential, none
-e    Compression file extension, exclude leading "." (default: gz)
-f    Output file name (default is the timestamp)
-h    Shows this help text
-i    Input directory (path to world folder)
-l    Compression level (default: 3)
-m    Maximum backups to keep, use -1 for unlimited (default: 128)
-o    Output directory
-p    Prefix that shows in Minecraft chat (default: Backup)
-q    Suppress warnings
-s    Minecraft server tmux session name
-v    Verbose mode

Example usage of command line options:

./backup.sh -c -i /home/server/minecraft-server/world -o /mnt/external-storage/minecraft-backups -s minecraft

This will use show chat messages (-c) in the tmux session called "minecraft" and save a backup of /home/server/minecraft-server/world into /mnt/external-storage/minecraft-backups using the default thinning delete policy for old backups.

  1. Create a cron job to automatically backup:
    • Edit the crontab: $ crontab -e
    • Example for hourly backups: 00 * * * * /path/to/backup.sh

Retrieving Backups

Always test your backups! Backups are in the tar format and compressed depending on the option you choose. To restore, first decompress if necessary and then extract using tar. You may be able to do this in one command if tar supports your compression option, as is the case with gzip:

Example:

mkdir restored-world
cd restored-world
tar -xzvf /path/to/backups/2019-04-09_02-15-01.tar.gz

Then you can move your restored world (restored-world in this case) to your Minecraft server folder and rename it (usually called world) so the Minecraft server uses it.

Help

  • Make sure the compression algorithm you specify is installed on your system. (zstd is not installed by default)
  • Make sure your compression algorithm is in the crontab's PATH
  • Make sure cron has permissions for all the files involved and access to the Minecraft server's tmux session
  • It's surprising how much space backups can take--make sure you have enough empty space
  • SERVER_DIRECTORY should be the server directory, not the world directory
  • Do not put trailing / in the SERVER_DIRECTORY or BACKUP_DIRECTORY
  • If "thin" delete method is behaving weirdly, try emptying your backup directory or switch to "sequential"