Acronis True Image 2021 v34340 - FAILS CONSTANTLY. CANNOT DO BACKUPS!!! DOES NOT WORK !!!
Hello -
Has anyone else had the same issues with ATI 2021 v34340? I'm running win 10 x64, with 32GB memory, and several TB of free space. All are SSD's. I have installed / uninstalled ATI 2021 countless times, evening using the recommended ATI Cleanup Utility. Nothing works. The backup will start, run for 5 minutes doing nothing, and then lockup. I get constant email notification of Backup Failure. I am writing to NAS Device, (Synology D218), and never had any issues with other products writing to that device. Only ATI 2021 v34340 seems to have massive issues and problems. I've contacted support multiple times, with no success. I'm ready to demand a FULL REFUND and go with a company that supports their customers, and not just take their money!!!!! See attached error log, for the error that constantly gets produced. They should never have releases such a BAD product !!!
Anhang | Größe |
---|---|
ErrorLog-122120-Forum.txt | 2.29 KB |


- Anmelden, um Kommentare verfassen zu können

In general terms the "cannot lock the file" message indicates that the file is in use by another process or user. I have one suggestion and it is going to sound completely ridiculous so I understand if you would rather not try it.
Right click on the Windows start flag and hover over Shutdown or sign out then move your mouse to select Sign out and click it. This will sign your user instance. At the logon screen click on the icon in the lower right corner of the screen, then click on the Power icon then Restart.
After the restart log in and try your backup again.
- Anmelden, um Kommentare verfassen zu können

The demon log seems to show the failure happening immediately so it is possible that the 5 minutes is just the time to do all the error attempts.
Some things in your initial post are unclear.
1. Is this your first install of True Image or are you updating from an earlier version.
2. If an update, are you trying to continue with a backup task already in existence?
3. Was True Image installed as an administrator (Run as Administrator... not just from an admin account)?
4. When you configured the backup task, was ATI able to properly access the NAS?
5. Are there any credentials required for the NAS?
6. The demon log shows an error in backup_worker so have you checked the backup worker logs to see if there is additional information?
7. Have you seen if there is a backup file even started on the NAS?
Can you be more specific about the type of backup you are running?
- Anmelden, um Kommentare verfassen zu können

Steve, in addition to the previous questions, couple of further points to offer here!
First, you mention 'All are SSD's' in your initial post. How many SSD's are you including in your backup task here? Is this a Disks & Partitions or 'Entire PC' backup task?
Please try selecting only a single SSD for the backup by clicking through on the Source panel to see the further options below this, i.e. Disks & Partitions, then select only one SSD disk.
Does this show the same issue with failing immediately?
If you have an external USB backup drive, does a backup of the same SSD fail to that drive? This will help eliminate this being an issue related to your Synology NAS destination.
Assuming that you are doing a Disk backup, then the Demon log holds minimal information as the main processing for this type of backup is shown in the Backup Worker logs instead.
There is a new MVP Assistant log viewer tool that has now been made available by Acronis via the Community Tools page..
If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backup using same) then look in the Demon logs.
I am using ATI 2021 #34340 to make regular backups to my own Synology NAS with no issues such as this, so it is doubtful that the error relates to using a NAS destination.
ATI 2021 must be installed using an Administrator account and run from the same to have all the correct authorities / privileges it needs to access the data being backed up.
Note for Ian, the reference to .tib in the log is for the Backup reserve copy, not the disk backup.
- Anmelden, um Kommentare verfassen zu können