I have some directiories that I wish to backup into single directory. That
source directories has some identical files which have to turn into single one
in destination directory. In this case FFS got an error if such identical file
does not exists in destination directory.
Different source dirs and one destination dir
-
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
If multiple directiories shall be merged into a single one, use multiple
folder pairs, set the directories as source on left side, and use the same
directory as target on right side. Then set sync config to "update". This
should do.
folder pairs, set the directories as source on left side, and use the same
directory as target on right side. Then set sync config to "update". This
should do.
I exactly use such a configuration as you said but with a little exception:
- category "Conflicts/files that cannot be categorized" is set to "Copy from left to right overwriting"
- category "Conflicts/files that cannot be categorized" is set to "Copy from left to right overwriting"
-
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
What is the exact problem?
The problem is the following error during syncronization:
> Error moving file:
"S:\Branch\OBranchClient\ORDB_lib.dll.ffs_tmp" ->
"S:\Branch\OBranchClient\ORDB_lib.dll"
Windows Error Code 183: Cannot create file because it already exists
After that error this file (ORDB_lib.dll) does exists in the destination
directory.
I suppose that after first copying of this file your program does not
understand that the file with the same name already exists in the destination
directory and tries to create it instead of overwriting or skipping it.
> Error moving file:
"S:\Branch\OBranchClient\ORDB_lib.dll.ffs_tmp" ->
"S:\Branch\OBranchClient\ORDB_lib.dll"
Windows Error Code 183: Cannot create file because it already exists
After that error this file (ORDB_lib.dll) does exists in the destination
directory.
I suppose that after first copying of this file your program does not
understand that the file with the same name already exists in the destination
directory and tries to create it instead of overwriting or skipping it.
-
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
The issue is that multiple folder pairs on source side have this file, but it
is missing in target directory. When the first folder pair is synchronized it
copies over the missing file. Then the next folder pair also tries to copy
over the same file and the error comes up.
FFS treats folder pairs independently so there is no update on the second
folder pair if the first one already copied the file.
In general it's not easy to deal with this kind of situation because
synchronization of one folder pair may have influence on sync-directions set
for the other pair(s).
If you're using v3.13, did you get the warning message "A directory will be
modified which is part of multiple folder pairs..."?
is missing in target directory. When the first folder pair is synchronized it
copies over the missing file. Then the next folder pair also tries to copy
over the same file and the error comes up.
FFS treats folder pairs independently so there is no update on the second
folder pair if the first one already copied the file.
In general it's not easy to deal with this kind of situation because
synchronization of one folder pair may have influence on sync-directions set
for the other pair(s).
If you're using v3.13, did you get the warning message "A directory will be
modified which is part of multiple folder pairs..."?
> In general it's not easy to deal with this kind of situation because
synchronization of one folder pair may have influence on sync-directions set
for the other pair(s).
You can solve this in the following way: you can make the list of unique
destination directories (if they repeated in the sync pairs) with a
corresponding list of source files with eliminating duplicate file names
according to the settings (for example, add the setting "choose the newest
file if duplicates found").
> If you're using v3.13, did you get the warning message "A directory will be
modified which is part of multiple folder pairs..."?
Yes, I did.
synchronization of one folder pair may have influence on sync-directions set
for the other pair(s).
You can solve this in the following way: you can make the list of unique
destination directories (if they repeated in the sync pairs) with a
corresponding list of source files with eliminating duplicate file names
according to the settings (for example, add the setting "choose the newest
file if duplicates found").
> If you're using v3.13, did you get the warning message "A directory will be
modified which is part of multiple folder pairs..."?
Yes, I did.
-
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
The main grid doesn't really fit for having the same target directory multiple
times: It's easy to (manually or automatically) set conflicting sync
directions for the same file which occurs multiple times. I'm not sure whether
specific types of sync scenarios (like multiple sources, single target) could
or should(!) be recognized by the tool and get further support.
On the other hand an error message in case a file is already existing seems
fine, as this may indeed be unexpected for the user.
times: It's easy to (manually or automatically) set conflicting sync
directions for the same file which occurs multiple times. I'm not sure whether
specific types of sync scenarios (like multiple sources, single target) could
or should(!) be recognized by the tool and get further support.
On the other hand an error message in case a file is already existing seems
fine, as this may indeed be unexpected for the user.
