non existent source folders created, when miroring

[ctmaster]

Hello to all,

I don't know wheter this is unwanted behaviour or not; therefore I think I better ask before start ranting about ab bug.

Following scenario:
I have to backup a file structure from several servers.
These have a file structure which is mostly identical

The emphasis lies on "mostly"

As I'm a lazy guy I created one single batch configuration for all of those machines anyway.
This one covers all possible source folders, I might wish to mirror to my backup.
Not all possible source folders I defined, really exist on every host

In case these source folders provided by my universal batch configuration do not exist, I get a warning on execution.

So far, so good - but when I continue, these source folders, that where only present in my config, get created by confirming the warning.

This definetly is usefull, when having a job, where both sides are synced.
It comes odd, when you have a mirror job, which better should ignore a non-existent folder on the source side.
It's a bit puzzling, when folders you do not expect or want there, are automagically created.

Is there any configuration option, which allows to skip this behaviour ?

Any help is appreciated - best regards

Ray

[Zenju]

Although creating missing target folders automatically is not a bug but the current design, you're right in that it should be refined in the case you describe. Missing folders should only be created by FFS if they really are "target" folders, i.e. at least one item is copied into them.

[Zenju]

Here's the new beta version; target folders will be created on demand only:
[404, Invalid URL: http://www.mediafire.com/download/zwuh3dpsrsikcr0/FreeFileSync_7.6_beta_Windows_Setup.exe]

[ctmaster]

Here's the new beta version; target folders will be created on demand only:
[404, Invalid URL: http://www.mediafire.com/download/zwuh3dpsrsikcr0/FreeFileSync_7.6_beta_Windows_Setup.exe]

Wow, thank you for the fast response on this !
Perfect to have a version, which supports me beeing lazy ... ;)

Serious: it is nice, to have this behaviour skipped.
To create empty source folders, which have not been there before does no damage.
But the result can be really puzzling, as you might run into an unexpected folder structure on the source.

Therefore much kudos !

edit: I already put it do the first test and works perfect so far.

btw.: will this change be implemented to the future stable versions ?

[Zenju]

Yes, this change will be in the next major release.