Hi everyone.
For the past few weeks, when I synchronize my updated documents (with a scenario I've been using for a long time), certain of the folders added at the end of Decembre 2024 are systematically added, even though I haven't made any changes to them. Note: this only applies to photo folders and files.
As a result, my backup is growing without me knowing why.
Does anyone have any idea what's causing this?
Systematically synchronized folders
-
- Posts: 15
- Joined: 29 Dec 2023
- Posts: 1202
- Joined: 8 May 2006
Have you confirmed that particular file pairs are in fact, identical?
Might something have added meta-data to the files (without changing date/size)?
Might something have added meta-data to the files (without changing date/size)?
-
- Posts: 15
- Joined: 29 Dec 2023
The files are stictly identical, and I have modified nothing and none of the files.
As the files concerned contain only photos, I've taken a look to my photo editing tool (Lightroom Classic): the previous new verson was released in october, a few months before the sync problem appeared...
As the files concerned contain only photos, I've taken a look to my photo editing tool (Lightroom Classic): the previous new verson was released in october, a few months before the sync problem appeared...
-
- Posts: 2946
- Joined: 22 Aug 2012
Your description is unclear:
> As a result, my backup is growing ...
versus
> The files are stictly identical, ...
If the files were/are already in your backup (and are identical), how can your backup be growing?
> As a result, my backup is growing ...
versus
> The files are stictly identical, ...
If the files were/are already in your backup (and are identical), how can your backup be growing?
-
- Posts: 15
- Joined: 29 Dec 2023
That's the point: although the files are identical, without any modification, FFS saves them again. And this is since the end of december: FFS takes again all folders and files of my directory containing my photos.
-
- Posts: 2946
- Joined: 22 Aug 2012
> FFS saves them again
The fact that FFS "saves" your photo files again (as in: re-copies, overwriting/updating files that were already in your right-side backup by identical files) does not make your backup grow.
At most, if applicable, it may make your Versioning location grow, depending on your Versioning settings.
Apparently FFS sees the need to sync your photo files again.
If you run just a Compare in the FFS GUI, you can hoover your mouse over the (proposed) sync action icon in between a left- and right-side item; in your case the green, right-pointing arrow without "+"-sign icon. This will tell you why FFS sees the need to propose the "Update right item" sync action.
The fact that FFS "saves" your photo files again (as in: re-copies, overwriting/updating files that were already in your right-side backup by identical files) does not make your backup grow.
At most, if applicable, it may make your Versioning location grow, depending on your Versioning settings.
Apparently FFS sees the need to sync your photo files again.
If you run just a Compare in the FFS GUI, you can hoover your mouse over the (proposed) sync action icon in between a left- and right-side item; in your case the green, right-pointing arrow without "+"-sign icon. This will tell you why FFS sees the need to propose the "Update right item" sync action.
-
- Posts: 15
- Joined: 29 Dec 2023
Hi and thanx for following my initial question.
In fact, it's less the fact that my sync growes than the fact that I look at the sync report to see what has been modified.
I looked closely to the sync parameters, as you suggested. Nothing special...
To explain what it happens, you well see attached a screen shot of my folders : the first one = original folders, second one = synced folders. As you ca see, on the original folders, only one has been modified today( 2025-03-01 Fre...), but FFS synced ALL off these folders!
For me, it's difficult to undestand...
In fact, it's less the fact that my sync growes than the fact that I look at the sync report to see what has been modified.
I looked closely to the sync parameters, as you suggested. Nothing special...
To explain what it happens, you well see attached a screen shot of my folders : the first one = original folders, second one = synced folders. As you ca see, on the original folders, only one has been modified today( 2025-03-01 Fre...), but FFS synced ALL off these folders!
For me, it's difficult to undestand...
- Attachments
-
- The synced folders
- Destination.jpg (29.06 KiB) Viewed 22004 times
-
- The source folders
- Source.jpg (27.73 KiB) Viewed 22004 times
-
- Posts: 2946
- Joined: 22 Aug 2012
The date of a folder is not relevant.
The date of files that will be / have been synced is relevant to FFS.
Folder creation and modification dates simply follow from the need to apply a sync action to any of the files in a folder or one or more of its subfolders (if any).
As advised before:
Look at the Compare results and hoover your mouse over the green "->+" action icon in between a left- and right-side file for which FFS proposed that action. This will tell you why FFS proposes that action.
The date of files that will be / have been synced is relevant to FFS.
Folder creation and modification dates simply follow from the need to apply a sync action to any of the files in a folder or one or more of its subfolders (if any).
As advised before:
Look at the Compare results and hoover your mouse over the green "->+" action icon in between a left- and right-side file for which FFS proposed that action. This will tell you why FFS proposes that action.
-
- Posts: 15
- Joined: 29 Dec 2023
OK, I undestand that the date of the file is the only to consider.
I have watched closely to the files that are synced, as you recommanded: it's OK the the files REALLY modified by with my photos as precised, FFS propose them to synce although the "From" dates are less than the "To" dates... By howering the mouse, the information is clear : "the right item is more recent than the left", and FFS synces them!!!
I have watched closely to the files that are synced, as you recommanded: it's OK the the files REALLY modified by with my photos as precised, FFS propose them to synce although the "From" dates are less than the "To" dates... By howering the mouse, the information is clear : "the right item is more recent than the left", and FFS synces them!!!
-
- Posts: 15
- Joined: 29 Dec 2023
Hello.
Here attached a copy of the FFS screen after "Compare" operation. Although the "From" files are older than the "To" files, FFS will save them. That's the point that I don't undestand and causes the trouble.
Any idea of the solution to apply?
Here attached a copy of the FFS screen after "Compare" operation. Although the "From" files are older than the "To" files, FFS will save them. That's the point that I don't undestand and causes the trouble.
Any idea of the solution to apply?
- Attachments
-
- ecran FFS.jpg (146.21 KiB) Viewed 21862 times
-
- Posts: 2946
- Joined: 22 Aug 2012
You have selected to use the Mirror sync variant.
That means that FFS intends to make your right side equal to your left side, irrespective of the cause of the differences.
Because your right-side files are different (at least in datetime) from your left-side files, FFS intends to copy those files left-to-right.
Obviously I don't know what is causing the datetime of your right-side files to be different/newer.
The most common reasons are:
• The right-side resource is not able to preserve a file's datetime when being synced/copied to, and the file gets the datetime of the moment of copying. This may e.g. be caused by the protocol used, the operating system or the file-system of the right-side resource.
• Software on your right-side resource is accessing your copied-over files, modifying the datetime to the moment of accessing. The most common sources are virus scanners and indexing tools.
You may consider to use the Update sync variant instead of the Mirror sync variant.
The Update variant will not propose to re-copy left-to-right if a right-side file is newer than its left-side counterpart. Nor will it delete a right-side item if its left-side counterpart was deleted.
That means that FFS intends to make your right side equal to your left side, irrespective of the cause of the differences.
Because your right-side files are different (at least in datetime) from your left-side files, FFS intends to copy those files left-to-right.
Obviously I don't know what is causing the datetime of your right-side files to be different/newer.
The most common reasons are:
• The right-side resource is not able to preserve a file's datetime when being synced/copied to, and the file gets the datetime of the moment of copying. This may e.g. be caused by the protocol used, the operating system or the file-system of the right-side resource.
• Software on your right-side resource is accessing your copied-over files, modifying the datetime to the moment of accessing. The most common sources are virus scanners and indexing tools.
You may consider to use the Update sync variant instead of the Mirror sync variant.
The Update variant will not propose to re-copy left-to-right if a right-side file is newer than its left-side counterpart. Nor will it delete a right-side item if its left-side counterpart was deleted.
-
- Posts: 15
- Joined: 29 Dec 2023
Thank you PIerry for your the follow-up of my problem.
I've had a good look at the different possibilities you present. Clearly, the "Update variant" does the job, but it doesn't suit me because it's a workaround to the problem and I want to have a mirrored backup.
So I proceeded in 2 steps:
A first "Update variant" backup, followed by a "Mirror" backup. And now it looks okay, FFS is back in working order!
I'll keep an eye on the next backups.
Thanks again for your help!
I've had a good look at the different possibilities you present. Clearly, the "Update variant" does the job, but it doesn't suit me because it's a workaround to the problem and I want to have a mirrored backup.
So I proceeded in 2 steps:
A first "Update variant" backup, followed by a "Mirror" backup. And now it looks okay, FFS is back in working order!
I'll keep an eye on the next backups.
Thanks again for your help!
-
- Posts: 15
- Joined: 29 Dec 2023
Hi everyone!
I'm back with the problem described upon (see post #13 for details): although the files are more recent on the right, FFS proceeds to sync the left files.
Precision: the backup is made on a NAS. I have made so many tests : change the mode of sync, delete/copy manually the files on the backup system, reinstall FFS. Always the same problem: FFS re-synces the files although they are unchanged.
Could anybody have a clue or a solution, or simply give me help?
I'm back with the problem described upon (see post #13 for details): although the files are more recent on the right, FFS proceeds to sync the left files.
Precision: the backup is made on a NAS. I have made so many tests : change the mode of sync, delete/copy manually the files on the backup system, reinstall FFS. Always the same problem: FFS re-synces the files although they are unchanged.
Could anybody have a clue or a solution, or simply give me help?
-
- Posts: 2946
- Joined: 22 Aug 2012
> Clearly, the "Update variant" does the job, but it doesn't suit me because it's a workaround to the problem and I want to have a mirrored backup.
Apparently you do not want to have a mirrored backup, because you don't want FFS to overwrite right-side files that have a more recent timestamp than your left-side files.
If you don't address the cause of your right-side files having/getting a more recent timestamp, a Mirror sync will always overwrite your right-side files.
What is it about the Update variant that does not suit you?
For your problem it does the job, so that should be OK.
The only other difference between an Update and a Mirror sync is that the Mirror variant does remove right-side files that exist right-side only, whereas the Update variant leaves such files intact.
If that is the part that does not suit you, you can define your own Custom sync variant, effectively creating a mix of the Mirror and Update sync variant.
You can e.g. do so by
EITHER
• Selecting the Mirror variant and then:
Do not checkmark "Use database file to detect changes", click on the bottom second-right icon (the Action icon for the Difference category "Right side is newer"), until it shows the gray minus sign ("Do nothing"). You should notice the variant has now changed to Custom.
OR
• Selecting the Update variant and then:
Do not checkmark "Use database file to detect changes", click on the bottom-right icon (the Action icon for the Difference category "item exists right-side only"), until it shows the green trash-bin icon with a red minus sign ("Delete right item"). You should notice the variant has now changed to Custom.
Apparently you do not want to have a mirrored backup, because you don't want FFS to overwrite right-side files that have a more recent timestamp than your left-side files.
If you don't address the cause of your right-side files having/getting a more recent timestamp, a Mirror sync will always overwrite your right-side files.
What is it about the Update variant that does not suit you?
For your problem it does the job, so that should be OK.
The only other difference between an Update and a Mirror sync is that the Mirror variant does remove right-side files that exist right-side only, whereas the Update variant leaves such files intact.
If that is the part that does not suit you, you can define your own Custom sync variant, effectively creating a mix of the Mirror and Update sync variant.
You can e.g. do so by
EITHER
• Selecting the Mirror variant and then:
Do not checkmark "Use database file to detect changes", click on the bottom second-right icon (the Action icon for the Difference category "Right side is newer"), until it shows the gray minus sign ("Do nothing"). You should notice the variant has now changed to Custom.
OR
• Selecting the Update variant and then:
Do not checkmark "Use database file to detect changes", click on the bottom-right icon (the Action icon for the Difference category "item exists right-side only"), until it shows the green trash-bin icon with a red minus sign ("Delete right item"). You should notice the variant has now changed to Custom.
-
- Posts: 15
- Joined: 29 Dec 2023
Yes, I cannot assume that a recent right-side file, already synced, should be overwritten by a older left-side file...
So I followed your advice and ticked the right boxes like this :
And that's it.
So I followed your advice and ticked the right boxes like this :
- ffs.jpg (6.32 KiB) Viewed 21414 times
-
- Posts: 2946
- Joined: 22 Aug 2012
> Yes, I cannot assume that a recent right-side file, already synced, should be overwritten by a older left-side file...
But still, that is exactly what a Mirror sync does and should do:
Make the right-side equal to whatever is in the left side.
But still, that is exactly what a Mirror sync does and should do:
Make the right-side equal to whatever is in the left side.
