Den heutigen Tag ernenne ich zum Tag des Backups. Gefühlt habe ich mich nur um Backups in verschiedenen Szenarien gekümmert.

1. Windows Server Backup mit #VSS
2. #Veeam für Hyper-V
3. Skript für #restic angepasst
4. Mit #Powershell für einen Updatedienst herumgespielt

#Restore mache ich dann morgen. 😉

#backup

I use restic for backups. Great but it is cumbersome to build up some regular update strategy around that. However there is a create tool resticprofile. https://creativeprojects.github.io/resticprofile/index.html, to close that gap. One can schedule backups for example via Systemd Timers. This tool is even mentioned in the official docs of restic itself, https://restic.readthedocs.io/en/stable/040_backup.html#scheduling-backups.

One caveat it has no packages in the official Linux distributions.
However it has build binaries on github.

#restic #ResticBackups #backup

New blog post!

I finally started writing about my home lab. This post is about how I back up data using restic.

Full story: https://britter.dev/blog/2026/04/10/home-lab-backup-with-restic/

#homelab #selfhosting #nixos #restic #backup

Is there any good zero-trust cloud solution out there? My dream would be something like #Restic that would put locally-encrypted blobs on any distant storage and would open it as a FUSE volume.
Does something like this exist? 🙏

Edit for clarification: I'd like to store files remotely, but with client-side encryption, so they're still safe if the remote server is compromised (and so I can backup them to another non-trusted server easily if needed).

Split my big "backup-verify-prune" script that runs on my homelab (and consumes quite a bit of bandwidth when running the verify) to three scripts.

Backup runs on homelab. If completed successfully, it will ssh to a VPS to run the verification. If that completes successfully, it will ssh back to to my homelab to trigger the pruning.

All steps are monitored, all accounts are locked down to the minimum they need to work. Secrets are stored in a (shared) vault.

Hoping to decrease my monthly bandwidth usage from 6+TB to something a bit lower - and speeding up the process, as the VPS has a lot faster internet connectivity than my home.

#homelab #restic

Sooo, #backrest is not really my thing either. You can't change the connection settings of an existing repository, which means no credential rotation and no clean way to handle IP changes when a server moves. That's a pretty fundamental limitation for a backup solution.

I'll take a closer look at #restic without relying on a frontend.

I'm also skeptical about #Borg #Backup and, more broadly, backup tools built on Python/Ruby/shell stacks. There's a lot of room for subtle breakage without strict type safety, and pushing performance-critical parts down into C/C++/ASM layers doesn't exactly inspire confidence either.

Makes me wonder what enterprise solutions look like under the hood. Apparently #Veeam is C#, which is actually a reasonable choice - but requiring a Windows server (and not being OSS) makes it a non-starter for me.

#DigitalIndependenceDay meets #WorldBackupDay (March 31st)! Backups are key to #digital #sovereignty. My 3-2-1 strategy: 3 copies, 2 media, 1 offsite — no #hyperscaler needed. I recently migrated from #BorgBackup to #Restic: better multi-repo flexibility, same solid encryption and deduplication. Offsite storage goes to a #Hetzner Storage Box, which is significantly cheaper than #AWS #S3 and the data remains in #Europe.

https://di.day

#did #diday #didit #ididit #dut #dutgemacht