Reproduction Steps.
While technically speaking it is correct in respect that there's no backup needed in terms of files. However, a snapshot of the new logical view should've been perform.
Also note this is also be true if it was an empty folder instead.
The workaround is to force a filesystem modification (new file/rename/date mod etc) at which there is now new files and areca will copy and then take a new snapshot for the logical view.
I'm in the process of trialing this product and thus far, it has been great. I'm too fussed over this bug as most of my backup will contains modification, deletion and creations all lump together. But it may pose a problem for users who were just culling files and performing a backup.
Apologies on mistake in the title and it appears that I have no access/way to modify it.
It's suppose to be:
Areca 7.x does NOT perform backup when the only changes are deletion
I noticed this in version 7.4.7 (first time I'd come across Areca) and posted in the forum. The release notes for Version 7.5 (released 2015-08-26) mention that this is fixed, and I can confirm I don't see the problem with that version.