this post was submitted on 17 Mar 2026
94 points (97.0% liked)

Selfhosted

60210 readers
1015 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hi community,

I’m one of the maintainers of Portabase, and this is my first time sharing about it on Lemmy.

Portabase is an open-source platform for database backup and restore.

It’s designed to be simple, reliable, and lightweight, without exposing your databases to public networks. It works via a central server and edge agents (like Portainer), making it perfect for self-hosted or edge environments.

It currently supports 7 databases:

PostgreSQL, MariaDB, MySQL, SQLite, MongoDB, Redis and Valkey

Repository: https://github.com/Portabase/portabase

(we hit 500 stars recently!)

Key features:

  • Logical backups for PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey
  • Multiple storage backends: local filesystem, S3, Cloudflare R2, Google Drive
  • Notifications via Discord, Telegram, Slack, webhooks, etc.
  • Cron-based scheduling with flexible retention strategies
  • Agent-based architecture for secure, edge-friendly deployments
  • Ready-to-use Docker Compose setup and Helm Chart

What’s coming next:

  • Increasing test coverage
  • Extending database support

I’d love to hear from you: which database would you like to see supported next in Portabase?

you are viewing a single comment's thread
view the rest of the comments
[–] abecede@lemmy.world 3 points 3 months ago (1 children)

Can you explain to me how the core backup process works? I browsed the git repo, but could not find it after about 10 minutes.

For example PostgreSQL: does it just do a pg_dump of a whole database? Or table for table? What about incremental backups? Are these implemented? And if so, what's the concept behind it?

Otherwise I would not see any use for larger (dozens of gigabytes and more) databases.

[–] KillianLarcher@lemmy.world 3 points 3 months ago (1 children)

Currently, the backup process is logical. Incremental backups are not implemented yet, as supporting them across multiple database systems (PostgreSQL, MariaDB, MongoDB, etc.) would require significant development effort.

The system relies on the database’s native tools when possible, such as pg_dump for PostgreSQL or mongodump for MongoDB. Table-level backups are not currently supported, but could be introduced in the future if there is enough demand.

[–] abecede@lemmy.world 1 points 3 months ago

Thanks for the clarification. Now I know, that I'll stick to my daily cronjob that just runs pg_dump via ssh to another machine. I get e-mail notifications with my simple shell script as well.