Password field
TI 2014 Premium
Where the heck is the password field that is referenced in the documentation?
I want to add a password to an existing backup job. Acronis says put a password in the password field. But there ISN'T ANY PASSWORD FIELD that I can find!
That's a very stupid design decision! Did they fire the guy responsible?
So if you decide to add password security to an image in the future, you have to throw away what you have and rebuild the whole job again, which I believe means that if you have an original version of an image file, you lose that also?
Is there some logic to this that would make it make sense that I am missing?
P.S. Why don't I ever receive notifications of response to posts I make here? It hasn't worked this time and I don't think it has ever worked. And this is a brand new Win 8.1 build on new hardware, so everything has been recreated in the last few weeks..
The oiginal tib file is not deleted unless you peform the delete so the tib file without the password is not lost unless you do a delete.
However, you do have to create a new task or clone the old task and. If you clone the old task, you can then edit and updae the changes needed to the password field. Any new task should point to a new task name, and a new target location so the new task is not confused with the old task.
Check out my signature link 2-A for info specific to 2014. Do setup your backup scheme to have automatic cleanup so the task will do its own deletion of old backups.
Posting notification requires two things.
1. When you make the post to checkmark that post to
"Notife me when new comments are psoted"
and
inside your personal account information,
to checkmark that you want to receive notificaton. found under
My account/Edits/ at the end of what is posted under the Edit section.
The oiginal tib file is not deleted unless you peform the delete so the tib file without the password is not lost unless you do a delete.
However, you do have to create a new task or clone the old task and. If you clone the old task, you can then edit and updae the changes needed to the password field. Any new task should point to a new task name, and a new target location so the new task is not confused with the old task.
Which is exactly as I was saying. I have to create a new task, a new backup chain and as per your recommendation EVEN A NEW REPOSITORY! Which means that I have to manage two repositories due to this idiocy until/if I convert the other backup tasks to store in the new repository also.
This was again, a stupid design decision. Why does Acronis keep shooting itself in the feet? Eventually, it's going to fall over and die.
The Acronis True Image application by design structure allows the user to set specific criteria to backup schemes known as tasks. By design it provides for any given number of such tasks to be defined. Not all backup tasks require the same criteria thus the app provides for the user to define all parameters of a task during the task creation process. Once the parameters of a task have been set it is not anticipated that these should change. What is anticipated is that if user needs change, a new task is created to fit those needs. This allows for efficient task management by the application and as an end result provides for the task result as defined by the user.
From my perspective password protection as used in the TI app utilizes Windows DCOM Security Descriptors policies. Those policies are in my perspective the reason that password protection can only be established at task creation and not after the fact.
The Acronis True Image application by design structure allows the user to set specific criteria to backup schemes known as tasks. By design it provides for any given number of such tasks to be defined. Not all backup tasks require the same criteria thus the app provides for the user to define all parameters of a task during the task creation process. Once the parameters of a task have been set it is not anticipated that these should change. What is anticipated is that if user needs change, a new task is created to fit those needs. This allows for efficient task management by the application and as an end result provides for the task result as defined by the user.
From my perspective password protection as used in the TI app utilizes Windows DCOM Security Descriptors policies. Those policies are in my perspective the reason that password protection can only be established at task creation and not after the fact.
That's a lame response that adds nothing to the discussion. Suggest you let Acronis defend their dumb decisions themselves. The fact that you agree changes nothing in the real world. Makes it easier to manage? You cannot be serious! Whew.