Best practices and practical solutions for backups?
retained text
I apologize is this is a repeated question. I did not find a helpful (to me) answer yet...
I "discovered" the magic of self-hosting some weeks ago and am in the process of creating more and more services on my small homelab. I'm running Docker on Ubuntu server on a small Dell mini PC. I am quite new-ish to Linux and very new to Docker as a concept. I work as a Windows Sys admin by day.
So, naturally, before hosting any really important data myself, I am trying to learn how to do backups. I had hoped to find a "ready to use" solution but so far was not successful.
Did I understand it correctly that all the data worthy of a backup are *NOT* inside of the containers but in my Compose files or the volumes mounted into the containers?
So my next step would be to create a backup mechanism myself. This seems... daunting.
I think these might be the necessary steps:
* iterate through all my stacks
* stop all containers inside each stack so no file is in active use
* backup all necessary files in TAR.GZ files to a temp directory
* Docker compose files with their .env files
* all volumes used in that stack
* move that TAR.GZ file to my NAS
* remove older backups there
* re-start the containers in the current stack
Do I really have to create such a solution myself? Surely I am not the first person in need of a backup solution... Can you nudge me into the right direction so I do not re-invent the wheel?document fetched 2026-10-20 00:29 · canonical https://reddit.com/r/selfhosted/comments/1xa7fl7/best_practices_and_practical_solutions_for_backups