Hello!
I haven't been able to find a good way to create hot-backups of a server/world that are both file-safe and don't block the main thread. Everything I've found online says to avoid
Backing up the world while the server is running under normal operation creates the potential condition of copying a chunk file while it's being written to, rendering the backup file incomplete/corrupted. In a perfect world, one would turn off chunk save queuing with
tldr; Does the
I haven't been able to find a good way to create hot-backups of a server/world that are both file-safe and don't block the main thread. Everything I've found online says to avoid
/save-all
like the plague, but I haven't been able to confirm if Paper uses its async chunk saving routine when calling /save-all
.Backing up the world while the server is running under normal operation creates the potential condition of copying a chunk file while it's being written to, rendering the backup file incomplete/corrupted. In a perfect world, one would turn off chunk save queuing with
/save-off
, flush chunks to disk with /save-all
, perform the backup, then re-enable the queue with /save-on
. But unless /save-all
saves queued chunks using Paper's graceful async method, this will typically cause a lag spike on the server. The only other failsafe solution is to back up the world while it's offline.tldr; Does the
/save-all
command obey max-auto-save-chunks-per-tick
and/or use Paper's async chunk saving routine? And if not, is there any reason it couldn't?
Last edited: