@micksta wrote:
Hey there! Just wanting to do a quick sanity check to see if this scenario plays into how syncthing operates.
I have 2 file servers, one at 20TB and another at 10TB.
And a few folders that total up to nearly 10TB, which means this all isn’t going to easily fit on the second server.
Currently have syncthing configured to ‘send/receive’ from the big server, and ‘receive only’ from the littler server.
The ideal plan, would be to only keep the latest X files/directories (managed through another process) and delete any older ones (basic retention of data).
Now I can just disable all the automatic/periodic scanning on the smaller server, so syncthing just keeps getting new files as they come down. But when I click ‘scan now’ or similar, it very obviously tells me there’s local conflicts (missing files), which makes 100% sense and is how syncthing works.
Is there any sort of day to have syncthing ignore local deletes of files, but still receive new changes they come down? (including new files that replace existing ones that might have been deleted locally, etc).
Or is this usecase just simply not catered for within syncthing.
Posts: 4
Participants: 3