Hi, it's possible, more or less, using week-numbers as your incrementing values. Week-number values will repeat again next year, thus will use the same locations (folders so-named) and thus housekeeping (deleting and/or updating out-of-date stuff from previous year as the same week occurs this year) can be (mainly) automated - unlike when using unique (or semi-unique) values like Dates which you should avoid* at all costs.
Unfortunately, due to our badly-organized planet, week-numbering isn't 100% perfect either as the days-in -year does not divide equally by 7, so in some years you get a week-53 and in other years you do not. But if you are prepared to live with the fact that some years won't have a week-53 so will not delete/refresh the (old) contents of a pre-existing week-53 folder (if any), it can be done thus, paraphrasing the example for Daily on the Help page for Fast Backup)
To keep 52/53 weeks worth of backups, and have a full-backup on first Saturday and incremental backups on all the other Saturdays of the year:
Create a backup profile and configure your source as appropriate
Set the Destination to something (the %WEEKOF% is required) like D:\Weekly Backups\%WEEKOF%\
Go to the Fast Backup tab and enable the options: Perform a fast backup and Delete all the files and folders in the destination before the backup, and set the full-backup folder to D:\Weekly Backups\1\ (or, D:\Weekly Backups\FULL\ if you prefer)
In the "Force a re-scan when:" box select the %WEEKOF% item, select Equals from the drop-down list to the right of the box, and enter 1 into the box to the right of the drop-down list
You should schedule the profile to run just once every Saturday
In a year that has no week-53, you would need to diarise to delete any old week-53 folder from the previous year at or just after the time it would be refreshed with last-week-of-current-year stuff if things were different.
Note: %WEEKOF% uses ISO rules to calculate its value - more details in Variables > Weeks section of SB Help (or Google)
* unless you are prepared to manually delete the oldest incremental folder-by-date. Why? Because the same Date will never ever occur again if it includes Year, and will on average only match reality once per 7 iterations if you only use Day/Month to identify a particular Saturday. For example, 07-01 is first Sat in 2017 but first Sat in 2018 is 06-01, so instead of flushing/re-using the same folder it would create a new neighbour.
Unfortunately, due to our badly-organized planet, week-numbering isn't 100% perfect either as the days-in -year does not divide equally by 7, so in some years you get a week-53 and in other years you do not. But if you are prepared to live with the fact that some years won't have a week-53 so will not delete/refresh the (old) contents of a pre-existing week-53 folder (if any), it can be done thus, paraphrasing the example for Daily on the Help page for Fast Backup)
To keep 52/53 weeks worth of backups, and have a full-backup on first Saturday and incremental backups on all the other Saturdays of the year:
Create a backup profile and configure your source as appropriate
Set the Destination to something (the %WEEKOF% is required) like D:\Weekly Backups\%WEEKOF%\
Go to the Fast Backup tab and enable the options: Perform a fast backup and Delete all the files and folders in the destination before the backup, and set the full-backup folder to D:\Weekly Backups\1\ (or, D:\Weekly Backups\FULL\ if you prefer)
In the "Force a re-scan when:" box select the %WEEKOF% item, select Equals from the drop-down list to the right of the box, and enter 1 into the box to the right of the drop-down list
You should schedule the profile to run just once every Saturday
In a year that has no week-53, you would need to diarise to delete any old week-53 folder from the previous year at or just after the time it would be refreshed with last-week-of-current-year stuff if things were different.
Note: %WEEKOF% uses ISO rules to calculate its value - more details in Variables > Weeks section of SB Help (or Google)
* unless you are prepared to manually delete the oldest incremental folder-by-date. Why? Because the same Date will never ever occur again if it includes Year, and will on average only match reality once per 7 iterations if you only use Day/Month to identify a particular Saturday. For example, 07-01 is first Sat in 2017 but first Sat in 2018 is 06-01, so instead of flushing/re-using the same folder it would create a new neighbour.
Statistics: Posted by cliffhanger — Wed Dec 20, 2017 11:18 am