Backups & restore

Configuration

Configure backups per server, under Backups in the server's Settings. Scheduled backups need the Pro plan or above. Choose any of the server's managed databases, any of its sites' persistent files, or both. Then set a destination and a schedule:

• Endpoint. Any S3-compatible service: AWS S3, Cloudflare R2, Backblaze B2, Hetzner Object Storage, MinIO. HTTPS only.
• Region, bucket, key prefix, and an access key pair. Provisore stores the secret encrypted and never shows it again. Leave it blank on a later save to keep the stored one.
• Schedule. Hourly, daily at an hour you choose, or weekly on a weekday and hour.
• Retention. Keep the last 1 to 30 runs. Provisore removes older ones.

Test connection uploads an object to the bucket with the saved configuration and deletes it again, so a wrong endpoint or key shows up now rather than at the first scheduled run.

What a file backup contains

A file backup holds the site's shared/ directory: uploads and whatever the application writes at runtime. Two exclusions are fixed:

• releases/, which is rebuilt from your repository on the next deploy.
• .env and .env.*. Archives sit unencrypted in your bucket, so recover an environment file from its encrypted environment version.

Everything else under shared/ is uploaded as it is. Add exclude patterns, such as *.log, for anything else you want left out. Patterns match at any depth.

Running and restoring

Run now backs up everything the configuration selects. Each run is listed with its outcome. A failed run notifies your channels with backup.failed, and a successful one sends nothing.

Restore writes a completed run back over the target it came from. A dump goes into its database, and a file archive goes over its site's shared/ directory. It overwrites live data, so you confirm by typing the database name or the site's domain. Restoring needs the admin or owner role.

A file restore never leaves a site without an environment file. It installs the site's current stored environment version into the restored files, or else keeps the .env already on the server. If neither exists, it stops without changing anything.