Skip to main content

Problem during planned backup: execution failed

Thread needs solution

This night start at 20,00 my monthly planned backup and receive on my mail this error message

 

2020-08-31T20:01:39:095+02:00 21104 I00000000: -----
2020-08-31T20:01:39:095+02:00 21104 I00000000: ATI Demon started. Version: 24.6.1.25700.
2020-08-31T20:01:39:138+02:00 21104 I00640000: Attributi della copia di riserva del backup: format tib; need_reserve_backup_copy false;
2020-08-31T20:01:39:138+02:00 21104 I00640002: Operazione ADATA SX8200PNP SS0411B avviata con pianificazione.
2020-08-31T20:01:39:186+02:00 21104 I00640000: Attributi della copia di riserva del backup: format tib; need_reserve_backup_copy false;
2020-08-31T20:01:39:186+02:00 21104 I013C0000: Operazione: Backup
2020-08-31T20:01:39:187+02:00 21104 I0064000B: Priorità modificata in Bassa
2020-08-31T20:02:41:429+02:00 21104 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 0x70021: Failed to create volume snapshot.
| line: 0x8ba4fa0bac28c26f
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup_partition.cpp:1308
| funzione: resizer::Archive3ImageBuilder::BackupPartitions
| line: 0x8ba4fa0bac28c26f, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup_partition.cpp:1308, resizer::Archive3ImageBuilder::BackupPartitions
| $module: disk_backup_vs_650
|
| error 0x10c449: Failed to lock the volume snapshot.
| line: 0x3fec04e376b8a236
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:1344
| funzione: win_snapshot_core::CallSbLock
| line: 0x3fec04e376b8a236, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:1344, win_snapshot_core::CallSbLock
| $module: disk_backup_vs_650
|
| error 0x9: Stato sconosciuto.
| 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: 0xe000006d
| $module: disk_backup_vs_650
|
| error 0xfff0
| line: 0xbd28fdbd64edb8f1
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp:307
| funzione: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0xe000006d
| $module: disk_backup_vs_650
2020-08-31T20:02:41:464+02:00 21104 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

and at this moment is in progress validation of backup...?!'

What is this problem ?

 

Thank

Hispa

Attachment Size
Immagine.png 55.39 KB
0 Users found this helpful

Hispa, the log is saying that the backup failed due to a VSS snapshot error.  The validation is running because you have configured it to run after your backup and there are existing backup files for it to validate.

Beyond the above, it is impossible to say why VSS had a problem but you could try running the Acronis VSS Doctor tool to see if it detects any issues?  Otherwise check for any disk errors for your source disk / partitions.

Now i received another mail form app:

2020-08-31T20:03:14:090+02:00 17728 I00000000: -----
2020-08-31T20:03:14:090+02:00 17728 I00000000: ATI Demon started. Version: 24.6.1.25700.
2020-08-31T20:03:14:132+02:00 17728 I00640000: Attributi della copia di riserva del backup: format tib; need_reserve_backup_copy false;
2020-08-31T20:03:14:133+02:00 17728 I00640002: Operazione ADATA SX8200PNP SS0411B avviata con pianificazione.
2020-08-31T20:03:14:165+02:00 17728 I00640000: Attributi della copia di riserva del backup: format tib; need_reserve_backup_copy false;
2020-08-31T20:03:14:166+02:00 17728 I013C0000: Operazione: Backup
2020-08-31T20:03:14:166+02:00 17728 I0064000B: Priorità modificata in Bassa
2020-08-31T20:46:14:924+02:00 17728 I013C0006: Operazione completata.

where tell backup completed and if open AI i have this situation and with backup valid !?

And result of VSS report

 

Hispa

 

Attachment Size
550513-196311.png 59.74 KB
550513-196313.txt 21.5 KB

Hispa, the second log is probably because of the successful validation operation.  I would recommend changing the validation option for the task to just do a backup only, not to do the validation immediately afterwards.

The VSS log points you to review the Google hits for the error code reported in the event log in Windows.

https://www.google.com/#newwindow=1&q=VSS+event+id+12293

Steve Smith wrote:

Hispa, the second log is probably because of the successful validation operation.  I would recommend changing the validation option for the task to just do a backup only, not to do the validation immediately afterwards.

The VSS log points you to review the Google hits for the error code reported in the event log in Windows.

https://www.google.com/#newwindow=1&q=VSS+event+id+12293

Ok if understand well my backup is safe...

After following your suggestions i planned only the backup and not backup and validation

Planned validation 1 day after backup...

Correct this ??

 

Hispa

 

Hispa, the validation was probably for an older backup given that the most recent one failed with the VSS snapshot errors shown in your log.

If you don't want to include validation with your backup then click on Options > Advanced then disable Validation in the settings there.

Thank Steve...
I resolved following Repair Install of Windows 10 with an In-place Upgrade

https://www.tenforums.com/tutorials/16397-repair-install-windows-10-pla…

Hispanico