From what I see, kopia is for the desktop. Unless I didn’t see something, it is not available for android, which is where more important to have backup in my case
Comment on Syncthing alternatives
sorter_plainview@lemmy.today 1 week ago
First and foremost Syncthing is not a ‘backup’ utility. Using it for backup is not at all recommended. Especially if you are dealing with Android or Raspberry pi, because the way clock / time works in these systems are pretty weird and create sync conflicts. So don’t.
Now to the solution. For backup, use a proper backup solution like Kopia. Modern solutions support browsing the snapshots created as backups. Also creating periodic snapshots ensures better redundancy and better chance for disaster recovery.
Now if you will not use it for backup, take a look at ‘Round Sync’ available in F-Droid. It’s an application built around the execptionally good app, ‘rclone’. It is similar to Syncthing, but designed in a very different way. Also it is more difficult to configure to copy the files to PC.
I also wanted to mention that I have used Syncthing for many heavy lifting jobs and never faced issues with it. It is a feature complete app, with the philosophy of doing only one thing and doing it perfectly. So if you run into any issues, do reach out to forums or devs. They will definitely help you.
ZeDoTelhado@lemmy.world 1 week ago
sorter_plainview@lemmy.today 1 week ago
Aah my bad… I was half asleep. What I meant was use Round Sync / Syncthing to copy files to pc and then use Kopia to backup. Round Sync can do one direction copying, so source files are not corrupted.
ZeDoTelhado@lemmy.world 1 week ago
That is something I can totally do after I figure out this syncthing thing. Probably will use Borg backup but same principle applies
milicent_bystandr@lemm.ee 1 week ago
Curious about your point about time conflicts. Doesn’t syncthing look at the change on your machine compared to the ‘canonical’ list also stored on your machine? So even if the timestamp is different, syncthing still detects the change, and the only problem is if the file is simultaneously modified on another machine before being propagated - which would be a conflict anyway.
sorter_plainview@lemmy.today 6 days ago
It didn’t work like that for me. I must admit I didn’t dig deep to clearly see what is the problem. So my setup had a Windows Pc, a Raspberry Pi 5, and an Android phone, sharing a folder which had notes.
Whenever I save any changes in Windows machine, the android used gets updated without much issue, but the Raspberry Pi caused conflicts. When looked at the time stamps they were different and it looked to me like the Raspberry Pi 5 Syncthing is sending the old file as new one, because of the save time.
It read somewhere the issue is with how time is handled in Rasberry Pi. So I disabled the Raspberry Pi Syncthing and went on, because that was not really needed.
milicent_bystandr@lemm.ee 6 days ago
Huh, interesting. I’ll bear that in mind - I don’t like the idea of a system clock error causing an old file to overwrite a new one!