Note that FFS is a sync-tool that uses (can use) versioning, which is different from revisioning.Īssume you have a one-way sync from "c:\source" to "d:\target". if there's a way to avoid a third folder and just have "c:\source" and "d:\revisions" where files overwritten or deleted in "c:\source" will be backed up via versioning on "d:\revisions". Can I do this on FFS currently and if not, is this feature something being considered? It would greatly reduce redundancy for version backups. Imagine dealing with files that are significantly bigger.Īlso, what if I just backup things from FolderA to a FolderC where FolderC is the version backup of things in FolderA whenever things in FolderA change? Currently, it seems that the only way to accomplish something similar is to have FolderA sync with FolderB and then stuff in FolderB that is overwritten or deleted then is then version backuped in FolderC.
For example, using the bookmarks backup scenario above, bookmarks.html created by Firefox will exist on my system but running my FFS batch job will create the same copy in my Version Backups folders-I now have 2 copies of the exact same file and there is no way to delete the original copy and only keep the backup via the FFS batch job. Currently, only copying is allowed (or deleting from left or right folder). My batch job is otherwise created correctly and works as expected if I specify the two folders as folders that where neither is a subfolder of the other.Īllow files from Folder A to be *moved* to folder B and vice versa. I don't see how they are dependent and why I can't simply do what I want to achieve with FFS. The following paths are dependent from each other: I want to save version backups to "D:\Firefox Stuff\Version Backups" but when I run the batch job I created for this purpose, it says the following: I specified Firefox to save its bookmarks.html every shutdown to "D:\Firefox Stuff".
0 kommentar(er)
