← All guides
ASA Manager · Step-by-step

ASA Manager: backups, restore and maintenance

Create recovery points, restore a test world and schedule backups or daily restarts while the manager is open.

TBB ASA Server Manager overview screen, captured from the desktop application
Select and verify the target server before creating or restoring a backup · Actual prototype 0.7.3 interface with sample data; final build may differ.

A recovery plan needs server-world backups as well as manager settings. First test restore on a disposable server, not your only copy of an established world.

1. Create a manual backup

  1. Select the correct server and stop it normally.
  2. Open Backups in the left menu.
  3. Choose the server in the selector.
  4. Click Create backup and wait for completion.
  5. Check the new entry’s date, size and file location.

The overview helps you verify which server you are working with before opening Backups. The pictured process statistics are sample data, not backup verification.

2. Restore a snapshot

  1. Stop the target server.
  2. Open Backups and select that server.
  3. Select the intended snapshot by date and file name.
  4. Click Restore and read the confirmation.
  5. Confirm only when the target and snapshot are correct, then wait for completion.
  6. Start the server and check the expected world state.

The restore workflow first makes a copy of the current Saved folder. A backup includes the server’s Saved folder and managed profile settings. Shared cluster transfer data is separate.

3. Schedule backups or restarts

  1. Open Tools & health, then Maintenance.
  2. Choose the server in Server schedule.
  3. Enable Scheduled backups and set the interval in hours if wanted.
  4. Enable Daily restart, enter a local PC time as HH:mm and choose the player-warning time.
  5. If enabling Delete older backups, choose how many to keep and ensure you have another recovery copy.
  6. Click Save schedule and keep the manager open.

Scheduled jobs do not run while the manager is closed. A running server may be warned, stopped, backed up and restarted; plan for downtime. A failed job needs its Console/log reviewed. Unsaved edits can defer maintenance.

4. Understand retention and cancellation

Deleting older backups is an explicit choice. Test retention using disposable backups before enabling it on important worlds. Cancel queued job cancels pending work and snoozes that server’s schedule for one hour; it is not the same as deleting the schedule.

5. Keep a second copy

Copy important backup archives to another drive/location and verify they can be read. Remember that changing the backup location does not move old archives; point the manager back to the old location when you need to list those backups.

Clusters and their separate transfer folder

Export the manager workspace

Explore ASA Server Manager

View the project →