Beam provides two different recovery tools: Published Releases for fast rollback and Webroot Backups for restoring a captured server state.
Published Releases
Every successful publish creates a release in Beam. The current release is marked in the project view, and the number of older releases kept on the server is configurable.
Use Rollback when a recent publish must be replaced by an earlier Beam release. Select the earlier release, confirm the action, and verify the public website when activation finishes. Old releases can also be deleted when they are no longer needed.
Webroot Backups
A webroot backup captures the current files before a risky change. Create one from the Publish menu with Create Webroot Backup, or choose Webroot Backup + Publish to run both actions in sequence.
By default, a webroot backup contains files from the webroot. Optional additional server paths can be added in Project Setup, for example a data directory stored beside the webroot. Databases are not included and require the backup tools provided by the database or hosting service.
Download, restore, or delete a backup
Beam lists available backups in Webroot Backups. A backup can be downloaded for safekeeping, restored to the server, or deleted. Restoring replaces the current webroot content except for protected paths, so create a current backup first when possible.
Rollback or restore?
Rollback: return to an earlier Beam-published release.
Restore: return to a broader snapshot of the server webroot and any configured additional paths.
Server space and backup format
Fast backup mode creates the archive with less server CPU work but produces a larger file. Compressed backup mode uses more CPU and less disk space. If a backup stalls or fails, check available disk space and Helper logs before retrying.
To keep server-only content safe during normal publishing, see Preserving server content with filters and protected paths.