Right now I’m creating a nightly restic snapshot of my server on borgbase and on some spare drives, and keeping the snapshots forever. There’s a ton of daily churn in my data though, between databases and logs and other files that don’t constitute ‘real data’ but might be needed to restore the app.
I didn’t really want to poke through each containers files to figure out where it stores logs, plus it adds risk that I’m not backing up something I should.
When I say databases aren’t real data, I’m more talking about them changing every day despite nothing happening. Even if I haven’t taken any photos or opened the app, today’s db dump of immich is not the same as yesterday’s db dump so restic stores it as a new unique file.
I did mean to ask, why restic into Borg instead of just Borg?
on the logs thing that’s fair enough, most of the stuff I use has a clear “logs” folder I can exclude, and I checked what the backup contains Vs what the container data folder has before calling it a day
I’m not doing any sort of backup conversion. Borgbase is a website that focuses on hosting borg backups, but they also natively support restic. I chose restic out of convenience for my local backups because it came preinstalled on truenas and figured it made sense to use the same for my cloud backups.