Backup Task execution failed - Error 0x40019
Hi there,
I get every Backup an Email with the error code above. The whole text looks like this:
2020-04-21T20:32:22:365+02:00 17764 I00000000: -----
2020-04-21T20:32:22:365+02:00 17764 I00000000: ATI Demon started. Version: 24.6.1.25700.
2020-04-21T20:32:22:393+02:00 17764 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
2020-04-21T20:32:22:394+02:00 17764 I00640002: Aktion Backup wurde per Planung gestartet.
2020-04-21T20:32:22:451+02:00 17764 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
2020-04-21T20:32:22:452+02:00 17764 I013C0000: Aktion: Backup
2020-04-21T20:32:22:453+02:00 17764 I0064000B: Priorität geändert in 'Niedrig'
2020-04-21T20:32:22:582+02:00 17764 E00040019: Error 0x40019: Fehler beim Backup.
| Ablaufverfolgungsebene: Fehler
| line: 0xaa33a143c434a5f5
| Datei: c:\bs_hudson\workspace\123\home\backup_worker\impl\backup_worker.cpp:167
| Funktion: `anonymous-namespace'::ReturnCodeToError
| line: 0xaa33a143c434a5f5, c:\bs_hudson\workspace\123\home\backup_worker\impl\backup_worker.cpp:167, `anonymous-namespace'::ReturnCodeToError
| Archive3Code: 0x138d
| Name:
| $module: archive3_adapter_vs_25700
2020-04-21T20:32:22:633+02:00 17764 E013C0005: Error 0x13c0005: Aktion mit Fehlern beendet.
| Ablaufverfolgungsebene: Fehler
| line: 0x9f2c53c72e8bced8
| Datei: c:\bs_hudson\workspace\123\products\imager\demon\main.cpp:738
| Funktion: main
| line: 0x9f2c53c72e8bced8, c:\bs_hudson\workspace\123\products\imager\demon\main.cpp:738, main
| $module: ti_demon_vs_25700
I found a similar error problem in this forum, but this was a cloud backup. My backup is saved to a RDX drive.
Please help me understanding this error.
Regards
Karel


- Anmelden, um Kommentare verfassen zu können

Karel,
Is this a new problem? Has the backup ever worked before or is this the result when you use RDX as your target drive? Do you have another disk that you can use as a target for the backup?
- Anmelden, um Kommentare verfassen zu können

Hi,
thanks for your comments.
@Steve The Log Files are attached. I hope this are the right ones :-)
@Enchantech The backup worked well for a long time. The mail message comes up one or two month ago. First only 1 by week, now every backup.
Cheers
Karel
Anhang | Größe |
---|---|
535953-182234.zip | 148.35 KB |
- Anmelden, um Kommentare verfassen zu können

Karel, thanks for the backup_worker logs. These show that your backup task was working OK until April 9th but starting failing from April 14th onwards.
The error is as shown below for all attempts from this time forward:
14/04/2020 08:30:00:791 PM +02:00 14380 I00000000: type=log; level=inf; message=ar#1: opening archive path="\\?\X:\/Backup.tibx" in append mode (create);
14/04/2020 08:30:00:793 PM +02:00 14380 I00000000: type=log; level=wrn; message=pcs_errno_to_err: Failed to convert errno 21 to pcs error. Return PCS_ERR_UNKNOWN value.;
14/04/2020 08:30:00:793 PM +02:00 14380 I00000000: type=log; level=inf; message=pcs_dirent_first(\\?\X:\) failed: 21 (pcs_err=4095);
14/04/2020 08:30:00:793 PM +02:00 14380 I00000000: type=log; level=err; message=ar#1: failed to find archive files: -5005 Input/output error;
14/04/2020 08:30:00:793 PM +02:00 14380 I00000000: type=log; level=err; message=ar#1: failed to open archive path="\\?\X:\/Backup.tibx" mode=append uuid=00000000000000000000000000000000, err=-5005 (Input/output error);
14/04/2020 08:30:00:793 PM +02:00 14380 I00000000: type=log; level=err; message=unable to open archive file (err -5005);
14/04/2020 08:30:00:793 PM +02:00 14380 I00000000: type=retcode; value=5005; id=1;
14/04/2020 08:30:00:793 PM +02:00 7956 I00000000: >>> exit
14/04/2020 08:30:00:801 PM +02:00 7956 I00000000: >>> exit
Put simply, ATI cannot find your X: backup destination for the task.
Please check that your RDX drive is still showing as being assigned drive letter X: ?
- Anmelden, um Kommentare verfassen zu können

HI Steve,
thanks for your help. I checked the RDX drive. The rdx cassette was not 100% engaged. Only 99% :-)
I removed the cassette and reload it and now it is ok.
If the error will come again, I will com back.
Thx
Karel
- Anmelden, um Kommentare verfassen zu können

Karel, glad that the issue is sorted, hope it stays that way for you!
- Anmelden, um Kommentare verfassen zu können