Skip to main content

Create and Manage Server Backups

By default, all servers are allowed to create two backups. After you create a backup, you can download the backup file or restore your server from that backup.

Requesting Increased Backup Limit

The default backup limit is two for all servers. This limit can be increased upon request, but is subject to my (Max's) discretion.

Create a Backup

It's important to remember that your server's Files tab supports downloading files to your computer, as well as compressing folders (which allows you to download them, too).

From your server's page, select the Backups tab on the top navigation bar. On the Backups page, click the blue  Create Backup  button near the top-right. A pop-up will appear with a few options. If you'd like, you can leave all of them blank and simply click the  Create  button. The backup's name will default to "Backup at YYYY-MM-DD HH:MM:SS," it will back up all of the server files, and it will be unlocked.

Ignored Files & Directories

When creating backups, there's normally at least a few files or folders that you don't actually want to have backed up. For example, you may want to skip a Minecraft's server.jar file, or a Garry's Mod server's addons folder, or a logs folder. To do this, you can specify a list of files and/or folder in this textbox. Each row represents an individual entry.

Examples of Ignoring Files & Directories

Minecraft example where we are ignoring the server.jar.

server.jar

More complex Minecraft example where we are ignoring specific folders for a plugin and other miscellaneous files.

server.jar
bluemap/web/maps/*
config
libraries
logs/*.gz
plugins/bStats
versions
eula.txt

Notice the inclusion of wildcards (*). These tell the backup system to match anything in place of the wildcard. For example, specifying bluemap/web/maps/a-map.file would tell the backup system to not backup a-map.file, but specifying bluemap/web/maps/* instead would prevent all files within the maps folder from being backed up.

Locked Backups

When you lock a backup, it will not be possible to delete it until it is unlocked. 

Backups and Schedules

Unfortunately, schedules you make that have a backup task will not overwrite older backups automatically. If you have hit your backup limit (two by default) and a backup task attempts to run, it will fail and no backup will be created.

Download or Delete Backups

Once a backup has been created, it will appear on the Backups page in a list. Along the right side of the list, each backup will have a kebab button. Clicking this button will provide you with a few options, notably Download and Delete. Click the option which corresponds with your desire.

Restore Backups

STOP! - Restoring from a backup is destructive. Make sure you know what you are doing! You will lose data!

After you've created a backup, you can restore your server from that backup. From the Backups page, click the desired backup's kebab button and then click Restore.

A pop-up will appear asking if you'd like to delete all files before restoring the backup. This option is extremely important and you should understand the difference.

Keep Files (Unchecked)

Leaving the setting unchecked means that restoring the backup will only affect files that were included in the backup. Any new files or directories will remain after the backup is restored. In certain edge-cases, new files or directories may be overwritten when restoring a backup even if the setting was left unchecked. In order to prevent this, it would be best to first download the backup file and then inspect it locally on your computer. Compare the names and locations of files and directories from the backup with what is currently visible on your server's Files tab. If anything in your backup matches what's currently in your Files, even if the file/directory in question was deleted and then remade after the backup, it will most likely me overwritten.

Delete Files (Checked)

Checking the setting will delete the entire contents of your server files. Once everything is deleted, the backup will then be restored. This effectively does a "proper" restore where files and directories are exactly how they were when the backup was created. In most cases, you'll probably want this behavior, but you must be sure that you're okay with wiping the current contents of your server. As silly as it sounds, it may be worth creating a backup before restoring from another.