TheBigBrotherIn your opinion what's the best way to do and restore full backups of a Linux server?
drktBy having it be a container
Elaborate please.
lemmyngThe container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.
Dunno why ppl are down voting you, this us 100% the way.
Architecture as code is amazing, being able to completely wipe your server, re-install fresh, and turn it on and it goes right back to how it was 8s awesome.
GitOps version controlled architecture is easy to maintain, easy to rollback, and easy to modify.
I use k8s for my entire homelab, it has some initial learning curve but once you “get it” and have working configs on github, it becomes so trivial to add more stuff to it, scale it up, etc.
All of my services run on LXC containers. Some files and configs are backed up to NAS and offsite. The containers are snapshotted in their entirety before I do any work on them. A snapshot takes 5 seconds to make and causes no downtime. If I regret a change or mess it up, I can restore the snapshot in under a minute at the cost of some seconds of downtime.
My only non-container machines are my desktop (doesn’t count), my NAS and the Hypervisor. The Hypervisor is very clean and wouldn’t be much fuss to reinstall and the NAS is literally just Debian with NFS. All of these have a regular rsync which runs to backup the important files.
mozzborg
You Borg the whole disk? Or which paths?
See excludes here: wiki.archlinux.org/title/Rsync#Full_system_backup
Nice resource! Thanks
Also, export your DBs first, and snapshot the export instead of the raw DB files
𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍Mine is 3-pronged:
/root change, plus one nightly /home snapshot. but it’s pretty demanding on disk space, and doesn’t handle drive failure; so I also doThe only “restore entire system b/c of screwing up the OS” is #1. I could - and probably should, make a whole disk snapshot to a backup drive via #2, but I’m waiting until bcachefs is more mature, then I’ll migrate to that, for the interesting replication options it allows which would make real-time disk replication to slow USB drives practical; I’d only need to snapshot /efi after kernel upgrades, and if I had that set up and a spare NVME on hand, I could probably be back up and running within a half hour.
EskueroI just stop my containers and tar gzip their compose files, their volumes and the /etc folder on the host
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters LXC Linux Containers NAS Network-Attached Storage NFS Network File System, a Unix-based file-sharing protocol known for performance and efficiency k8s Kubernetes container management package[Thread #931 for this sub, first seen 21st Aug 2024, 08:35] [FAQ] [Full list] [Contact] [Source code]
Rclone with crypt option, to any super cheap cloud storage.
Relax and Recoverfor bare metal backup of the OS critical components and directories, and Deja Dup (or Gnome Backup) for user files
I found UrBackup to be very easy to use. Very little nitty-gritty setup and configuration required to get started. I have a feeling those with more experience will (rightly) pick apart if I’m missing something egregiously bad about it, but it worked for my small homelab use cases.
I use proxmox and proxmox backup server (in a vm). I reinstall them both, and re-add lxc and vm and their drives. har already worked once.
important files are additionaly synced to laptop and phone using syncthing.
proxmox backups (which are encrypted) are rcloned to backblaze for offsite backup
ShimitarDon’t. Backup data, reinstall software.
Answer.