OK, now talking #backup tools for/with #ubuntu for people like me - being in-between noob and nerd status, having a bit of experience with console scripting and being capable to get solutions by using online search. Recently discovered #Borg plus #Volta GUI which sounds like a very capable deduplicating combo. Also stumbled about #Kopia that is advertised as being simpler but you know, this doesn't sound appealing.

What would you recommend as backup tools/strategy for private usage?

Saferlayer: gehitu segurtasun extra bat zure nortasun agiriaren kopiei

Nortasun agiriaren kopia emailez edo beste moduren batean bidali behar duzunerako, Saferlayer webguneak seguruago egiten lagunduko dizu

https://teknopata.eus/2025/03/saferlayer-gehitu-segurtasun-extra-bat-zure-nortasun-agiriaren-kopiei/

#Kopia is great. At least it didn't fail me so far. However, here are my gripes about it:

1. You need to run separate instances if you want to use multiple repositories
2. The cache and logs folders can bloat that they sometimes occupy significant server storage.

@thestrangelet have a look at kopia. I'm using it with Backblaze B2. #Kopia

I wrote up a detailed review of using Kopia and rclone to back up my MacOS home directory to OneDrive. Along the way I create an APFS snapshot and use launchd to manage scheduling.

https://blog.koehn.com/posts/kopia-mac-onedrive/

I use #TimeMachine to my #NAS for backing up my MacBook, which works great and has occasionally bailed me out. But I recently learned that my preferred backup tool #kopia that I use on my #Linux servers, can back up to #OneDrive. My OneDrive account comes with 1TB of storage, and I only use about 10GB of it. So now I have offsite backups of my home directory in case things really go kablooey.

I use launchctl (the MacOS equivalent of systemctl) to manage running the backups unattended. Works great.

Ich habe schon viele Backup-Lösungen ausprobiert, aber #Kopia bietet IMHO das beste Gesamtpaket. Dank der GUI ist es auch für Einsteiger (nach Eingewöhnung) leicht bedienbar. Falls ihr nach einer Backup-Lösung sucht: Unbedingt anschauen!

https://kopia.io/

Finally managed to fix my permission issues with the 2 NFS CSIs I'm running on my #k3s cluster, and all the apps are back to a working state. Including #immich, my most important app on the new cluster by far.

Now that it's holding over 300GB of my photos, and knowing it takes significant time and resources to ingest media, it's time for getting #kopia configured to back all of this up to #backblaze. Thankfully that seems to be going pretty well!

Backups auf dem neuen Server sind nun auch eingerichtet und werden dann zu mir nach Hause geschickt.
Lieber einmal eine alte HDD dafür opfern anstatt irgendwo nen Terrabyte oder zwei zu bezahlen.

Diesmal versuche ich es mal mit #kopia - sieht pauschal schon mal ganz nice aus und ist relativ leicht zu benutzen, wenn man erstmal verstanden hat, wie das mit so funktioniert (also alles wie immer eigentlich)

What's the current hotness for backups? Looking at #kopia and #borg, both seem pretty straightforward. #rsync is a workhorse but I'm trying to play around with using #resilio to replicate data to a centralized nas and then do something locally for back ups.

Artikel, die mal jemand schreiben müsste:

#Backup unter #Linux: #Borg / #BorgBackup[1], #Kopia[1] oder #Restic[3]?

Aber naja, das vernünftig zu machen -- also inklusive Praxistests über mehr als nur ein paar Tage -- ist schrecklich viel Arbeit, für die in der heutigen Medienwelt niemand mehr adäquat bezahlt.

[1] https://borgbackup.readthedocs.io/
[2] https://kopia.io/
[3] https://restic.net/

I am trying to use #Kopia to backup my #OneDrive to my #Linux NAS. The problem I'm having is that Kopia is making cloud only files download when it makes the backup.

It seems that even using ignore rules does not prevent the files from being downloaded.

Is their an easy way to fix this or will I have to reorganize my one drive and only backup specific directories?

I had a #SyncThing issue. I'm running a local #Kopia backup server in #Docker to collect backups from multiple computers. I'm replicating this folder to secondary server with SyncThing. The source folder is shared as "Send Only" to prevent any changes to propagate back.

Somehow the destination SyncThing collected ghost files. The source folder has about 100k/3TB files. Same number was in source SyncThing and destination folder, but destination SyncThing thought there were 150k files. And the number stuck even after all syncing and restarting.

Fix was to completely reindex the destination. There is no (AFAIK) GUI option to do it but i found an API call. I paused the destination folder and ran in destination server

curl -X POST -H "X-API-Key: <apikey>" http://localhost:8384/rest/system/reset?folder=<folderid>

It took awhile to run and *very* long time for SyncThing to rescan the folder, but in the end it fixed the issue.
#HomeLab

Another migration long overdue was getting off Dropbox.

Here is what I implemented a few days ago - in the middle of my Windows to Linux migration, doh! - but its going well so far.

Seemed complicated at first and ran into a few quirks, but is turning out to be exactly the right thing to have done.

Anyone got other approaches that have worked well for them let me know.

#dropbox #syncthing #kopia #backup #data

https://markdkberry.home.blog/2024/06/04/opt-for-privacy-transition-from-dropbox-to-syncthing-and-kopia/

So does #Kopia do disk imaging, or no? I ask because I'm looking for a good alternative to #MacriumReflect , saw some stuff here and in a web search that they ended support of the free version and I want to get off Mr. Bone's wild ride (late-stage capitalism and #proprietary software).