Backups to your S3
Schedule automatic backups of your database to an Olimpia bucket, AWS S3, Cloudflare R2, Backblaze B2, MinIO, or any S3-compatible service.
You schedule the backups of each database yourself: to an Olimpia bucket or to your own bucket, so your data stays under your control, with your provider and your retention policy. A database with no backups configured has no copies, so set them up as soon as you create it.
Set up
Prepare a bucket
Create a bucket with your provider and an access key with permissions only on that bucket. The key needs to list, read, and write objects.
Open Backups
In your database, open Backups → Configure backups.
Enter the destination
| Field | Example |
|---|---|
| Endpoint | https://s3.us-east-1.amazonaws.com or https://<cuenta>.r2.cloudflarestorage.com |
| Region | us-east-1, or auto if your provider doesn’t use regions |
| Bucket | mi-empresa-backups |
| Access key ID and Secret access key | The ones from the key you created |
Choose frequency and retention
| Frequency | When |
|---|---|
| Every hour | At minute zero of every hour |
| Every 6 hours | Four times a day |
| Every day | 03:00 UTC |
| Sundays | 03:00 UTC |
| Custom | A cron expression in UTC |
In Keep, set how many backups to keep, from 1 to 90. Older ones are deleted automatically.
Save
Olimpia tests access to your bucket before saving. If something fails, it tells you what to check.
Custom frequency
The cron expression has five fields (minute, hour, day, month, and day of week), in UTC, with a fixed minute: at most one backup per hour. The console shows you the next scheduled times before you save.
30 */4 * * * cada 4 horas, a los 30 minutos
0 6 * * 1-5 de lunes a viernes, 06:00 UTC (03:00 en Buenos Aires)
What gets saved
Each backup is a compressed dump of the database (.sql.gz), with the date in the file name. In Recent backups, you can see the files in your bucket and download them directly from the console.
To restore one into another database:
gunzip -c backup.sql.gz | psql "postgresql://app:<contraseña>@pg-<id>.db.olimpia.cc:5432/app?sslmode=require"
Back up now
Back up now runs a backup immediately, without waiting for the next scheduled time. This is useful before a large migration. You can run one every 10 minutes per database.
Disable
Disable stops backups for that database. Files already in your bucket are not deleted.
From your agent
Your agent can set up backups with the MCP server tools. The simplest option is to use an Olimpia bucket in the same project, with no credentials to enter:
Programá backups diarios de la base main en el bucket backups y hacé uno ahora para probar.
It can also use your own S3 if you give it the endpoint, the bucket, and the key. It can change the frequency or retention, and run a backup before a migration.
Examples by provider
| Provider | Endpoint | Region |
|---|---|---|
| AWS S3 | https://s3.<región>.amazonaws.com |
The bucket’s region |
| Cloudflare R2 | https://<cuenta>.r2.cloudflarestorage.com |
auto |
| Backblaze B2 | https://s3.<región>.backblazeb2.com |
The bucket’s region |
| MinIO | https://minio.tuempresa.com |
The one you configured |