I specified Firefox to save its bookmarks.html every shutdown to "D:\Firefox Stuff". 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:
The following paths are dependent from each other:
D:\Firefox Stuff
D:\Firefox Stuff\Version Backups
I don't see how they are dependent and why I can't simply do what I want to achieve with FFS. 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.
Also, a feature request:
Allow files from Folder A to be *moved* to folder B and vice versa. Currently, only copying is allowed (or deleting from left or right folder). 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. Imagine dealing with files that are significantly bigger.
Also, 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. Can I do this on FFS currently and if not, is this feature something being considered? It would greatly reduce redundancy for version backups.
Cannot save version backups to subfolder.
- Posts: 3
- Joined: 24 Jan 2016
-
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
I believe the thing you're looking for is the exclude filter. Usually versioning between "c:\source" and "d:\target" works by specifying a third folder "e:\revisions". You can also make this "d:\target\revisions" instead, but then you need to exclude the "revisions" folder from sync, or FFS will include this folders again for sync.
- Posts: 3
- Joined: 24 Jan 2016
What I meant was 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". The "problem" with the way that is currently done (what you said) is that a copy of the file exists in the extra third folder because it is synced from the source folder *then* it is versioned to revisions. FFS is a syncing program to be fair and maybe I'm just trying to bend it too far to backup files to my liking.
-
- Posts: 2453
- Joined: 22 Aug 2012
Your terminology is confusing:
> ... 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".
Note that FFS is a sync-tool that uses (can use) versioning, which is different from revisioning.
Assume you have a one-way sync from "c:\source" to "d:\target".
When running a sync, all files meeting the include filter and not meeting the exclude filter will be copied from "c:\source" to "d:\target" in their existing (sub)folder structure.
After the running the sync for relevant files "d:\target" is a 1:1 copy of "c:\source".
Now assume you have selected Versioning (to folder "d:\prev_verions") as the deletion method.
To the extent that any files pre-exist on "d:\target" prior to running a sync (e.g. from previous syncs) that will/would be overwritten by the new sync, due to the existence of a more recent version of that file in "c:\source", those pre-existing files will be moved as previous version to "d:\prev_verions" (in their (sub)folder structure) before the most recent version will be copied from "c:\source" to "d:\target".
So, unlike is common in revisioning, "d:\target" will only contain the most recent synced versions.
Any previous versions of the most recent synced version of any file will not exist/stay in "d:\target", but rather be moved to "d:\prev_verions".
Whether that is just the latest previous version or all previous versions depends on the Naming Convention you choose.
If you choose "Replace", you will only find the latest previous version in "d:\prev_verions";
if you choose "Time stamp", you will find all previous versions in "d:\prev_verions"
> ... 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".
Note that FFS is a sync-tool that uses (can use) versioning, which is different from revisioning.
Assume you have a one-way sync from "c:\source" to "d:\target".
When running a sync, all files meeting the include filter and not meeting the exclude filter will be copied from "c:\source" to "d:\target" in their existing (sub)folder structure.
After the running the sync for relevant files "d:\target" is a 1:1 copy of "c:\source".
Now assume you have selected Versioning (to folder "d:\prev_verions") as the deletion method.
To the extent that any files pre-exist on "d:\target" prior to running a sync (e.g. from previous syncs) that will/would be overwritten by the new sync, due to the existence of a more recent version of that file in "c:\source", those pre-existing files will be moved as previous version to "d:\prev_verions" (in their (sub)folder structure) before the most recent version will be copied from "c:\source" to "d:\target".
So, unlike is common in revisioning, "d:\target" will only contain the most recent synced versions.
Any previous versions of the most recent synced version of any file will not exist/stay in "d:\target", but rather be moved to "d:\prev_verions".
Whether that is just the latest previous version or all previous versions depends on the Naming Convention you choose.
If you choose "Replace", you will only find the latest previous version in "d:\prev_verions";
if you choose "Time stamp", you will find all previous versions in "d:\prev_verions"
