# Back up Firetower

> Protect the database, credentials and files needed for recovery.

Source: https://usefiretower.com/docs/backups

Open **Updates** from the account menu as an administrator. You can create a database backup directly from the app.

![Updates → Back up now, highlighted with a box and arrow](https://usefiretower.com/product/guide-backup-start-light.webp)

Updates → Back up now, highlighted with a box and arrow. Desktop app · sample data. Select to enlarge.

## 1\. Create a backup

Click **Back up now** below the Machines list. Keep the page open while it shows **Backing up…**.

## 2\. Check completion

The button changes to **Backed up** when the request succeeds. The dump is saved on the server; it is not downloaded to your device.

![The app confirms that the backup completed](https://usefiretower.com/product/guide-backup-done-light.webp)

The app confirms that the backup completed. Desktop app · sample data. Select to enlarge.

## 3\. Keep the rest of the recovery set

The in-app backup contains the database’s public schema. Keep these items as well:

| Setting | What it does |
| --- | --- |
| Matching root key | Required to decrypt saved credentials. Store a protected copy separately from the database dump. |
| Deployment configuration | Your domains, environment settings and service configuration. |
| Worker files | Uncommitted changes and non-git outputs you need to keep. These are not in the server database. |

The server keeps the ten most recent dumps. Keep off-server copies under your team’s retention policy.

## Test recovery

Test the complete recovery set in an isolated environment. Follow [Restore and recover](https://usefiretower.com/docs/restore).