legacy-wp (mysql) in this project needs attention too.
analytics-events (mongo) in this project needs attention too.
hel1-db-01postgresinternal only
Size on disk
7.8 GB
Connections
42/100
42% of limit
Schedules
2
2 enabled
Next backup
Sep 4, 2026, 03:00
gap 24h
Largest table
1.8 GB
pageview
Backup schedules — hel1-db-01
2 schedules · one destination each
| Schedule | Destination | Keep | State | |
|---|---|---|---|---|
| 0 3 * * * Daily at 03:00 | Wasabi eu-central xyte/panel/daily/ | 7 | enabled | |
| 0 4 * * 0 Every Sunday at 04:00 | Hetzner Object Storage xyte/panel/weekly/ | 8 | enabled |
Dokploy exposes the schedule, not the runs — there is no per-run size, duration or exit code to show here. Run history needs a backup_record table, the way deploy records are already persisted.
Destinations
Where this project's backups are written — shared across every database here
Wasabi eu-centralS3in use here
s3://xyte-backups · eu-central-2 · s3.eu-central-2.wasabisys.com
Hetzner Object StorageS3in use here
s3://panel-backups · fsn1 · fsn1.your-objectstorage.com
MinIO on hel1S3not used here
s3://backups · us-east-1 · minio.xyte.be
Runs on the same host as the databases. Fine as the fast-restore copy, not as the only one.
Dokploy exposes no usage or quota per destination, so there is no bar to draw — only provider, bucket, region and endpoint.
Inspector
10 tables · click one for its columns and first rows
| Table | Rows | Size | Idx |
|---|---|---|---|
| pageview | 4,120,000 | 1.8 GB | 6 |
| check_result | 2,140,000 | 96.3 MB | 3 |
| error_event | 986,000 | 412 MB | 4 |
| audit_log | 12,400 | 8.4 MB | 3 |
| deployment | 8,420 | 6.1 MB | 4 |
| error_group | 342 | 1.4 MB | 5 |
| monitor | 24 | 103 KB | 3 |
| env_var | 96 | 80.1 KB | 2 |
| project | 11 | 205 KB | 3 |
| backup_record | 0 | 15.6 KB | 2 |
iduuidproject_iduuidpathtextcreated_attimestamptz
id project_id path created_at ------------ ------------ ------------ ------------ ecab945f-4f1 ebab92cc-4f1 / 2026-09-01 0 e6a94c56-4f1 e7a94de9-4f1 /pricing 2026-09-02 0 a736ad-4f1a ffa7351a-4f1 /features 2026-09-03 1 7aa42524-4f1 7ba426b7-4f1 /docs/gettin 2026-09-04 1 74a1dd1b-4f1 73a1db88-4f1 /contact 2026-09-05 1
Structure and samples need a new read-only probe — no query endpoint exists today. No editing, no DDL, ever.
Docker prune never touches volumes, so cleanup cannot lose these. A volume removal can — that is why the server page's cleanup actions are limited to images, containers and build cache.