Beam provides two different recovery tools: Published Releases for a fast rollback and Webroot Backups for restoring a captured server state.

Published Releases

Every successful publish creates a release. The current release is marked in the project view.

Open Project Setup → Transfer → Release history to choose how many releases Beam keeps on the server. Beam 1.2.0 keeps between one and ten releases per project.

Use Rollback when a recent publish must be replaced by an earlier Beam release. Choose the earlier release, confirm the action, and verify the public website when activation completes. You can delete older releases when they are no longer needed.

Webroot Backups

Create a backup from the Beam action menu with Create Webroot Backup, or choose Webroot Backup + Publish to run both actions in sequence.

By default, the backup contains the current webroot. Under Project Setup → Transfer → Webroot backup, you can add server paths outside the webroot, for example ../tcms-data or an absolute data-folder path. Beam adds those paths to the backup ZIP.

Beam does not back up databases. Use the database or hosting provider’s backup tools separately.

Choose the backup ZIP mode

  • Fast (no compression) uses less server CPU but creates a larger archive.

  • Compressed ZIP needs more server CPU but normally uses less disk space.

When a backup fails, check available server space and try the other mode.

Download, restore, or delete a backup

The Webroot Backups section lists the available archives. You can:

  • Download a backup to the Mac. The circular progress control can cancel an active download.

  • Restore a backup to the server.

  • Delete an archive that is no longer required.

Restoring replaces the current captured server state. Create a new backup first when possible, then verify the live website and any included data folders.

Rollback or restore?

  • Use Rollback to return to an earlier Beam-published release.

  • Use Restore to return to a broader snapshot of the webroot and configured additional server paths.

For safe publish contents, see Publish filters, hidden files, and server-managed content.