Skip to main content

Why is Jenkins Agent Stopping My Backups????

Thread needs solution

ATI did its regularly scheduled backup of my System today (C Drive and EFI). It took forever before it even started the backup!

ATI itself says, "The backup has successfully completed". BUT it sent me the following "Backup task execution failed" email notification. I know the backup isn't correct, because it's about half the size of my usual backup. (And it distresses me that the ATI program says it was successful when it wasn't!!!)

Who is this Jenkins_Agent, and why is he sabotaging my backup???? I did a search for him on my computer, and he doesn't seem to exist.

My regular drive backups are working just fine.

-Peg
_____________________

Subject: Backup task execution failed - Acronis True Image notification from PEGSCOMPUTER
Date: Sun, 13 Mar 2022 01:22:49 -0500

2022-03-13T01:21:27:189-05:00 13624 I00000000: -----
2022-03-13T01:21:27:189-05:00 13624 I00000000: ATI Demon started. Version: 24.8.1.38600.
2022-03-13T01:21:27:868-05:00 13624 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2022-03-13T01:21:27:869-05:00 13624 I00640002: Operation Monthly System Image to V (overwritten) started manually.
2022-03-13T01:21:34:656-05:00 13624 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2022-03-13T01:21:35:661-05:00 13624 I013C0000: Operation: Backup
2022-03-13T01:21:37:381-05:00 13624 I0064000B: Priority changed to Low.
2022-03-13T01:22:26:404-05:00 13624 W01E50023: Error 0x1e50023: The specified file does not exist: V:\Monthly System Image to V (overwritten)_full_b8_s1_v1.tib.
| trace level: warning
| line: 0x4d3f22948e29f18c
| file: c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\archive\impl\utils.cpp:181
| function: `anonymous-namespace'::GenerateGuiErrorWithPath
| line: 0x4d3f22948e29f18c, c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\archive\impl\utils.cpp:181, `anonymous-namespace'::GenerateGuiErrorWithPath
| $module: ti_demon_vs_38600
|
| error 0xb007f: The initial full backup version is not accessible at the moment.
| line: 0x65e40aa0b4871b8
| file: c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\archive\impl\operations\archive_operation_backup.cpp:807
| function: TrueImage::Archive::BackupArchiveOperationImpl::TraceFirstVolumeExistance
| line: 0x65e40aa0b4871b8, c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\archive\impl\operations\archive_operation_backup.cpp:807, TrueImage::Archive::BackupArchiveOperationImpl::TraceFirstVolumeExistance
| $module: ti_demon_vs_38600
|
| error 0x40011: The specified file does not exist.
| line: 0xf35f747b3b21fc69
| file: c:\jenkins_agent\workspace\ati-main-win\1824\core\file\windows\winnt_dir.cpp:1376
| function: winnt_dir::iterator::iterator
| line: 0xf35f747b3b21fc69, c:\jenkins_agent\workspace\ati-main-win\1824\core\file\windows\winnt_dir.cpp:1376, winnt_dir::iterator::iterator
| function: FindFirstFileW
| path: \\?\V:\Monthly System Image to V (overwritten)_full_b8_s1_v1.tib
| $module: ti_demon_vs_38600
|
| error 0xfff0: The system cannot find the file specified
| line: 0xbd28fdbd64edb8f1
| file: c:\jenkins_agent\workspace\ati-main-win\1824\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\jenkins_agent\workspace\ati-main-win\1824\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070002
| $module: ti_demon_vs_38600
2022-03-13T01:22:30:079-05:00 13624 E02160007: Error 0x2160007: No current partition.
| trace level: error
| line: 0x36eed22d32caa1c8
| file: c:\jenkins_agent\workspace\ati-main-win\1824\core\da_api\set_prop.cpp:1238
| function: DaSetProperty
| line: 0x36eed22d32caa1c8, c:\jenkins_agent\workspace\ati-main-win\1824\core\da_api\set_prop.cpp:1238, DaSetProperty
| $module: ti_demon_vs_38600
|
| error 0xb03ec: Cannot find the partition selected for the backup.
| line: 0x839cdd79f76937e2
| file: c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\archive\impl\operations\backup_disk_source_preparer.cpp:361
| function: TrueImage::Archive::DiskBackupSourcePreparer::AppendBackupSource
| line: 0x839cdd79f76937e2, c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\archive\impl\operations\backup_disk_source_preparer.cpp:361, TrueImage::Archive::DiskBackupSourcePreparer::AppendBackupSource
| $module: ti_demon_vs_38600
2022-03-13T01:22:34:468-05:00 13624 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bceda
| file: c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\demon\main.cpp:740
| function: main
| line: 0x9f2c53c72e8bceda, c:\jenkins_agent\workspace\ati-main-win\1824\products\imager\demon\main.cpp:740, main
| $module: ti_demon_vs_38600
Attachment Size
ATI Results.jpg 38.82 KB
ATI Results2.jpg 17.56 KB
0 Users found this helpful

The Jenkins Agent is apparently a component of ATI.

Looking at the information posted, I noticed the following line in the report:

 error 0xb007f: The initial full backup version is not accessible at the moment.

This can be a fatal problem for Disk and Partitions on Whole PC backups which use the *.tibx architecture. If the first *.tibx assoicated with the task is missing, then the backup is essentially useless. This file contains information necessary to make future backups and to do recovery. This files can be very small, about 12kb, if the task has been established for a long time. Please confirm that the first file is present.

You say the backup file is smaller than usual; the can happen when a new backup chain is created (mainly with incremental backups). Are you do an incremental backup?

I think that the best thing to do is to look at the appropriate log files; Steve Smith says the following log files are relevant for ATI 2020:

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 backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.

To view the log files you need to download the MVP Assistant - a new tool, including new Log Viewer (Latest version 1.1.6.0, 12/05/2021) - here the Backup Worker logs will be needed. Please post the appropriate log file as attachment(s).

I will not be able to assist you further, as I am off on holiday and will not have internet access for much of the next two weeks.

Ian