Skip to main content
Open a database and select Backup to protect its data. Paid database plans can create daily encrypted recovery points and manual backups. Retention is controlled by the plan.

​
Choose a destination

Pxxl-managed database backups are separate from normal user Storage buckets. Custom destinations require a public HTTPS endpoint, bucket, region, prefix, access key, and secret key. Pxxl verifies the bucket before saving the settings and stores the credentials securely.

​
Recovery point lifecycle

​
Create or restore a recovery point

1

Open Backup

Select the database, open Backup, and choose the destination.
2

Enable daily backups or create one now

Save daily protection, or select Create recovery point for an immediate backup.
3

Wait for Completed

Only completed recovery points can be downloaded or restored.
4

Confirm before restoring

A restore is queued separately and can replace the current database data. Confirm the database and recovery point before starting it.
For S3 fields, AWS CLI checks, IAM policies, object prefixes, and the full storage flow, read Database Backups in Storage.

​
Destination changes

Changing the destination creates a new destination record. A completed recovery point stays connected to the destination and credentials used when it was written, so changing the setting does not move older backups.

​
Troubleshooting

If a backup fails, check the endpoint, bucket region, prefix, and access key permissions. A key that can list a bucket but cannot write to the selected prefix will pass some checks and still fail during backup. If a restore cannot start, check whether another backup or restore is already running. Pxxl allows one active backup and one active restore per database.