Hi, I’m pretty new to syncthing, and have been having a few issues on my more complicated syncs. The “typical” use case of syncing “downloads”, “documents” etc between windows devices using a centralized server for versioning is working great.
But I’m wondering if my sync structure is too complicated. And also, the best way to sync that does not also sync the versions etc…
On primary server:
- (A) should be considered the “master” source and is a one way sync to (B)
- © syncs with (D) in a send/receive relationship of all subfolders including (E) and (G). The point is twofold: (D) workstation brings all the items locally so I can edit, rename, etc. videos and photos prior to moving to another folder structure entirely on the primary server. I also have a much longer versioning set on (D) due to essentially a dedicated hard drive on the workstation. Changes made in (D) would ultimately be reflected in (B), (F), and (H).
- (E) syncs with (F) in a send/receive relationship with short duration versioning on (E)
- (G) syncs with (H) in a send/receive relationship with short duration versioning on (G)
the entire private folder is also backed up to offsite storage using a cloud provider.
Although it seems to be working, it does get “stuck” sometimes. Still trying to figure it out and haven’t found a decent resolution other than dropping the folder and re-sharing from primary as it’s the always correct version.
Also, the short duration versioning for the subfolders (E) and (G) get synced to (D) in the © to (D) sync, which is un-necessary.
Primary and Backup servers are both unraid boxes with syncthing 1.13.1 running in linuxserver’s docker. Workstation is a Windows 10 machine, and Phone 1 and 2 are Android Galaxy s8 and s10.All devices are connected on the same local network & subnet.
Any opinions please?
8 posts - 3 participants