2 folders, A and B. Each one contains identical files. I create a sub-folder inside folder B and move folder B's file into that sub-folder.
folder A\file.jpg
folder B\sub-folder\file.jpg
folder A on left side, folder B on right side, run compare. The results for the file in folder A are 'item exists on left side only', and the results for the file in folder B are 'item exists on right side only'. Keeping in mind both files are identical.
Now, if I want to synchronize using the mirror setting, it will delete the file in the sub-folder of folder B and copy over the file in folder A. But I don't want that. I want the file to be moved out of the sub-folder and placed in the parent folder so it matches folder A's set up.
I'm dealing with 10s of thousands of large image files. Many of the files already exist in my backup destination, but over time on the drive I have been working from (where new files have been added, which are the ones in need of backing-up) all the folders have been renamed and many levels of sub-folders created.
The only synching option which seems to be available involves deleting everything in the destination and copying everything over fresh. Which seems like a massive waste of time when the files already exist in both locations and could just be rearranged.
How to mirror synchronize by rearranging files already in both locations (but in different folders), without deleting and copying?
- Posts: 6
- Joined: 27 Nov 2012
- Posts: 6
- Joined: 27 Nov 2012
It just seems to me that this should be such an obvious function for synching software that it must be me being stupid and overlooking something. The advantages are clear. Less wear and tear on drives, and less time wasted. Why copy over files which already exist on the other drive and could easily be moved around instead?
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
Just select "detect moved files" in sync settings, and FFS will do what you want for the *next* sync.
- Posts: 6
- Joined: 27 Nov 2012
I feel like I'm being a massive pleb right now, but I cannot see that option anywhere.
Although I just noticed I am still using 5.7. But according to the changelog this feature was introduced to mirror sync in 5.21.
'Detect moved and renamed files and folders' is listed as a key feature, but every syncing configuration I can think of applying results in deletion and then copying, rather than simply moving the files around.
I've seen all the related threads:
viewtopic.php?t=1822
[404, Invalid URL: https://sourceforge.net/p/freefilesync/feature-requests/299/?page=0]
viewtopic.php?t=1334
viewtopic.php?t=1822
And as far as I can gather, this feature should be there. Last I reached a point where I had no choice but to go ahead with a backup, because I couldn't waste any more time fiddling with the settings to figure out how to FFS to 'Detect moved and renamed files and folders'. The mirroring process took more than 6 hours, when it should only have taken 1 or 2 (most of the files being copied over already existed in the destination in the first place, but were pointlessly deleted).
Although I just noticed I am still using 5.7. But according to the changelog this feature was introduced to mirror sync in 5.21.
'Detect moved and renamed files and folders' is listed as a key feature, but every syncing configuration I can think of applying results in deletion and then copying, rather than simply moving the files around.
I've seen all the related threads:
viewtopic.php?t=1822
[404, Invalid URL: https://sourceforge.net/p/freefilesync/feature-requests/299/?page=0]
viewtopic.php?t=1334
viewtopic.php?t=1822
And as far as I can gather, this feature should be there. Last I reached a point where I had no choice but to go ahead with a backup, because I couldn't waste any more time fiddling with the settings to figure out how to FFS to 'Detect moved and renamed files and folders'. The mirroring process took more than 6 hours, when it should only have taken 1 or 2 (most of the files being copied over already existed in the destination in the first place, but were pointlessly deleted).
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
> I am still using 5.7. But according to the changelog this feature was introduced to mirror sync in 5.21.
5.21 > 5.7. So it's time to upgrade :) Detection of moved files has always been active for "two way" sync variant, but it's new for "mirror". Since there is this "cosmetical" drawback of requiring a database file in the base directories, it's opt-in.
5.21 > 5.7. So it's time to upgrade :) Detection of moved files has always been active for "two way" sync variant, but it's new for "mirror". Since there is this "cosmetical" drawback of requiring a database file in the base directories, it's opt-in.
- Posts: 6
- Joined: 27 Nov 2012
aaaaahh... silly me. Thanks for clearing that up. Sorry for the time wasting.
- Posts: 6
- Joined: 27 Nov 2012
Right, the 'detect moved files' is not working for me in mirror mode. I have been running test after test, and getting some strange results.
The first time I run mirror sync between 2 folders, one with the file A in it, and the other with file A within a sub-folder, FFS will delete file A which is in the sub-folder and copy over file A from the other folder. But then if I place the copied file A back in a sub-folder, without closing FFS, and then run the mirror sync again, instead of deleting file A which is in the sub-folder, it will move it out of the sub-folder to match the other folder.
What I'm saying is, FFS is only detecting moved files in mirror mode after I've already done at least one sync. I am not being stupid by forgetting to tick the 'detect moved files' during the first sync. I have run multiple tests.
The first time I always get the recycling bin symbol with the red line, then when running the same test again without closing FFS I will get the arrow with the red line where the recycling bin was during the first test (indicating the file will be moved within the folder, rather than moved to the recycling bin).
This is doing my head in. I absolutely need to sync right now, and I've been wasting my morning running tests. I'll be running mirror sync, and FFS will be unnecessarily deleting thousands of files and copying the exact same ones over again. But there's nothing I can do.
Is there any way I can make FFS remember this session so next time this won't happen again? I am looking at the FFS window right now, the 'detect moved files' box is ticked for mirror mode, and I know for a fact (I can see it right in front of me) that files which exist on both sides will be deleted on one side and copied over from the other. It's just frustrating.
The first time I run mirror sync between 2 folders, one with the file A in it, and the other with file A within a sub-folder, FFS will delete file A which is in the sub-folder and copy over file A from the other folder. But then if I place the copied file A back in a sub-folder, without closing FFS, and then run the mirror sync again, instead of deleting file A which is in the sub-folder, it will move it out of the sub-folder to match the other folder.
What I'm saying is, FFS is only detecting moved files in mirror mode after I've already done at least one sync. I am not being stupid by forgetting to tick the 'detect moved files' during the first sync. I have run multiple tests.
The first time I always get the recycling bin symbol with the red line, then when running the same test again without closing FFS I will get the arrow with the red line where the recycling bin was during the first test (indicating the file will be moved within the folder, rather than moved to the recycling bin).
This is doing my head in. I absolutely need to sync right now, and I've been wasting my morning running tests. I'll be running mirror sync, and FFS will be unnecessarily deleting thousands of files and copying the exact same ones over again. But there's nothing I can do.
Is there any way I can make FFS remember this session so next time this won't happen again? I am looking at the FFS window right now, the 'detect moved files' box is ticked for mirror mode, and I know for a fact (I can see it right in front of me) that files which exist on both sides will be deleted on one side and copied over from the other. It's just frustrating.
- Posts: 6
- Joined: 27 Nov 2012
I just turned on 'show hidden files' and noticed the sync.ffs_db
So I guess everything I was saying is just the way it's meant to be... I suppose it's good for the next time I want to sync. Doesn't help me much this time though. My understand is that there would be performance issues involved in creating a database before the first sync, correct?
Anyway, I shouldn't have needed to go through all that to make this discovery. It should be clearer to new users how FFS works in that regard. It might be useful to update the help guide, and maybe include a little pop-up along with the 'detect moved files' tick box informing users that this won't work during the first sync.
So I guess everything I was saying is just the way it's meant to be... I suppose it's good for the next time I want to sync. Doesn't help me much this time though. My understand is that there would be performance issues involved in creating a database before the first sync, correct?
Anyway, I shouldn't have needed to go through all that to make this discovery. It should be clearer to new users how FFS works in that regard. It might be useful to update the help guide, and maybe include a little pop-up along with the 'detect moved files' tick box informing users that this won't work during the first sync.
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
> FFS is only detecting moved files in mirror mode after I've already done at least one sync
Yes, syncing at least once is required. This isn't about performance, but a logical requirement: In order to notice that something was moved, you first have to know where it was before.
>update the help guide
Yes, this should get some help entry covering usage.
Yes, syncing at least once is required. This isn't about performance, but a logical requirement: In order to notice that something was moved, you first have to know where it was before.
>update the help guide
Yes, this should get some help entry covering usage.
