Bug: Custom Backup schemes cannot be custom named & function correctly.
If the backup scheme name is "custom", there is NO problem. The problem is: Any custom backup scheme with a scheme name other than "custom" will not be correctly configured with options selected by the user.
If user chooses custom scheme and further chooses the "Save As" function to assign a meaningful name to that specific scheme, the task values erroroneously saved into the script will mistakenly be the program default values rather than the options configured by the user. Any custom task with a name other than "custom" name will not be correctly configured with options selected by the user and will function totally different than expected
Some of the script values saved wrongly are listed below but this list may not be conclusive.
Rotation count
Rotation scheme
Quota Chain Count
Quota Capacity
Quota Age
Likewise, the "Save" function (scheme-upper right corner) does not appear to be working--but that may depend upon its function which is not defined.
Likewise, the "Save as default" option (lower left corner of backup opitons) is not properly applied on those custom schemes which have custom names assigned by the user.
Attention to the users:
Custom schemes are still the best choice for backup schemes.
Avoid this problem by not assigning a specific "save as" custom name to any scheme until this bug is fix--sometime in the future--maybe.
This problem can easily be proven.
Create a custom task with a custom name with your unique scheme settings using the "SAVE AS" and "SAVE" OPTION and the "Save as Default" setting. Finally save the task. Write your selected settings down or do screen capture to record your settings.
Save it as a non-scheduled task with backups to be "later" so no backups need to be created.
After the task has been saved, then with that task still selected, Click the options button (lower left) to edit and select the "Backup schemes" header and compare the scheme settings now displayed with the record of the settings you saved. You will find that the settings now displayed will not be those values you configured but rather are program default values. The actual results of any backups will be based on the wrong values displayed on your screen--rather than those you specified in your original custom scheme.
User specified settings saved.
Compare settings. Same settings as shown above should appear below--but do not.
Resulting User backup will not be as user configured.
Thank you Anna,
This issue of wrong custom name also being reported here.
This is not a new issue but an issue which was never fixed in prior version.
This is STILL not fixed (2016 build 5634.) Any ETA?
I have the same problem. Its really annoying and makes the product extremely unhandy.
@ACRONIS: Please fix this bug in TI 2016 a.s.a.p. or you will loose customers!