Skip to main content

Acronis True Image 2020 backup fails

Thread needs solution

Hello everyone.

Attention. This is a somewhat long post and automatically translated via online translator.

I have a problem with Acronis True Image 2020

Here's my setup:

Windows 10 version 2004 build SO 19041.423
Acronis True Image 2020 build 25700

Hard disk nr.1 containing the files for backup:

Seagate ST3000DM001-1CH166

Hard disk nr.2 contain files for backup:

Toshiba MQ01abd050

The data contained in these hard drives is encrypted with Bitlocker and is processed with a unique backup process that allows me to have a backup on NAS in turn encrypted with Acronis.

The NAS is a Synology DS115j with DSM firmware updated to the latest release 6.2.3-25426 Update 2

Before opening Acronis True Image 2020 (using the administrator user) I must manually unlock the two above drives (Hard disk 1 and 2)

The backup process often ends with this error:

2020-08-06T16:05:58:881+02:00 11116 I00000000: -----
2020-08-06T16:05:58:881+02:00 11116 I00000000: ATI Demon started. Version: 24.6.1.25700.
2020-08-06T16:05:58:910+02:00 11116 I00640000: Attributi della copia di riserva del backup: format tib; need_reserve_backup_copy false;
2020-08-06T16:05:58:911+02:00 11116 I00640002: Operazione Dati avviata manualmente.
2020-08-06T16:06:00:122+02:00 11116 I00640000: Attributi della copia di riserva del backup: format tib; need_reserve_backup_copy false;
2020-08-06T16:06:00:123+02:00 11116 I013C0000: Operazione: Backup
2020-08-06T16:06:00:124+02:00 11116 I0064000B: Priorità modificata in Bassa
2020-08-06T21:21:00:807+02:00 11116 E02160015: Error 0x2160015: Errore di backup.
| livello traccia: errore
| line: 0xa340ffd3416335cf
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353
| funzione: da_backup::Commit
| line: 0xa340ffd3416335cf, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353, da_backup::Commit
| $module: disk_backup_vs_650
|
| error 0x70030: Il backup è stato creato ma i suoi dati non corrispondono a quelli dell'origine. Il backup verrà riavviato automaticamente.
| line: 0x1c981e20c1c9f1bb
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup.cpp:533
| funzione: resizer::Archive3ImageBuilder::CommitBackup
| line: 0x1c981e20c1c9f1bb, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup.cpp:533, resizer::Archive3ImageBuilder::CommitBackup
| $module: disk_backup_vs_650
|
| error 0x10c44a: Failed to obtain the snapshot state.
| line: 0x3fec04e376b8a2b6
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:1472
| funzione: win_snapshot_core::GetNextSector
| line: 0x3fec04e376b8a2b6, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:1472, win_snapshot_core::GetNextSector
| $module: disk_backup_vs_650
|
| error 0x9: Già arrestato.
| line: 0x2aacb7b2ab852ac
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| funzione: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0xe0000004
| $module: disk_backup_vs_650
2020-08-06T21:21:10:724+02:00 11116 E013C0005: Error 0x13c0005: Operazione completata senza errori.
| livello traccia: errore
| line: 0x9f2c53c72e8bced8
| file: c:\bs_hudson\workspace\123\products\imager\demon\main.cpp:738
| funzione: main
| line: 0x9f2c53c72e8bced8, c:\bs_hudson\workspace\123\products\imager\demon\main.cpp:738, main
| $module: ti_demon_vs_25700

What puzzles me is this string:

error 0x70030: The backup was created but its data does not match the data of the source. The backup will restart automatically.

I opened a command prompt with CMD run as administrator to give the command chkdsk /f on both drives encrypted with bitlocker but unlocked.

This is the result:

C:-WINDOWS-system32>chkdsk /f e:
The file system is of type NTFS.
The volume label is data.

Step 1: Analyze the basic file system structure in progress...
  759808 file records processed.
File verification completed successfully.
Phase Duration (Check File Records): 8.22 seconds.
  1785 large file records processed.
Phase Duration (Recover orphaned file records): 0.00 milliseconds.
  0 invalid file records processed.
Phase Duration (Invalid File Record Check): 0.24 milliseconds.

Step 2: Analyze the file name link...
Unspecified error (696e647863686b2e 532).
Unspecified error (6e74667363686b2e 1798).

To try to understand the problem I first disabled the bitlocker on one of the two disks and then ran chkdsk /f /r j: from a session started in safe mode.

I didn't get any error messages. I can only say that I think it is very unlikely that this is a bitlocker problem as I am now still receiving it after starting Windows 10 in normal mode and with the drive unencrypted. I have indeed temporarily disabled bitlocker for this drive.

I didn't try to remove the encryption from the other disk as it would take many hours. I think that as in safe mode chkdsk /f /r j: did not report errors would happen the same thing for the currently still encrypted disk.

Another error message I noticed is
Failed to obtain the snapshot state.

Can you help me?

 

0 Users found this helpful

Lorenzo, welcome to these public User Forums.

Please can you confirm that you are creating a Disks & Partitions backup with this task (as suggested by some of the log messages)?

Have you changed any of the Advanced Options for this task, in particular, the Performance options related to the use of VSS for snapshot creation?

I would recommend downloading the Acronis VSS Doctor tool (link in my signature) and running this to check for any snapshot issues on this computer.  Let the tool fix any issues it finds if it offers this option.

Next, please try separating this backup into 2 unique backup tasks, 1 for each disk drive in your current task source, so that you can better identify if any errors come from a particular disk?

Was this backup task created by ATI 2020 and thus using .tibx files for the backup, or was it a task created by an earlier version of ATI that still uses .tib files?

What other options are configured for the task?  Are you running validation after the backup?

Has this backup been running successfully prior to this problem or is this the first time it is being used?

Similar problem here. Same error, this started since I cloned my SSD to an M.2 disk. The backup throws this error but after 2-3 times finishes correctly. Also as soon as the backup starts the system becomes partially unresponsive (mouse moves but clicking around does not work). The destination disk is a 2TB caviar red, much slower than the soruce disks (a sabrent rocket 240gb m.2 + a kingston 480GB SSD).

Today I changed the schedule from a fixed time (18.00) to backup on shutdown, hoping that maybe NOT accessing the disk solves the problem.

I'm thinking that the huge difference in I/O speed is the source of the problem.

Lastly the VSS diagnostic tool is all green, sometimes I get a yellow warning on the tool regarding I/O speed on the destination HDD, rarely I get the same warning on the SSD, NEVER on the M.2.