Skip to content

Backup problems

This page covers problems on the Backups page. See Backups for how they work.

I cannot create a backup, the limit is reached

Section titled “I cannot create a backup, the limit is reached”

Why it happens: Your plan allows a set number of backups. When you hit it, manual creation is blocked.

How to fix it:

  1. Download any backup you want to keep on your own PC.
  2. Delete an old backup you no longer need.
  3. Create the new one.
  4. To see your limit, check Provisioning Limits on your service page in the client area. Need more? See Upgrade.

I cannot create a backup, all my backups are locked

Section titled “I cannot create a backup, all my backups are locked”

Why it happens: Locked backups cannot be deleted, so nothing can make room.

How to fix it:

  1. Unlock the backup you can spare using its menu.
  2. Delete it, then create the new backup.
  3. Unlocking and locking needs the backup delete permission if you are a subuser.

Why it happens: Locking protects a backup from deletion, including automatic rotation.

How to fix it:

  1. Open the backup’s menu and choose Unlock.
  2. Then choose Delete.
  3. If you do not see the option, you may lack the backup delete permission. Ask the server owner.

Why it happens: Large servers take time to back up. Very busy or full disks can be slower.

How to fix it:

  1. Wait several minutes. A big world or many files takes longer.
  2. Refresh the page and check whether it finished.
  3. If it is still in progress after a very long time, open a ticket.
  4. In the future, remove files you do not need (old logs, caches) so backups are smaller.

Why it happens: A failed backup can come from a full disk, a file that changed during backup, or a node problem.

How to fix it:

  1. Delete the failed backup. It cannot be restored anyway.
  2. Check that your disk is not full. See Disk full.
  3. Try again, ideally with the server quiet or stopped.
  4. If it keeps failing, open a ticket.

Why it happens: When a scheduled backup runs at the limit, the oldest unlocked backup is deleted to make room.

How to fix it:

  1. Lock the backups you want to keep. See Backups.
  2. Bear in mind locked backups count toward your limit, so keep only a few locked.
  3. Download important backups to your PC for a copy that is fully yours.

Why it happens: If the limit is full and every backup is locked, the scheduled backup cannot make room.

How to fix it:

  1. Unlock and delete one you do not need.
  2. Check the schedule. See Schedule problems.

Why it happens: The backup may be unfinished or failed, or the server may be in the middle of another operation such as installing.

How to fix it:

  1. Make sure the backup shows as completed.
  2. Make sure the server is not installing or suspended.
  3. Wait a few minutes and try again.
  4. If it still fails, open a ticket and say which backup you tried.

Why it happens: Restoring stops the server, and the panel blocks power buttons, files, and new backups until it finishes. Large backups take longer.

How to fix it:

  1. Wait and refresh the page. Big backups can take several minutes.
  2. If it stays in this state for a long time, open a ticket.

The restore did not bring back everything, or old files are still there

Section titled “The restore did not bring back everything, or old files are still there”

Why it happens: A normal restore unpacks files over the current ones. It overwrites files with the same name and leaves other files alone. Files created after the backup stay.

How to fix it:

  1. When you restore, tick the option to delete all files before restoring if you want an exact copy of the backup.
  2. Warning: that option wipes everything first. Download anything you still need before you use it.

The restore overwrote something I wanted to keep

Section titled “The restore overwrote something I wanted to keep”

Why it happens: Restore overwrites files with the same name.

How to fix it:

  1. Before restoring, make a fresh backup of the current state (if you have room).
  2. Then you can restore only what you need by downloading the older backup, unpacking it on your PC, and uploading just the files you want.

Why it happens: Backups contain everything in your server files, so big worlds, many mods, and old logs all add up.

How to fix it:

  1. Remove things you no longer need (old worlds, logs, crash reports).
  2. Ignored files can be set when you create a backup. Use that to skip cache or log folders.
  3. Run backups when few players are online.

Why it happens: You may lack the backup download permission, or the backup is unfinished, or it is very large and the browser download times out.

How to fix it:

  1. As a subuser, ask the owner for the backup download permission.
  2. Make sure the backup is finished.
  3. Retry, or try another browser.
  4. If it keeps failing for a big backup, open a ticket.

Why it happens: It may have been rotated out by a scheduled backup, deleted, or the server was deleted.

How to fix it:

  1. Check the Activity page for backup delete events and who made them. See Activity.
  2. Check that you are on the right server.
  3. If you are sure it should exist, open a ticket.

Why it happens: Panel backups are stored separately from your server files, so they are not counted in the same way as your files. The exact storage setup can vary.

How to fix it:

  1. If you are worried about space, check your disk usage on the Console page.
  2. If you have questions about how backup storage counts on your plan, open a ticket.

Why it happens: Some changes cannot be undone: switching software, reinstalling, updating versions, or deleting worlds.

How to fix it:

  1. Stop the server first for the cleanest backup.
  2. Create a backup, then lock it.
  3. Optionally download a copy.
  4. Now make your change.
  5. If something goes wrong, restore the locked backup.

Open a ticket or ask on Discord. See Contact support. Include the backup name and the time you tried.