Plan and verify backups
Use your runtime backup tooling and test restoration before automating it.
EnderDash can run a backup script through an agent-side shell automation. It does not turn a downloaded file or successful scheduled command into a verified server backup.
Before you begin
Choose backup tooling appropriate to the game runtime, databases, and container storage. You need access to those resources and a destination outside the data being backed up.
For shell automation, the agent needs terminal support and the required access. Confirm the backup tools exist in the agent's execution environment.
Establish a restore procedure first
- Identify the worlds, configuration, plugin data, databases, and persistent volumes that must be restored together.
- Follow each application's documented procedure for a consistent snapshot. Some need a save, a database dump, or downtime.
- Run your backup script manually as the intended agent user.
- Inspect the resulting files and their destination.
- Restore the backup into an isolated test runtime.
- Start the test runtime and verify the expected world, records, and configuration.
Do not restore a test over a running production server. Keep the recovery commands and required credentials available independently of EnderDash.
Schedule the tested script
Open Automations and create a shell job for the script's absolute path. Set its working directory, schedule, and timezone. Start with no retries and skipped missed runs until duplicate execution is safe.
Use Run now once. Confirm the agent's run history, then inspect the actual backup output. Monitor storage capacity, retention, and access to the destination through your backup tooling.
After an incident
Determine the intended recovery point before replacing data. Stop the affected workload where required, preserve evidence needed for diagnosis, and use the tested restore procedure.
EnderDash agent state and your application data are separate. Preserving /enderdash/data in an agent container does not back up game worlds or database volumes.
Next: scheduled jobs or file transfers.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on