Syncthing alternatives
-
Yea, gotta be something odd with your setup.
Currently I have one phone (of several) thats syncing en excess of 10,000 files, some only on Wifi (with 3 access points), some wifi/cell data.
ST knows the state of a file, so a disconnect should have no effect. If you're getting corrupted files, I wonder if something else is going on which may also affect another sync tool.
Try Resilio for the same folders, see if you have the same problem (disable Syncthing of course, otherwise conflicting edits will cause file corruption).
I checked their page and I have now a personal license. I am going later to try to find out how it works, so we will see
-
Dug into it, got into Memtest’s source code and discovered that the first pass is shorter on purpose so that it quickly flags obviously bad RAM. Apparently if you want to detect less obvious issues, you have to run multiple passes.
I thought it was common knowledge that Memtest needed to be run for multiple passes to truly verify there are no issues. Seems that's one of those things that stopped being passed down in the community over the years. Back when I was first learning about overclocking around 2005 that was emphasized HEAVILY, with the recommendation to run it at least overnight, and a minimum of 10 passes.
The software should inform the user to run atleast 10 passes in the UI
-
That sounds like a crazy story to find out what the issue was. As I stated somewhere on the thread, ram is not the issue, and the APS are quite new (Aruba stuff that is 1 and a half year old). And the only situation I get this issues is with my phones in specific. I will probably use the smb solution stated before and see how is goes. If the thing still happens, then is hunting time
Good hunting
-
Is Syncthing my ideal backup application?¶
No. Syncthing is not a great backup application because all changes to your files (modifications, deletions, etc.) will be propagated to all your devices. You can enable versioning, but we encourage you to use other tools to keep your data safe from your (or our) mistakes.
https://docs.syncthing.net/users/faq.html#is-syncthing-my-ideal-backup-application
Sync is sync. Sync is NOT backup.
Would syncing your backup directory work? Like take snapshots of your system, dump the snapshots all in a single directory, and sync it to an off-site location?
-
Would syncing your backup directory work? Like take snapshots of your system, dump the snapshots all in a single directory, and sync it to an off-site location?
No, re-read above.
-
Would syncing your backup directory work? Like take snapshots of your system, dump the snapshots all in a single directory, and sync it to an off-site location?
Kind of. That improves your backup safety, but doesn't mitigate all the risks. E.g. if you accidentally delete everything from your backup directory, then all those deletions also happen on the sync'd one.
-
I am using rsync triggered by cronjobs for this task now for... well... nearly forever.
If you ask Syncthing how to do local sync (e.g. to an external HDD), the answer is, use the right tool for the job: Unison.
If you ask Unison how to do certain things (directory timestamps is the one I miss), the answer is, use the right tool for the job: rsync.
In the end, it all comes down to rsync.
P.S. I'm actually gradually migrating up the chain from rsync, having used my own hand-built utility to make convenient rsync commands, but now using syncthing and Unison more.
-
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 some what 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.
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.
-
Hi,
As the title suggests: what are alternatives to syncthing that are basically fire and forget, works on multiple device types, and just focuses on file syncing?
I've had over the months the weirdest problems with syncthing, and lately I noticed some of my photos got corrupted, which is an absolute no no for me. I use syncthing currently as a easy automatic backup of documents, photos and other files, between my PCs and my phones (they all send only to the server. Folders are not shared with other devices).
I had some similar and obscure corruption issues that wound up being a symptom of failing ram in a main server node. After that, only issues have been conflicts. So I'd suggest checking hardware health in addition to the ideas about backups vs sync.
-
Is Syncthing my ideal backup application?¶
No. Syncthing is not a great backup application because all changes to your files (modifications, deletions, etc.) will be propagated to all your devices. You can enable versioning, but we encourage you to use other tools to keep your data safe from your (or our) mistakes.
https://docs.syncthing.net/users/faq.html#is-syncthing-my-ideal-backup-application
Sync is sync. Sync is NOT backup.
This is why you should have file history versioning on. With backup this is a most.
-
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.
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.
-
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.
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!
