TL;DR: looking for updated recommendations on software to run a debian-based backup server.
The last thread I found on this topic was 2015, so I'm wondering if the advice has changed.
I run an ubuntu-server-based server (call him "Server"). Server is mostly running docker containers that run different file-serving or home-based apps (actual budget, immich, home assistant, etc.). Server's key files are at:
~/docker_volumes --> Bound folders for each container's volumes letting me access the files (stored on main NVME drive)
/mnt/videos --> Various videos that I serve using Jellyfin in-house (stored on /dev/sda)
/mnt/photos --> Personal photos that I serve using Immich (stored on /dev/sdb)
/mnt/ABC --> My initials, signifying my personal documents or other non-shared creations (stored on /dev/sdc1)
/mnt/DEF --> My wife's initials, for her personal documents etc. (stored on /dev/sdc2)
My one backup solution was to copy those folders onto an eSata drive doing rsync, mounted to /mnt/backup. Unfortunately, said drive died so I lost the backups (but not the originals, mercifully). I'm not making that mistake twice.
I bought 4x 2gb enterprise drives, but I didn't have any more sata ports in Server. I elected to set up those drives in another old machine that I had (call him "Backup"), installed Debian 12 headlessly, and put them together in a RAID5. Using LVM to partition out the root and swap, I have about 5.5TB remaining accessible on /mnt/backup on Backup.
Now what I'm wondering is what's the next best step, since Backup is separate from Server. They're on the same network, albeit in different locations (Backup lives upstairs near an exit door, so if crap ever hit the fan and we needed to get out I'd just grab him rather than trying to fish Server out). What's the best software and networking option to pull those key files out? Is there an easy way to do some versioning of ~/docker_volumes? I don't mind installing straight onto Backup or setting up docker on it as well.
Thanks!
The last thread I found on this topic was 2015, so I'm wondering if the advice has changed.
I run an ubuntu-server-based server (call him "Server"). Server is mostly running docker containers that run different file-serving or home-based apps (actual budget, immich, home assistant, etc.). Server's key files are at:
~/docker_volumes --> Bound folders for each container's volumes letting me access the files (stored on main NVME drive)
/mnt/videos --> Various videos that I serve using Jellyfin in-house (stored on /dev/sda)
/mnt/photos --> Personal photos that I serve using Immich (stored on /dev/sdb)
/mnt/ABC --> My initials, signifying my personal documents or other non-shared creations (stored on /dev/sdc1)
/mnt/DEF --> My wife's initials, for her personal documents etc. (stored on /dev/sdc2)
My one backup solution was to copy those folders onto an eSata drive doing rsync, mounted to /mnt/backup. Unfortunately, said drive died so I lost the backups (but not the originals, mercifully). I'm not making that mistake twice.
I bought 4x 2gb enterprise drives, but I didn't have any more sata ports in Server. I elected to set up those drives in another old machine that I had (call him "Backup"), installed Debian 12 headlessly, and put them together in a RAID5. Using LVM to partition out the root and swap, I have about 5.5TB remaining accessible on /mnt/backup on Backup.
Now what I'm wondering is what's the next best step, since Backup is separate from Server. They're on the same network, albeit in different locations (Backup lives upstairs near an exit door, so if crap ever hit the fan and we needed to get out I'd just grab him rather than trying to fish Server out). What's the best software and networking option to pull those key files out? Is there an easy way to do some versioning of ~/docker_volumes? I don't mind installing straight onto Backup or setting up docker on it as well.
Thanks!
Statistics: Posted by databoy2k — 2024-03-18 19:02 — Replies 0 — Views 5