Versioning has no effect if you use a send-only folder. Versioning stores copies of files which were changed/deleted on a remote. As send-only folders do never accept changes from remotes, there is nothing to be versioned.
Apart from that, your setup sounds good - hard to say anything more useful without knowing your use case. However in general if it works for you, that’s nice
Hi,
Simon thank you for advice.
So in Theory i can disable the file versioning on Rhodan, The File Server.
my first goal to this setup is to preserve the files from Rhodan, creating 3 copies of its 2 TB files on the other computers.
(PSD, docx, jpg and xlsx), 30 or more users accessing a “public” folder.
the others computers; 2 of them is on same network.
(but the users has no access to these computers)
and the 3rd computer is on a remote place kilometers away from Rhodan.
I use Syncthing in a similar way to this. I have remote machines that are receive only and send only machines in my house. Family photos, financial data, that kind of thing. If my house burns down, I’ve only got to worry about getting us out and not our memories. There’s also HDDs in bank vaults which are rsync’d from these machines. If 3 houses (as well as mine) and the banks burn down (which are all more than 15 miles from each other), at least I can say I took reasonable precautions. Probably the end of the world, so more important things to worry about.
I think this strategy is quite common amongst the data paranoid.
I wonder if these systems prevent against ransomware attacks? If a send only filserver (Rhodan) is hit with ransomware would it not send the ransomware to the backup devices and then their entire filesystem would become locked down with the ransomware including the versioned files?
Am I missing something, or is this a realistic concern?
This is counter-intuitive to me, so I was glad to learn this bit of information. I would have thought that versions on the send-side would be saved on the receive-side, up to the limit.
