# Separate Palworld local save history from off-server backups

Palworld's local backup saves can help with a recent gameplay mistake, but keep a separate copy outside the game server. A lost disk, full account or inaccessible node can affect both the live world and local history together. Review where each copy lives before promising players that their world has an off-server recovery path.

## Identify the two backup layers

Pocketpair documents `bIsUseBackupSaveData` for creating backup data beneath the save location and warns that enabling it increases disk load. Check the current official reference for its retention schedule. Do not copy an old schedule into a panel task and assume you have changed the game's internal history behaviour.

In the file manager, identify the live world directory and any local `backup` directory without renaming or moving them. Record approximate sizes and dates. Then inspect your panel's backup page separately: check whether a completed archive exists, its timestamp and whether you can download it. A directory named backup proves only that files exist at that location.

## Establish a recoverable checkpoint

1. Record the server build, world identity and relevant configuration. Ask players to leave for a short maintenance window and stop the server through its normal control.
2. Create a panel backup covering the complete required save and configuration. Wait for a completed result rather than treating a queued or running job as finished.
3. Download a recovery copy or confirm the plan's off-server backup arrangement with support. Keep a note of its size, completion time and location without placing credentials in the filename.
4. Start the original server and verify established characters and bases. Inspect disk use after the next period of normal activity so you can see whether local history is accumulating as expected.
5. Arrange an isolated restoration check when possible. Use separate storage and allocations, and prevent the test world from accepting ordinary players as if it were production.

## Budget storage for history

Compare live saves, local backup history, logs and panel archives as separate categories. Keep free space for normal saves and maintenance rather than filling the account to its published limit. If local history grows unexpectedly, record the directory sizes and contact support before deleting files you do not recognise. Do not remove an archive while a backup or restoration task is using it.

Choose retention around how long players may take to notice a problem. Several recent copies can all contain the same unwanted change. Keep dated older checkpoints when your storage plan permits, and document which copies you have verified. Avoid claiming that the game setting automatically exports files to another machine.

## Recover with the correct copy

Before restoring, preserve the current world and choose a complete checkpoint from before the incident. A rollback can remove progress from other players, so agree the recovery point with the group. If a panel task fails or stays running, preserve its request details and seek support. Repeatedly starting restorations can make it harder to identify which copy reached the live directory.

## Related help and sources

- [Schedule game server backups and check retention](https://help.cloudexa-hosting.com/books/game-hosting/page/schedule-game-server-backups-and-check-retention)
- [Move an existing Palworld world safely](https://help.cloudexa-hosting.com/books/game-hosting/page/move-an-existing-palworld-world-safely)
- [Investigate and recover from a full game server disk](https://help.cloudexa-hosting.com/books/game-hosting/page/investigate-and-recover-from-a-full-game-server-disk)

[Pocketpair local backup-save documentation](https://docs.palworldgame.com/settings-and-operation/configuration/).