Add macro @date@ replaces file name, not appends it
Add macro @date@ replaces file name, not appends it. So the new file and Backup name is NOTEBOOK@date@-@time@. This happens 50% of the time. This is the same error we had with 2011 or 2010. /Howard
- Log in to post comments
Where are you setting the name? Can your give a step by step example? Are you changing the name of the task, or the backup filename during creation or editing of the task?
- Log in to post comments
After I had the problem from a new setup script, I changed the "Backup Name" and then browsed to the Destination to see that the fail name had changed there as well. So I saved the Destination screen and then the saved the Backup Configuration Screen. Then I made a shortcut to the Desktop and ran two more backups, both with the same problem.
- Log in to post comments
Howard,
As I am unable to duplicate the problem you are having, is there any way you can post some screen captures of the steps you are taking, as well as a screen capture of the resulting files list?
- Log in to post comments
- Log in to post comments
- deleted - please see Grover's post below. Additional testing on my part revealed no problems with Grover's approach. Thanks Grover for the clear and precise instructions.
- Log in to post comments
Howard,
My experience with file names is as per this link. Look at figures 6-7-8. Note the comments surrounding all 3 illustrations. Also note the comments at the bottom of figure 18.
http://forum.acronis.com/forum/28705
I have found that the file name can only be correctly set when the backup filename is assigned from inside the destination folder. This name must not be edited and must be correct when task is created. It can be either of the below and I always use the dash or underscore before and after each of the coding.
Notebook-@date@-@time@-.tib
Notebook_@date@_@time@_.tib
The name at the bottom of the main GUI (fig 18) is the task name and not the name of the backup file. You can change the task name without changing the backup file name. The two names are totally separate and serve separate functions and must be assigned separately. The name assigned to the backup file should not be edited and only assignable via the browse for destination as shown in figure 7 & 8.
While you may disagree with my approach, I found that it works and I have no issues with the name assigned to the backup file.
- Log in to post comments