Backup Protection is totally broken in TI2014
If i create an backup and set a password for the Backup Protection everything seems to be ok. If you do one backup and try to either change setting or restore the backup you just did you are promted to type the password. This is to be expected.
However, if you now do a subsequent backup the password is from now on no longer needed. You can restore both backups, or change settings in the backup without having to type the password. It seems that the first backup is password protected until you do a second one. If i close TI and re-open it i am not promted to type any passwords.
I just tested to Recover some files for testing purposes and realized that i could recover the files successfully without having to type the password. When i created a new backup job, gave it a password i realized that when you have done more than one backup the password was no longer needed. How can this be true, that i give the backup a password but once you have done two backups it is no longer needed?
Ehh, how did this issue slip through beta testing? Or is build 5560 still in beta?
Please tell me that i am wrong about this. This worked in TI2013.
OS: Win 8
- Anmelden, um Kommentare verfassen zu können
Hello Roger, Grover,
thank you for your posts.
Grover, the program behavior that you are describing is expected and it can be considered as feature, namely, the so called-session password. It means that within one session (from opening console till closing it) you should enter password only once. But after closing and re-opening of the console password should be requested again.
Roger, please check once more, whether in your case password is requested after console re-opening. If it isn't, please let me know it and then contact our support team for investigation.
Thank you.
- Anmelden, um Kommentare verfassen zu können
Anna,
The 2014 appears to been the same as the 2013 in this regard.
However, I believe this behavior is not what most users would want and definietly not what I expected.
My preference would be that once a password task is opened or edited and the edits saved, the task should be closed.
Any re-edit of the same task (even if immediately), the password would be again required to reopen the task for additional use or edits.
- Anmelden, um Kommentare verfassen zu können
Hello Grover,
I've forwarded your feedback to development team.
Thank you!
- Anmelden, um Kommentare verfassen zu können
GroverH wrote:Anna,
The 2014 appears to been the same as the 2013 in this regard.
However, I believe this behavior is not what most users would want and definietly not what I expected.
My preference would be that once a password task is opened or edited and the edits saved, the task should be closed.
Any re-edit of the same task (even if immediately), the password would be again required to reopen the task for additional use or edits.
2nd this. (and wanted to subscribe)
- Anmelden, um Kommentare verfassen zu können