1) use a Variable such as %DATE% in the Destination path, e.g.
X:\main folder\%DATE%\
X:\main folder\Backup_%DATE%\
Help -> Search > 'variables' for a full list, including 'components' you can use to make a DATE in a different format, such as %YEAR%_%MONTH%_%DAY% to achieve 'YYYY_MM_DD (and so on)
2) not supported. You could arguably write a callable script (that you call in Programs-After) to do the housekeeping, though if you give sufficient thought when designing such a script (and bear in mind
you would be designing for a specific case/format, using rules you decided, based on parameters you decided to use - whereas 2BS would need to provide something 'general'), it may give some insight into why there isn't any built-in automated functionality to mass-delete stuff that can handle any situation that other profile parameters (also, usage patterns...) might create.
Many people elect to use a 'cycling' Variable (such as %DAYOFWEEKNAME% ) to point to such named locations in turn, and let the profile simply update the earliest location used next time it comes around. This does require 'systematic' use (e.g. daily) to get the best out of such a scheme, though. It's not really suitable for 'ad hoc' run-frequency, as you can quickly lose (mental) track of which day-name (etc) contains the latest backup (dated when?).
Or, you could simply use a static Destination in a profile configured to use Versioning set to keep [in your case, 3] Versions for [as long as you like], and if necessary use the Rollback facility ('nearest to, but no later than specified date/time') that Versioning makes possible during any Restore (if you need one). This method does auto-delete superfluous/expired Versions, because the process of creating them is fixed-mechanism/format, and would not have to handle a 'user-configured, could be (have been / may have changed) anything' situation. Versioning also has the added advantage in that it only keeps one copy of any given incarnation of any file it makes a Version of, and does not make extra copies of files which haven't changed at all (which your idea would), so is potentially hugely less 'space-costly' (thus you can likely afford to keep more old Versions for longer). You can also 'turn down the volume' if you do find space becoming an issue (just reduce the [number] and/or [age] parameters and run the profile again to strip oldest stuff)
Statistics: Posted by cliffhanger — Tue Feb 02, 2016 11:34 am
![[2bs]](http://www.2brightsparks.com/bb/images/smilies/2bs.gif "2BrightSparks")