First: i mirror two folderpairs. All is fine.
Then, i decide a file (or a folder) not to sync and take it to the Filter.
The file or the folder still exist in the Destination.
Is this behavior desired?
volker01
Filter Rules ...
- Posts: 100
- Joined: 14 Feb 2015
-
- Posts: 2272
- Joined: 22 Aug 2012
I suppose "take it to the Filter" means you have added that item to the Exclude filter.
If so, what you describe is the designed-in behavior:
after all you have excluded that item from the sync,
so it will not be affected (in casu: deleted) by the sync.
Whether you find this the desired behavior is up to you ...
If so, what you describe is the designed-in behavior:
after all you have excluded that item from the sync,
so it will not be affected (in casu: deleted) by the sync.
Whether you find this the desired behavior is up to you ...
- Posts: 100
- Joined: 14 Feb 2015
Yes, to the Exclude Filter ...
Do not mirror this file next Mirroring ...
But should this file, then it is in the Exclude Filter - and exist in the destinatation - after next Mirroring - deleted in the Destination?
Do not mirror this file next Mirroring ...
But should this file, then it is in the Exclude Filter - and exist in the destinatation - after next Mirroring - deleted in the Destination?
-
- Posts: 2272
- Joined: 22 Aug 2012
No because, as stated in my earlier reply:
"you have {now} excluded that item from the sync,
so it will not be affected (in casu: deleted) by the {next} sync."
Similarly (and fortunately ...), items not included per the Include filter are not part of the sync, and will not be affected by the sync.
In a Mirror sync, if you do want a Destination item to be deleted after the corresponding Source item has been deleted, do not add such item to the Exclude filter, or remove it from the Exclude filter.
"you have {now} excluded that item from the sync,
so it will not be affected (in casu: deleted) by the {next} sync."
Similarly (and fortunately ...), items not included per the Include filter are not part of the sync, and will not be affected by the sync.
In a Mirror sync, if you do want a Destination item to be deleted after the corresponding Source item has been deleted, do not add such item to the Exclude filter, or remove it from the Exclude filter.
- Posts: 100
- Joined: 14 Feb 2015
Sure but,
i don't won't delete this file in the source.
The goal is mirror files and folders to the destination.
Later i decide some file from the source should not mirrored to the destination,
then ffs should delete this file also in the destination, that is mirroring.
We have three variants in freefilesync:
Two way, Mirror and Update (and custom) ...
When a user won't delete exisiting files in the destination,
then he should use the variant: "update".
i don't won't delete this file in the source.
The goal is mirror files and folders to the destination.
Later i decide some file from the source should not mirrored to the destination,
then ffs should delete this file also in the destination, that is mirroring.
We have three variants in freefilesync:
Two way, Mirror and Update (and custom) ...
When a user won't delete exisiting files in the destination,
then he should use the variant: "update".
- Posts: 1
- Joined: 5 Apr 2018
I agree with volker01. After lots of filter tweaking over the last few years I just recently realized my backups are full of garbage that I had filtered out. When using Mirror I expected those files/folders to be removed. Now my only choices (because manually removing those files isn't an option) are to backup from scratch or write a tool that removes those files... unless that functionality is corrected/added to FreeFileSync.
- Posts: 100
- Joined: 14 Feb 2015
@KronusGT:
The only useful way is: take an new ffs-task, mirror with an empty folder to your destination - (clean the destination),
then run your normal mirror task with your current filter.
This solves not the problem for the future, it's only a workarround.
hope that this will be changed... the filter should only work to the source and not to the destination.
The only useful way is: take an new ffs-task, mirror with an empty folder to your destination - (clean the destination),
then run your normal mirror task with your current filter.
This solves not the problem for the future, it's only a workarround.
hope that this will be changed... the filter should only work to the source and not to the destination.
- Posts: 100
- Joined: 14 Feb 2015
Now i have a situation, where it is useful! that the filter doesn't have an effect to the Destination directory:
On a computer (with NT6.0) i have to split ffs into more than on tasks, because ffs runs on NT6.0 only in 32bit Mode and cannot mirroring all at once.
For that the ffs-config is:
ffs-task1: mirror only folder1 (source-dest.)
d:\userdir\folder1
s:\userdir\folder1
ffs-task2 mirror only folder2
d:\userdir\folder2
s:\userdir\folder2
ffs-task3: mirror all - WITHOUT the dir folder1 and folder2 (is in the filter)
d:\userdir
s:\userdir
In this case - when the filter would not works to the dest. - ffs would delete folder1 and folder2,
and that would be wrong here.
On a computer (with NT6.0) i have to split ffs into more than on tasks, because ffs runs on NT6.0 only in 32bit Mode and cannot mirroring all at once.
For that the ffs-config is:
ffs-task1: mirror only folder1 (source-dest.)
d:\userdir\folder1
s:\userdir\folder1
ffs-task2 mirror only folder2
d:\userdir\folder2
s:\userdir\folder2
ffs-task3: mirror all - WITHOUT the dir folder1 and folder2 (is in the filter)
d:\userdir
s:\userdir
In this case - when the filter would not works to the dest. - ffs would delete folder1 and folder2,
and that would be wrong here.
