Is it possible in a future release to have the ability to set versioning to a definable directory?
Reason for the ask is I run an 8Tb drive for very large backup images, however there’s not enough capacity to hold one previous version as well as the current but also, in the event of a drive failure, I would have an earlier version located else where.
I looked at the external option, but I only want to retain one copy of the image so if something happens during the transmission of the latest update, I have a copy of the one prior. I could do something with bat files, but figured it would be easier for St to handle everything.
I will look into symlinks. Not really ever used them.
I think all the versioners technically support archiving to an arbitrary place, but for historical reasons only the staggered versioner allows setting it in the gui.
I would try calmh and AudriusButkevicius’s suggestions but…
The example in external versioning will overwrite files to only keep the latest. If you are changing the name on each backup, each file will be seen as a different file and kept but this will happen with all of the versioners.
If the file names are different after each backup:
The closest you will get is trashcan versioning with which you can set to keep files for 1 day. Keep in mind though, you should expect multiple versions to exist sometimes even if only backing up once a day. Or worse the old version may be deleted before a new one is synchronised.
Trashcan versioning only ever keeps the one version, since it doesn’t rename versions at all. That, with a hack to set the version path, should be the solution here.
Sorry for intrusion. This request reminds to me: anyone remember I suggested months or years ago if ST could retrieve blocks from within the versions? I guess this could dramatically increase the Saved by re… stats
This a known enhancement proposal (see https://github.com/syncthing/syncthing/issues/5279). I would guess that this is a little bit tricky, as Syncthing would need to be able to index those files, while not adding them to the overall local/global state at the same time.
It is a bug, but nothing new - quite ancient actually. The path originally was called versionsPath which was changed to fsPath in https://github.com/syncthing/syncthing/pull/5514 - not in the GUI though. Staggered versioner still accepts versionsPath, thus it’s the only one that works. I’ll fix.
EDIT: I could have also mentioned: The correct key is fsPath - if you use that instead of versionsPath in config.xml it should work.
There is an ugly way to do : create a folder for .stversions (don’t worry with the warning about nested folder) and share with no-one. Set ageing as usual for main folder and no trash for the “Trash” folder (or maybe another trash to get a double stair trash… although I feel easier to increase the main trash ageing).