# Backups and automation

URL: https://docs.vaultpanel.net/guides/backups-and-automation

> Back up websites, apps and databases, keep copies off the server, run commands on a schedule, and notify other systems when something happens.

VaultPanel keeps the things you host safe and running on their own: backups on demand or on a
schedule, copies in S3-compatible storage or on another server, cron jobs that run as each site's
user, and webhooks that tell your chat or tools when something needs attention.

- [Backing up and restoring](https://docs.vaultpanel.net/guides/backups-and-automation/backups)
- [Off-server backup storage](https://docs.vaultpanel.net/guides/backups-and-automation/backup-storage)
- [Running cron jobs](https://docs.vaultpanel.net/guides/backups-and-automation/cron-jobs)
- [Webhook notifications](https://docs.vaultpanel.net/guides/backups-and-automation/webhooks)

## Two kinds of backup

| Backup | What it covers | Where to manage it |
| --- | --- | --- |
| **Backups** in the panel | The files of a website or app, or the contents of a database. | **Backups** in the sidebar, or the **Backups** tab of a website, app or database. See [Backing up and restoring](https://docs.vaultpanel.net/guides/backups-and-automation/backups). |
| The panel's own backup | VaultPanel itself: its database, settings, secret key and certificate. | The `vaultpanel backup` and `vaultpanel restore` commands on the panel's server. See [Backing up the panel](https://docs.vaultpanel.net/getting-started/backing-up-the-panel). |

You need both. Backups in the panel restore a site, app or database; the panel's own backup restores
every account, setting and the key that decrypts them if the panel's server is lost.

## What runs in the background

The panel's worker handles the scheduled side of automation every 15 seconds: it starts backups that
are due, deletes scheduled backups beyond their keep count, and sends webhook deliveries with
retries. Keep the `vaultpanel-worker` service running, or none of this happens.

Cron jobs are different: the agent writes them into the server's own cron, so they keep running even
while the panel is down. The agent reports each run to the panel with its next request.
