this post was submitted on 17 Mar 2026
85 points (96.7% liked)

Selfhosted

58172 readers
465 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 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
[–] RadDevon@lemmy.zip 3 points 2 weeks ago (3 children)

This looks exciting! A couple of questions:

  1. How would I deploy an agent into an existing docker container in a way that makes it persist across restarts? Most of my databases are running in containers.
  2. Regarding redis and valkey: what good does backup do without restore? Not trying to denigrate; I just really want to understand how that is useful.

Thanks for building this!

[–] KillianLarcher@lemmy.world 2 points 2 weeks ago (2 children)

Hi,

  1. The agent need to be on the same network as your database. You can either include the agent in the same Docker Compose setup or create a Docker network to link them. I’m not sure what you mean by 'persist across restarts.' Can you clarify? However, it works perfectly fine with databases running in Docker.

  2. For Redis and Valkey, hot restores are unfortunately not supported. You need to stop the services and perform some manual operations. This limitation is why backups are mainly useful for disaster recovery rather than live rollback.

Feel free to ask any other questions or clarification if needed.

[–] RadDevon@lemmy.zip 1 points 2 weeks ago (1 children)

Thanks for the clarification. By "persist across restarts," I'm referring to the fact that if I just install the agent in my container, it won't persist if I restart the container, unless I install it on a volume which seems clunky. Running the agent alongside in a separate container with network access is the solution I was looking for.

On the Redis and Valkey restores, that makes sense. Disaster recovery is my use case anyway. Do you document the manual restore process for those? I didn't notice it in a brief review of the docs, but I may have overlooked it.

[–] KillianLarcher@lemmy.world 1 points 2 weeks ago

Do you document the manual restore process for those?

No, we haven’t documented it yet, but that’s a good idea. I’ll add it to the backlog, and we’ll work on it soon!