Comment on Portabase v1.7.1 - Open source database backup/restore tool
RadDevon@lemmy.zip 1 week ago
This looks exciting! A couple of questions:
- 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.
- 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 1 week ago
Hi,
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.
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 6 days ago
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 6 days ago
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!