There isn't any easy way to clean up unwanted files in a Backup profile, due to the nature of what a Backup profile is - which is to store files as a back up even if the Source is moved/renamed/deleted, so that you have the a copy of that original file to fall back on if something goes wrong. This is the main advantage of a Backup profile. Its disadvantage however, is that it fills up your storage space quickly (sometimes with redundant data).
There are ways to run some form of 'housekeeping'. However, such methods usually base its cleanup methods on age of the file. Meaning that it is not intelligent enough to differentiate/look for redundant/repeated files stored on Destination, nor is it able to know that File A is no longer required by you but it hasn't reached the age limit yet (thus not deleting it). Also, as this age rule is strictly adhered to, sometimes it may inevitably remove files which you still need.
The only alternative would be to delete unwanted files yourself manually, but most people consider this as a hassle.![:twisted:]( "Twisted Evil")
But it's the safest way to ensure you only delete files you don't want (not counting human error, of course!)
However, if you want to consider this Housekeeping method, read on.
Set up a new profile to point at an empty (dummy) folder as Source (created for this purpose, and ensured kept empty, e.g. C:\KeepThisEmpty\ ), and to the same backup folder you wish to 'clean up' as its Destination. (That is, the housekeeping profile would use the same location where you keep your backed up files as its Destination)
Then, set the profile type as Mirror Right for this housekeeping profile (so that it deletes files in its Destination that are not present in its Source)
Note that the profile at this stage (without further tweaks) will delete all files in its Destination when run, as the Source folder is empty! So do not run this profile just yet.
One 'further tweak' might be to set the 'Delete from Destination if not on Source' setting (under Decisions-Files page) to use its optional LastModified filter to [XX] days. It will thus ignore any files with LastModified date/time stamps that are within the last [XX] days (etc), but delete the older ones.
However, that simple option uses fixed 'day' units, and involves rounding during the decision-making, and may not process files over X days old but less than Y days old (this may well also be affected by the actual time-stamps of the files versus when you run the profile..and so on)
Alternatively, another option would be to skip that setting in Decisions-Files (leave it at [0] days). Instead, you can add finer-grained control by using the Date & Time option under Expert > Compare Options to add a bespoke age-based limit of which files it processes at all. Do read the contextual Help (press F1 with Date & Time settings page open) for the rounding which is used. You can use large values of smaller units (for example '1440 minutes' rather than '1 day') for finer-grained control up to a maximum value of '65535' of any available unit
You can then run that housekeeping profile as part of a Group which includes the main profiles, or however else you prefer.
Bear in mind that any files that has LastModified date/time stamps that is more than [X period] old, running such a housekeeping profile will delete those files without mercy!
==================================================================================
This proposal is worded to suit a particular situation/requirement. Adjust the general concept and configuration to suit your circumstances. Remember you use such a profile/scheme at your own risk. Test first with stuff you can afford to lose, and definitely do Simulated Runs and check the Differences window closely for what it proposes, fine-tune to suit, etc.
==================================================================================
There are ways to run some form of 'housekeeping'. However, such methods usually base its cleanup methods on age of the file. Meaning that it is not intelligent enough to differentiate/look for redundant/repeated files stored on Destination, nor is it able to know that File A is no longer required by you but it hasn't reached the age limit yet (thus not deleting it). Also, as this age rule is strictly adhered to, sometimes it may inevitably remove files which you still need.
The only alternative would be to delete unwanted files yourself manually, but most people consider this as a hassle.
But it's the safest way to ensure you only delete files you don't want (not counting human error, of course!)However, if you want to consider this Housekeeping method, read on.
Set up a new profile to point at an empty (dummy) folder as Source (created for this purpose, and ensured kept empty, e.g. C:\KeepThisEmpty\ ), and to the same backup folder you wish to 'clean up' as its Destination. (That is, the housekeeping profile would use the same location where you keep your backed up files as its Destination)
Then, set the profile type as Mirror Right for this housekeeping profile (so that it deletes files in its Destination that are not present in its Source)
Note that the profile at this stage (without further tweaks) will delete all files in its Destination when run, as the Source folder is empty! So do not run this profile just yet.
One 'further tweak' might be to set the 'Delete from Destination if not on Source' setting (under Decisions-Files page) to use its optional LastModified filter to [XX] days. It will thus ignore any files with LastModified date/time stamps that are within the last [XX] days (etc), but delete the older ones.
However, that simple option uses fixed 'day' units, and involves rounding during the decision-making, and may not process files over X days old but less than Y days old (this may well also be affected by the actual time-stamps of the files versus when you run the profile..and so on)
Alternatively, another option would be to skip that setting in Decisions-Files (leave it at [0] days). Instead, you can add finer-grained control by using the Date & Time option under Expert > Compare Options to add a bespoke age-based limit of which files it processes at all. Do read the contextual Help (press F1 with Date & Time settings page open) for the rounding which is used. You can use large values of smaller units (for example '1440 minutes' rather than '1 day') for finer-grained control up to a maximum value of '65535' of any available unit
You can then run that housekeeping profile as part of a Group which includes the main profiles, or however else you prefer.
Bear in mind that any files that has LastModified date/time stamps that is more than [X period] old, running such a housekeeping profile will delete those files without mercy!
==================================================================================
This proposal is worded to suit a particular situation/requirement. Adjust the general concept and configuration to suit your circumstances. Remember you use such a profile/scheme at your own risk. Test first with stuff you can afford to lose, and definitely do Simulated Runs and check the Differences window closely for what it proposes, fine-tune to suit, etc.
==================================================================================