A backup failed or takes too long

My backup fails or never finishes.

Usually not enough disk, huge files (maps, logs) or the server writing while backing up; clean up and try again.

Before you start: Statistics (disk) and Files open.

Step by step

1. Check disk space in Statistics: a backup needs free room while it is built.
2. Delete large unneeded files: old zips, logs, and Dynmap/BlueMap tiles.
3. Exclude big folders you do not need by listing them in a .pteroignore file in the root (one path per line, for example plugins/dynmap/web/tiles).
4. Run save-all, or stop the server, before backing up so files do not change mid-backup.
5. Create the backup again and wait for it to show as completed.

Check it worked: The backup completes.

Why it happens: Backups archive every file; very large or changing folders make them slow or fail.

If backups keep failing with plenty of space, contact support with the server ID.

More guides on Backups, restores, and data loss:

• Take a backup
• No backup slots or the limit is reached
• Restore a backup
• Automatic daily backups
• Recover after data loss or griefing
• Does CoreX keep backups for me?