Skip to main content

Backup File names changed / Win10 --> Win11(?)

Thread solved

Morning All.  I recently moved my PC from Win10 to Win11 ... very similar set up, same hardware, dual boot, etc.

My nightly Acronis backup jobs are generating different file names.

Here is an example from Win10 ... '2022 Backup to OneDrive_full_b3_s1_v1.tib'
Here is an example from Win11 ... '@task@_full_b1_s1_v1.tib'

My guess is that @task@ is some form of placeholder that should be replaced by the name of the task (the name of the backup task was '2022 Backup to OneDrive') but it isn't.  Have I swapped some toggle somewhere, missed a key radio button, other?

0 Users found this helpful

Your guess is correct that @task@ should be getting replaced by the actual task name and this shouldn't have changed just by moving from Win 10 to 11.

Couple of checks:

Are you still running Acronis as Administrator - that is required for all versions to operate correctly with all required authority / permissions?

Did Acronis get reinstalled in your migration from Win 10 to 11?

You could try doing a Repair Install (as Administrator) to see if that corrects the names.

See KB 60915: Acronis Cyber Protect Home Office, Acronis True Image: repairing program settings - for more information.

Note: I do not recollect seeing any similar issues reported by other users or for my own systems.

Here is an example from Win10 ... '2022 Backup to OneDrive_full_b3_s1_v1.tib'
Here is an example from Win11 ... '@task@_full_b1_s1_v1.tib'

I have seen the same issue on two separeate installs. I see it on a file/folder backup with a lot of source files, small and large ones. When i saw it first i deleted the backup and re-created it only to discover the very same issue the second time i did a fresh install of Windows 11 and #40729 of ACPHO.

I had Games_full_b1_s1_v1.tib and expected Games_full_b2_s1_v1.tib the second time but got @task@_full_b2_s1_v1.tib instead.

Other file/folder backups did not fail, only this backup with lot´s of small and large files:

  • 289 957 files
  • 11 878 folders
  • Size on disk: 118 669 209 600 bytes
  • Backup file size: 58 258 550 784 bytes

The issue can be 100% reproduced.

Before i did the clean install of Win 11/Acronis i exported all settings from ACPHO using the Settings > Backup settings transfer and on the new install i imported those settings. Since the backup works and fails during this stage i guess that the exported settings has some kind of flaw.
 

Side note: On all backups ACPHO lost track of which files to cleanup, as usual...

Thanks for the replies.  I reinstalled Acronis into Win11.  I did import the settings from the Win10 backup tasks so I might have been bitten by Roger A's observation.  I just ran a super small backup and the file came through correctly (TestNaming_full_b1_s1_v1.tib).

I am going to re-create one of my nightly backups are force new backup.

Edit: recreated task running now.  File naming is correct.  Will make as solved based on results from scheduled backup overnight (1am).

Edit2: Interesting to note that the @taskname@ used in the email header was converted.  Just the actual file names were borked.  I have emails that show the conversion and the borked task names :).

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Ruff_Hi wrote:

Thanks for the replies.  I reinstalled Acronis into Win11.  I did import the settings from the Win10 backup tasks so I might have been bitten by Roger A's observation.  I just ran a super small backup and the file came through correctly (TestNaming_full_b1_s1_v1.tib).

I am going to re-create one of my nightly backups are force new backup.

Edit: recreated task running now.  File naming is correct.  Will make as solved based on results from scheduled backup overnight (1am).

Edit2: Interesting to note that the @taskname@ used in the email header was converted.  Just the actual file names were borked.  I have emails that show the conversion and the borked task names :).

Hello!

I have raised a ticket with our support so the issue can be investigated 06200126.

Our support will send you an email so we can get more information.

Best regards.

Both scheduled tasks ran last night with no task naming issue.

 

I am going to mark this solved with the answer being: Don't import old settings, recreate the backup task.