Backup4all Forum

I recently realised that I had accidentily added a filter that I had intended to be an "exclude" filter but had actually added as an "include". The effect was that it removed 100 GBytes of (backup) data from a cloud drive and that I also took many days to realise this problem.
I therefore think it should be made very obvious when adding a filter to a job, as the unintended consequence of getting it wrong can be very bad. Maybe highlight (using different colours) the include/exclude field to draw ones attention to it.
Also when creating a B4All "system wide" filter (file/options...) you should be able to set the preference for whether when adding it to a job the filter should default to either include or exclude, as nearly always any added filter is for one or other and not both. This would reduce the likelihood of adding it to a B4All job in the wrong mode.
My point is that for a complex product like B4All with many options, this particular setting (include/exclude filter) is one of the most crucial and should therefore somehow be made difficult to get wrong/miss.

Hi,

I'm sorry to hear about your incident.

We will think about your suggestions.