SCHEDULING BACKUPS USING T. I. HOME 2010
I am using Acronis True image Home 2010 which I have just installed, As the result of a catastrophic failure using the programme I had to restore my C drive from a backup on another drive. Since this when I attempt to run the backup section to do a scheduled backup of my emails the box marked username is filled in with details of the machine and I input the password that I use to log onto the machine as the user. As soon as it starts to run the programme comes up with an error stating its the wrong information in these boxes. Is it possible to run it without credentials if not can you alter the username and password as don’t know where it’s picking the username up from and the password is not the same as I use for logging onto the computer as a user. The user name appears to start with the machine name and the a backslash and the username of myself. I can only assume its not picking this information up correctly and I don’t know where to look to confirm what it should be. Any help on this matter would be greatly appreciated as I can only do backups without scheduling at the moment until I manage to fix this problem.
I went onto the section of the Main Web Site for Acronis and it suggested that it may be worth running a configuration file which downloaded and run on my machine. It seems to work now so this file must have corrected the problem.
My particular problem is still unresolved and I'm ready to try almost anything. Would you be kind enough to post the exact location and name of the configuration file that sorted your problem so that I can find, download it and try it?
Many thanks.
If you look at Knowledge Base Record 1518 the file is half way down the item marked in blue 'scheduling' I fould that by downloading this fix and running the files it seemed to clear the problem up and it accepts my password as the computer user. Hope this helps. let me know if it works for you as well.
Thank you. The delay in answering is mainly due to my trying out your suggestion. Using the scheduler fix file seems to have solved the problem, but the results are patchy. I am also in correspondednce with Acronis about this issue - another reason for delay - and I shall post again when anything clear emerges.