> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Backup copies of the panel

> How to create a profile, run, check and restore a backup through the Backups section.

Open **Management → Backup**.

## Create a profile

1. Click **Create a profile of**.
2. Choose local, S3 or combined storage.
3. Set up a schedule and retention.
4. For S3, specify the storage address, region, bucket and credentials.
5. Save the profile.

## Run and check.

Click **Run now** in the profile card. Launch history is in the adjacent tab. Open successful launch and press integrity check.

## History of S3 Storage

A new launch saves the original remote storage settings and the version of the credentials used. Changing the endpoint, bucket or keys in the profile does not transfer the old archive or redirect its verification, downloading, recovery or cleaning to the new storage.

Older launches created before supporting such images may still depend on the current profile. Before changing the storage, check the availability of the desired historical archives. Revoking the old key from the S3 provider can also deprive access to the archive: the saved image does not cancel the review on the provider's side.

If an archive is inaccessible or damaged, first restore the ability to read and verify; do not consider the presence of a record in the history as proof of the suitability of the backup.

## Restore.

1. Open a successful launch.
2. Click **Preview Recovery**.
3. Check the list of changes.
4. Confirm recovery.

> [!WARNING]
>
> Restoration replaces the current state of the database with the contents of the archive. Before starting, create a fresh, verified copy.

## Verification and rollback of recovery

After recovery, check the availability of the panel, the expected data and the status of the operation. If you want to cancel the result, you will need a separate recovery from the copy created in front of it. Returning the panel files without a consistent database state is not a base rollback.

Reconciliation of S3 behavior and recovery: 2026-09-06.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.