I backup “everything” from my raspberries, and just \home for laptops but for an actual disaster recovery I’d just do a clean install, get an IP address and then reinstall everything via Ansible, then drag my home data back off the NAS
But… I like that statement. I’ll use that at work.
Is your NAS on site? If it is not backed up: I used to follow a 3-2-1 strategy, 3 separate copies, 2 mediums, 1 off site. I have sorta feel to a 2-2-1, I am wanting to get to a 2-2-2ish.
I was following a 2-2 strategy but then 3 houses went went up in flames down the street.
The NAS is on site, yes. It’s backed up to Hetzner - inc. it’s own /etc, /home, etc. so the NAS itself is kinda a 2-1 (2 backups, 1 offsite), but it would be a lot of rework to restore and that’s the device I’d need to recover everything else in case of a total disaster (like a house fire).
(🤔 better check the Hetzner encryption is noted in my keypass file)
I do need to get it’s config setup in Ansible though so it can be rebuilt automatically, but Ansible for single devices can be a little overkill and difficult to maintain.
Similar for my hypervisor box… damn… there goes some more evenings…
I do not have much that I I cannot just rebuild and retune so I got a little VPS, to backup my irreaplaceables and host my blog all the docker images can be replaced the pi’s can be replaced.
The encription I chose was age, I had just asked Vibe what the best option for me would be, wish I had chosen differently, maybe some day I will sit my butt down for a few days and figure out a new strategy. I wish I had chosen differently because it is coded in Go.
Looking Go up to see if there has been any big issues found with it I see that other major parts of my homelab are also coded, in full or in part, with Go. Most importantly Caddy followed closly with Docker so maybe I will not worry to much about Age being coded in Go! Without Caddy, fuck this girl aint remembering port numbers.
Nice philosophy.
I’m kinda in the middle ground here.
I backup “everything” from my raspberries, and just \home for laptops but for an actual disaster recovery I’d just do a clean install, get an IP address and then reinstall everything via Ansible, then drag my home data back off the NAS
But… I like that statement. I’ll use that at work.
Is your NAS on site? If it is not backed up: I used to follow a 3-2-1 strategy, 3 separate copies, 2 mediums, 1 off site. I have sorta feel to a 2-2-1, I am wanting to get to a 2-2-2ish.
I was following a 2-2 strategy but then 3 houses went went up in flames down the street.
The NAS is on site, yes. It’s backed up to Hetzner - inc. it’s own
/etc,/home, etc. so the NAS itself is kinda a 2-1 (2 backups, 1 offsite), but it would be a lot of rework to restore and that’s the device I’d need to recover everything else in case of a total disaster (like a house fire).(🤔 better check the Hetzner encryption is noted in my keypass file)
I do need to get it’s config setup in Ansible though so it can be rebuilt automatically, but Ansible for single devices can be a little overkill and difficult to maintain.
Similar for my hypervisor box… damn… there goes some more evenings…
I do not have much that I I cannot just rebuild and retune so I got a little VPS, to backup my irreaplaceables and host my blog all the docker images can be replaced the pi’s can be replaced.
The encription I chose was age, I had just asked Vibe what the best option for me would be, wish I had chosen differently, maybe some day I will sit my butt down for a few days and figure out a new strategy. I wish I had chosen differently because it is coded in Go.
Looking Go up to see if there has been any big issues found with it I see that other major parts of my homelab are also coded, in full or in part, with Go. Most importantly Caddy followed closly with Docker so maybe I will not worry to much about Age being coded in Go! Without Caddy, fuck this girl aint remembering port numbers.