Direkt zum Inhalt

Date no longer appended to backup filename

Thread needs solution

After upgrading to 2013 version, the date is no longer appended to my backup filenames. I remember using an @date@ macro in my original setup, but cannot find reference to how that macro is included. There is a vague reference in the help files that this macro can be still used, but no clue how to apply it. Anyone have any suggestions?

0 Users found this helpful

This is an extract from my guide found in link #2 inside signature whcich can help with the task opitons.

Figure 8: Assign folder name and assign custom backup file name

Task Name (Figure 18 ) also is relevant to Figure 8. The names of the backup files can only be changed as in Figure 8; whereas the task name can differ from the backup file name.
In 2013, all backup files will have a program added suffix to the *.tib name such as
   user assigned name_FULL_B1_S1_V1.tib
   user assigned name_INC_B1_S2_V1.tib as per this link example
    http://forum.acronis.com/sites/default/files/mvp/user285/guides/test201…
Understand that the backup file name is not task name and the task name is not the backup file name. The task name and the backup file name are two separate entities. They both may or may NOT carry the same name but that is a user controlled option.

My ATI 2013 with build 6514 does not show the date either and further places the backup in a new folder:
\My Backups\PC1\PC1_FULL_B1_S1_V1.tib
Why is the new folder PC1 showing up? Do I understand correctly that the @date@ is no long useable.
Thanks for the excellent graphics.
This is on a new PC with Windows 8 Pro. the ATI 2013 was upgraded to build 6514 several days ago.
Thanks. /Howard

6514 test task backup file name was set to
F:\My backups\ST3320620AS-@date@-Test-@exec@_
which produced
F:\My backups\ST3320620AS-2013-04-14-Test-1__full_b1_s1_v1.tib

Don't know about the PC1 folder name. If you have other backups in the "My backups" folder, perhaps it did not want to mix.
Is the target a network disk, etc

I reall do not have a good explanation here. Try the task name & date again on a new task.

Hmm. @date@ and @time@ still work in build 6514 bootable Rescue Media. So, I would think they are intended to still work in the Windows application. Perhaps a new bug that should be reported.