Your first post requires manual approval ('Moderation') before it is visible: this is a spam prevention measure. This has now happened (your duplicate post has been deleted accordingly)
Plus, we don't have a version called 'SyncBack Pro SE' - it's one or the other (Pro or SE). The answers may vary accordingly, so it's important to be clear about this (and post in the correct forum section)...
There is a form of per-file Versioning available, but not with single-Zip compression (for technical reasons to do with the Zip format itself)
You'd probably need to use a Variable in the Destination string, but there's no built-in customisable* cycling variable). You could use %DATE% as part of the string (either as a folder, or part of the Zip-name), but that produces an infinite series (obviously, no full date ever re-occurs) and there's no routine to look for and delete older backups (too many permutations that can be affected unpredictably by (e.g.) how often you actually run it).
Hence many people use a cycling Variable. Those available are calendar-based, but a reasonable approximation of what you want is probably to use %DAYOFMONTH% in the string (path or Zip-name). This will follow the date you run it, and cycle at month end, (start again at 1, etc) usefully limiting the number of Zips to the max days in a month
Of course, this has issues where months have less than 31 days (at the end of such a month, Zips 28-31 may not be updated), and in the month thereafter will represent an older month (not the one just ended). The same will happen (older content left as a remnant) if you miss a day (if you miss running the profile on the 19th, for example, Zip-19 will still represent the last time you did run it on a 19th, unless & until you do run the profile on the 19th again). You can delete such older content manually, or simply remember the fact and work around it.
Help > Search > 'variables' (without the quotes) > top hit for a full list of Variables. Bear in mind that some can only be used at/after a certain stage or with certain profile types - as shown.
Or you can devise your own script and run it via Programs-Before or After to delete existing Zips by age and/or total number. Devising such a script to match just the scheme you use, and the pitfalls (which you may or may not figure out before finding out the hard way), may give you some insight as to why there's no such 'general' function that will cope with any scheme a user devises to make multiple backups (and whether or not he adheres to the schema timing)![;)]( "Wink")
* the Pro version supports installable scripting, and there is an example installable script with it that you can use to create your own, but not in the SE version (installable scripting not supported). See what I means about being specific about versions?
Plus, we don't have a version called 'SyncBack Pro SE' - it's one or the other (Pro or SE). The answers may vary accordingly, so it's important to be clear about this (and post in the correct forum section)...
There is a form of per-file Versioning available, but not with single-Zip compression (for technical reasons to do with the Zip format itself)
You'd probably need to use a Variable in the Destination string, but there's no built-in customisable* cycling variable). You could use %DATE% as part of the string (either as a folder, or part of the Zip-name), but that produces an infinite series (obviously, no full date ever re-occurs) and there's no routine to look for and delete older backups (too many permutations that can be affected unpredictably by (e.g.) how often you actually run it).
Hence many people use a cycling Variable. Those available are calendar-based, but a reasonable approximation of what you want is probably to use %DAYOFMONTH% in the string (path or Zip-name). This will follow the date you run it, and cycle at month end, (start again at 1, etc) usefully limiting the number of Zips to the max days in a month
Of course, this has issues where months have less than 31 days (at the end of such a month, Zips 28-31 may not be updated), and in the month thereafter will represent an older month (not the one just ended). The same will happen (older content left as a remnant) if you miss a day (if you miss running the profile on the 19th, for example, Zip-19 will still represent the last time you did run it on a 19th, unless & until you do run the profile on the 19th again). You can delete such older content manually, or simply remember the fact and work around it.
Help > Search > 'variables' (without the quotes) > top hit for a full list of Variables. Bear in mind that some can only be used at/after a certain stage or with certain profile types - as shown.
Or you can devise your own script and run it via Programs-Before or After to delete existing Zips by age and/or total number. Devising such a script to match just the scheme you use, and the pitfalls (which you may or may not figure out before finding out the hard way), may give you some insight as to why there's no such 'general' function that will cope with any scheme a user devises to make multiple backups (and whether or not he adheres to the schema timing)
* the Pro version supports installable scripting, and there is an example installable script with it that you can use to create your own, but not in the SE version (installable scripting not supported). See what I means about being specific about versions?