Error 0x2160015: A backup error.
Don't know what happened, but I just got this, and it restarted the backup. PC is super slow now, and the 'progress' is as well too.
A screen shot, and it shows LARGER than the drive file is now, and has NOT changed the time, even as the backup size increases?
My backup file size now:
08/06/2021 02:16 PM 260,796,551,168 My disks-0087.tibx (could one be bytes and the other MB's, possibly, but I've been checking the size on disk and it doesn't always increase when the ATI screen doesn?)
Log data emailed to me on the fail:
======================
2021-08-06T10:10:00:695-04:00 3748 I00000000: ----- 2021-08-06T10:10:00:695-04:00 3748 I00000000: ATI Demon started. Version: 24.7.1.38530. 2021-08-06T10:10:00:843-04:00 3748 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 2021-08-06T10:10:00:844-04:00 3748 I00640002: Operation My disks started by schedule. 2021-08-06T10:10:01:249-04:00 3748 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 2021-08-06T10:10:01:249-04:00 3748 I013C0000: Operation: Backup 2021-08-06T10:10:01:250-04:00 3748 I0064000B: Priority changed to High. 2021-08-06T13:03:54:205-04:00 3748 E02160015: Error 0x2160015: A backup error. | trace level: error | line: 0xa340ffd3416335cf | file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353 | function: 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: The backup has been created but its data is inconsistent with the source. Backup will be automatically restarted. | line: 0x1c981e20c1c9f1bb | file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup.cpp:533 | function: 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 0x10c482: A fatal error occurred while reading the snapshot. The snapshot was canceled by the system. See system logs for details. | line: 0x3fec04e376b89f08 | file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:530 | function: win_snapshot_volume::IoOp | line: 0x3fec04e376b89f08, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:530, win_snapshot_volume::IoOp | $module: disk_backup_vs_650 | | error 0x9: Unknown status. | line: 0x2aacb7b2ab852ac | file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\ver2\arch\windows\win_errors.cpp:40 | function: 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: 0x1b1 | $module: disk_backup_vs_650 | | error 0xfff0: A device which does not exist was specified | line: 0xbd28fdbd64edb8f1 | file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x800701b1 | $module: disk_backup_vs_650 2021-08-06T13:03:54:767-04:00 3748 E013C0005: Error 0x13c0005: Operation has completed with errors. | trace level: error | line: 0x9f2c53c72e8bceda | file: c:\jenkins_agent\workspace\ati-main-win\1440\products\imager\demon\main.cpp:740 | function: main | line: 0x9f2c53c72e8bceda, c:\jenkins_agent\workspace\ati-main-win\1440\products\imager\demon\main.cpp:740, main | $module: ti_demon_vs_38530 =======================
Saw another older one with the same fail and VSSDoctor should be run. So I did, no real errors I can see: Did report some problems though, but I don't think these matter?
==========
Disk Free Space Available
Status: Warn
Description: Some disks have insufficient free space. Perform a cleanup.
===========
Those that it did find are not assigned drive letters....
===
Name: \\?\Volume{c8173012-2912-4f45-b969-cea6b488a0dc}\
DeviceId: \\?\Volume{c8173012-2912-4f45-b969-cea6b488a0dc}\
Size: 528 MB
Available: 83 MB
Minimum: 320 MB
IsOk: False
Description: Free space is below required minimum
IsMounted: False
===========
That is my RECOVER volume by the way.
Also
Disk I/O Load
Status: Warn
Description: Some disks may be overloaded. VSS may behave incorrectly under such conditions. Stop heavy operations or wait until completion.
===============
Name: 3 P:
DiskBytesPersec: 6419617
DiskReadBytesPersec: 6419617
DiskReadsPersec: 269
DiskTransfersPersec: 269
DiskWriteBytesPersec: 0
DiskWritesPersec: 0
PercentDiskReadTime: 3301
PercentDiskTime: 3301
PercentDiskWriteTime: 0
PercentIdleTime: 0
IsOk: False
================
P" IS the backup drive, and VSSDOCTOR was run when ATI was trying again.
Something is CLEARLY wrong now too...
As I've been composing this message, ATI continues to run.
The File size NOW,
08/06/2021 02:30 PM 260,849,856,512 My disks-0087.tibx
What it was before:
08/06/2021 02:16 PM 260,796,551,168 My disks-0087.tibx
Hardly changed?
What ATI reports:
Very confusing to me?
Suggestions?

- Accedi per poter commentare

Well, it DID finish and complete:
Look OK in the Recovery Screen. Suspect it took over where the first try failed.
As you can see, the back up files are about the same in size:
P:\Acronis_Backup\All Drives>dir
Volume in drive P is P_Drive
Volume Serial Number is 6C93-8314
Directory of P:\Acronis_Backup\All Drives
08/06/2021 03:25 PM <DIR> .
08/06/2021 03:25 PM <DIR> ..
07/09/2021 01:06 PM 265,989,201,920 My disks-0083.tibx
07/16/2021 01:28 PM 262,680,997,888 My disks-0084.tibx
07/23/2021 02:19 PM 255,409,221,632 My disks-0085.tibx
07/30/2021 01:18 PM 253,941,772,288 My disks-0086.tibx
08/06/2021 03:25 PM 262,953,902,080 My disks-0087.tibx
01/03/2020 11:26 AM 12,288 My disks.tibx
6 File(s) 1,300,975,108,096 bytes
2 Dir(s) 1,634,223,902,720 bytes free
Weird, but I think the write speed is very low?
Disk appears OK via CHKDSK:
Windows has scanned the file system and found no problems.
No further action is required.
3815444 MB total disk space.
2256657 MB in 29641 files.
7460 KB in 833 indexes.
0 KB in bad sectors.
237159 KB in use by the system.
65536 KB occupied by the log file.
1595954144 KB available on disk.
4096 bytes in each allocation unit.
976753919 total allocation units on disk.
398988536 allocation units available on disk.
Total duration: 8.19 seconds (8198 ms).
- Accedi per poter commentare

Well, looks like VSSDOCTOR which I reran sort of indicates why ATI failed:
Don't know WHY those 2 drives (that were being backed up) dropped off? PC is on a UPS???
C: usually 25GB's free? Not sure why not now? Can't see anything that I can delete/move...
- Accedi per poter commentare