Sorry, not sure what you mean by 'historic' files? If you mean old files that (since originally being copied) were (correctly) deleted on the Source as unwanted, but are still present* on the Destination, then the only way to exclude them is 'manually' (on the basis SB doesn't know which ones you don't want, so you have to tell it)
* inter-mingled with files you do want
If you had used a Mirror Right profile, they wouldn't normally be there by now (the profile would have deleted them for you), and if you had used a Mirror Right profile with Versioning**, they would have been deleted from the main backup (so you can get a 'clean' Restore) but would have been moved to a segregated Version repository so that (subject to any number/age limits you set), you can get them back again if they were deleted accidentally. But it sounds as though you used a Backup profile, so it did nothing about now-on-Destination-only files, because you didn't configure it to...
** note that Versioning also keeps Versions of changed files, too. We simply treat deletions as a fairly drastic 'change'. You can set the limits down to [1] Version for [1] day, etc, but
a) that would not give you much time to retrieve accidental deletions
b) it would still keep one extra ('one stage older') copy of each changed file for a short time, on a rolling basis.
* inter-mingled with files you do want
If you had used a Mirror Right profile, they wouldn't normally be there by now (the profile would have deleted them for you), and if you had used a Mirror Right profile with Versioning**, they would have been deleted from the main backup (so you can get a 'clean' Restore) but would have been moved to a segregated Version repository so that (subject to any number/age limits you set), you can get them back again if they were deleted accidentally. But it sounds as though you used a Backup profile, so it did nothing about now-on-Destination-only files, because you didn't configure it to...
** note that Versioning also keeps Versions of changed files, too. We simply treat deletions as a fairly drastic 'change'. You can set the limits down to [1] Version for [1] day, etc, but
a) that would not give you much time to retrieve accidental deletions
b) it would still keep one extra ('one stage older') copy of each changed file for a short time, on a rolling basis.