#restic — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #restic, aggregated by home.social.
-
The Restic Off-Site Backup Workflow That Costs Almost Nothing and Encrypts Everything — A Vinyl Burns Workflow
Restic is an encrypted, deduplicated backup tool that works with Backblaze B2 for off-site storage. The cost for 100GB is under $1 a month. -
The Restic Off-Site Backup Workflow That Costs Almost Nothing and Encrypts Everything — A Vinyl Burns Workflow
Restic is an encrypted, deduplicated backup tool that works with Backblaze B2 for off-site storage. The cost for 100GB is under $1 a month. -
The Restic Off-Site Backup Workflow That Costs Almost Nothing and Encrypts Everything — A Vinyl Burns Workflow
Restic is an encrypted, deduplicated backup tool that works with Backblaze B2 for off-site storage. The cost for 100GB is under $1 a month. -
Wochenend-Projekt: **Zerobyte** 💾 #shipit
Ein modernes Backup-Frontend für Restic. Unterstützt S3, SMB, NFS & rclone. Macht Backups endlich wieder schön & einfach! 🚀
Link: https://github.com/nicotsx/zerobyte
#Backup #SelfHosted #Restic #Zerobyte #OpenSource #Homelab #Linux #RadioTux
-
Wochenend-Projekt: **Zerobyte** 💾 #shipit
Ein modernes Backup-Frontend für Restic. Unterstützt S3, SMB, NFS & rclone. Macht Backups endlich wieder schön & einfach! 🚀
Link: https://github.com/nicotsx/zerobyte
#Backup #SelfHosted #Restic #Zerobyte #OpenSource #Homelab #Linux #RadioTux
-
Wochenend-Projekt: **Zerobyte** 💾 #shipit
Ein modernes Backup-Frontend für Restic. Unterstützt S3, SMB, NFS & rclone. Macht Backups endlich wieder schön & einfach! 🚀
Link: https://github.com/nicotsx/zerobyte
#Backup #SelfHosted #Restic #Zerobyte #OpenSource #Homelab #Linux #RadioTux
-
Wochenend-Projekt: **Zerobyte** 💾 #shipit
Ein modernes Backup-Frontend für Restic. Unterstützt S3, SMB, NFS & rclone. Macht Backups endlich wieder schön & einfach! 🚀
Link: https://github.com/nicotsx/zerobyte
#Backup #SelfHosted #Restic #Zerobyte #OpenSource #Homelab #Linux #RadioTux
-
Wochenend-Projekt: **Zerobyte** 💾 #shipit
Ein modernes Backup-Frontend für Restic. Unterstützt S3, SMB, NFS & rclone. Macht Backups endlich wieder schön & einfach! 🚀
Link: https://github.com/nicotsx/zerobyte
#Backup #SelfHosted #Restic #Zerobyte #OpenSource #Homelab #Linux #RadioTux
-
J'ai souvent tendance à réinventer la roue et à mal/pas lire la doc.
Ça me complique la vie et je perds du temps.
Dernier exemple en date: la mise en place de mes sauvegardes avec #restic vers mon #NAS sous #openmediavault
Me suis embêté à vouloir monter un répertoire avec la gestion des droits qui va avec alors qu'il suffisait d'installer #SFTP sur #OVM et dire à restic de l'utiliser.
En jouant avec un HOST SSH parce que restic est susceptible si on utilise pas le port 22. -
J'ai souvent tendance à réinventer la roue et à mal/pas lire la doc.
Ça me complique la vie et je perds du temps.
Dernier exemple en date: la mise en place de mes sauvegardes avec #restic vers mon #NAS sous #openmediavault
Me suis embêté à vouloir monter un répertoire avec la gestion des droits qui va avec alors qu'il suffisait d'installer #SFTP sur #OVM et dire à restic de l'utiliser.
En jouant avec un HOST SSH parce que restic est susceptible si on utilise pas le port 22. -
Just released **restic-monitor** - a small tool that checks your restic backup repositories for stale snapshots and pushes a heartbeat to Uptime Kuma. Silent backup failures are the worst kind.
https://0l.de/blog/2026/04/restic-monitor
https://codeberg.org/stv0g/restic-monitor#restic #backup #selfhosted #opensource #NixOS #golang #UptimeKuma
-
Secure Offsite Backups: Verification & Hardening
Goal: Validate and harden the Restic + SFTP + WireGuard backup architecture.
#sftp #wireguard #hardening #restic
https://medium.com/@nyb.an/secure-offsite-backups-verification-hardening-f70daf1214c7
-
Secure Offsite Backups: Restic + SFTP over WireGuard.
Goal: Build a resilient, encrypted, and isolated backup system that survives total server failure.
#sftp #WireGuard #proxmox #restic
https://medium.com/@nyb.an/secure-offsite-backups-restic-sftp-over-wireguard-2eae5f5882de
-
Se hai un VPS / Server Linux e non hai ancora impostato dei backup automatici, questa potrebbe esserti utile:
Backup con Restic e rclone, guida passo passo, con approccio pratico e semplice da replicare.🔗 https://www.risposteinformatiche.it/backup-automatici-vps-linux-restic-rclone/
-
One thing I want to figure out and build in a robust way is how to verify backups on NixOS via the restic module.
The secret management with sops-nix and per-host backup and restore logic to an append-only server is working. It just needs automatic testing, better notifications, and better insight.
The current idea is to spin up randomly and automatically a new NixOS host, configuring it as one of the others, and verifying if everything is restored correctly.
-
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. 😉
-
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. 😉
-
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. 😉
-
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. 😉
-
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. 😉
-
Mon test de #sauvegarde de mon home avec #restic a fonctionné au poil cette nuit.
-
Mon test de #sauvegarde de mon home avec #restic a fonctionné au poil cette nuit.
-
Mon test de #sauvegarde de mon home avec #restic a fonctionné au poil cette nuit.
-
Mon test de #sauvegarde de mon home avec #restic a fonctionné au poil cette nuit.
-
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/
-
Je comprends pas.
Quand je veux me connecter sur #openmediavault dans le terminal avec la commande #sftp, aucun problème.
Mais pas moyen d’initialiser un repo pour #restic dessus.
Aucune info à part un subprocess ssh : permission denied après la saisie du mot de passe ssh... -
Je comprends pas.
Quand je veux me connecter sur #openmediavault dans le terminal avec la commande #sftp, aucun problème.
Mais pas moyen d’initialiser un repo pour #restic dessus.
Aucune info à part un subprocess ssh : permission denied après la saisie du mot de passe ssh... -
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? 🙏 -
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.
-
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.
-
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.
-
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.
-
Maybe I'm blind but is there any way to monitor a running #resticProfile job?
I know for a plain #restic process I could keep a watcher attached to stdout and tell it to send me json status updates.
From what I gather resticprofile can toggle pre/post/success/fail hooks and write a statusfile after a job is done - I'm mainly interested in how far along a job is though..
-
Okay, fine I give up on my search for a macOS (preferably status-bar) GUI for #restic/ #rustic.
Everything out there seems to be tailored for the WebUI fanatics.
There's ResticScheduler which is great but missing a few crucial features like "abort if pre-run-script fails" as well as the ability to manage multiple backup tasks.
So I guess I'll have to bite the bullet and write my own launchd jobs and some #HammerSpoon or similar magic to monitor those jobs.
(P.S. I'm currently a happy #Arq7 user but the scanning phase for my local and cloud backup has become excruciatingly slow over the past year so I'm trying to once again "find a better thing")
-
Okay, fine I give up on my search for a macOS (preferably status-bar) GUI for #restic/ #rustic.
Everything out there seems to be tailored for the WebUI fanatics.
There's ResticScheduler which is great but missing a few crucial features like "abort if pre-run-script fails" as well as the ability to manage multiple backup tasks.
So I guess I'll have to bite the bullet and write my own launchd jobs and some #HammerSpoon or similar magic to monitor those jobs.
(P.S. I'm currently a happy #Arq7 user but the scanning phase for my local and cloud backup has become excruciatingly slow over the past year so I'm trying to once again "find a better thing")
-
Okay, fine I give up on my search for a macOS (preferably status-bar) GUI for #restic/ #rustic.
Everything out there seems to be tailored for the WebUI fanatics.
There's ResticScheduler which is great but missing a few crucial features like "abort if pre-run-script fails" as well as the ability to manage multiple backup tasks.
So I guess I'll have to bite the bullet and write my own launchd jobs and some #HammerSpoon or similar magic to monitor those jobs.
(P.S. I'm currently a happy #Arq7 user but the scanning phase for my local and cloud backup has become excruciatingly slow over the past year so I'm trying to once again "find a better thing")
-
Okay, fine I give up on my search for a macOS (preferably status-bar) GUI for #restic/ #rustic.
Everything out there seems to be tailored for the WebUI fanatics.
There's ResticScheduler which is great but missing a few crucial features like "abort if pre-run-script fails" as well as the ability to manage multiple backup tasks.
So I guess I'll have to bite the bullet and write my own launchd jobs and some #HammerSpoon or similar magic to monitor those jobs.
(P.S. I'm currently a happy #Arq7 user but the scanning phase for my local and cloud backup has become excruciatingly slow over the past year so I'm trying to once again "find a better thing")
-
Join @aarnoaukia, me and other VSHNeers @vshn today at #KubeCon at the #K8up kiosk P-24A 10:15 - 14:40. Looking forward to seeing you there 🙌
-
Ein neuer Forumbeitrag: https://linux-nerds.org/topic/1836/restic-ui-vorstellung-linux-windows #rust #restic #restic-ui #linux
-
While GNOME 50 is rightfully being celebrated today, it reminded me that I never posted about Déjà Dup 50.
No big changes there, just a nice collection of bug fixes.
But there are some exciting bits of news in Debian/Ubuntu land: Debian finally got the package back in “testing” (it had been blocked by some old Rclone security issues) and Ubuntu finally got Restic into main and switched the default backend to Restic.
So stating with Ubuntu 26.04 there will be a gradual uptick in Restic backups, and hopefully happier Déjà Dup users.
#DejaDup #Gnome #Restic #AppDev -
@stfn I am also playing around with restic and it feels intuitive. Love that it can use rclone.
I tried to set a global exclude file variable (as I assumed it would exist when you can set the repo and encryption key) and saw the discussion [1] around environment variables (since 2017). Sadly no exclude file var in sight.
I found resticprofile [2] that comes to the rescue. Has exactly what I was looking for.
[1] https://github.com/restic/restic/issues/1233
[2] https://creativeprojects.github.io/resticprofile/index.html
-
@schenklklopfer Absolut. Kennst du schon den freundlichen Wrapper rund um #Restic namens #resticprofile?
-
@DocM Erst hab ich #Borg #backup genutzt.
Dann hatte ich damit Probleme.
Jetzt nutze ich #Restic und #Resticprofile, auch weil es 10 mal schneller ist und es weniger Probleme mit dem Cloudspeicher gab.
Wie #Restic und #Resticprofile funktioniert haben @ascherbaum und ich auf den #clt2025 erzählt:https://www.rainerrose.de/docs/writings/2025/#backups-mit-restic-und-resticprofile
-
Whelp, finally got the laptop backing up using #restic to backblaze. If I screw up moving to UEFI really badly, I should be able to restore.
It wasn't hard, but this is only the second system I've set up, so I had to follow the instructions very closely and still had a few missteps.
If you want an inexpensive Linux cloud backup, I can recommend https://github.com/erikw/restic-automatic-backup-scheduler files are encrypted locally, so you don't have to trust the cloud provider. #Backblaze is storing terabytes for me, and I pay very little.
-
At some point in the last few months, deja dup has gotten unbearably slow. When I use duplicity directly with backblaze, my backups take 10 minutes; with deja dup (presumably using restic now) it takes over an hour.
Part of the problem was that at some point in these updates, several of my ignored folders were not being ignored (confirmed by looking at dconf), but I fixed that weeks ago.
Any thoughts?