-
Notifications
You must be signed in to change notification settings - Fork 16
Add ability to create World Backups #357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
Closed
…e being a folder for S3 storages
- Load backups in `/worlds backup` asynchronously - Improvements to restoring backups - Add ability to also backup not active worlds - Store used generator type for imported worlds
This allows the first backup deletion, then creation action to better be performed sequentially
thomasmny
added a commit
that referenced
this pull request
Jun 30, 2025
thomasmny
added a commit
that referenced
this pull request
Jul 1, 2025
thomasmny
added a commit
that referenced
this pull request
Jul 7, 2025
thomasmny
added a commit
that referenced
this pull request
Aug 10, 2025
thomasmny
added a commit
that referenced
this pull request
Aug 15, 2025
thomasmny
added a commit
that referenced
this pull request
Aug 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introducing World Backups
World Backups allow copies of worlds to be (automatically) created which can then restored at a later point in time
Getting started
This update introduces new config options
backup.max-backups-per-world: The maximum amount of backups a world can have (limited to 18)backup.auto-backup.enabled: When enabled, worlds will be automatically backed up in a predefined intervalbackup.auto-backup.interval: The interval (in seconds) in which worlds are backed up automaticallybackup.auto-backup.only-active-worlds: When enabled, only active worlds (worlds with builders in them) will be backed upbackup.storage.type: Defines where backups are to be saved to. Can be eitherlocal(saved on the server),s3(saved on an S3 storage) orsftp(uploaded to a server)When using S3:
backup.storage.s3.url: If not using AWS S3, specify the S3 storage's URLbackup.storage.s3.access-key: The access key required to access the S3 storage instancebackup.storage.s3.secret-key: The secret key required to access the S3 storage instancebackup.storage.s3.region: The region of the S3 storage instancebackup.storage.s3.bucket: The bucket in which backups are to be storedbackup.storage.s3.path: The path at which backups are to be stored within the bucketWhen using SFTP:
backup.storage.sftp.host: The server hostbackup.storage.sftp.port: The server portbackup.storage.sftp.username: The username required to access the serverbackup.storage.sftp.password: The password required to access the serverbackup.storage.sftp.path: The path at which backups are to be stored on the serverCreating a backup
Automatically
When enabled in the config, backups are automatically created in the defined interval.
If
backup.auto-backup.only-active-worldsis set totrue, the time until a backup will be only created is only incremented as long as a builder (i.e. player who can modify the world) is present in the world.Manually
Players with the permission
buildsystem.backup.createcan manually create a backup of the world they are in using/worlds backup create.Viewing backups
Creators of a world (or players with the
buildsystem.adminbypass permission) can view the backups of the world they are in using/worlds backup. Additionally, they will need the permission:buildsystem.backup.Each backup item's name will have the date and time at which it is was created.
Restoring a backup
Warning
Restoring a backup of the server's main world (often
world) can lead to issues and is not advised. If you decide to do so, make sure to restart the server immediately after.To restore a world to a backup, simply click on the desired backup within the backups overview. You will then be prompted to confirm the action since it cannot be reverted.