Skip to main content

Build 34340 - TIBX backups still fail with VSS problems.

Thread solved

Windows 10 Pro 64 bit, TI 2021 Build 34340

With the November update, I'd hope to be able to start creating TIBX backups, but the attempt still fails as I reported earlier with multiple sessions with tech support.

Still receiving 3 Application error events in the Windows log, Source VSS, Event ID 12293, as before. The AcronisVSSDoctor-net45 still doesn't find anything wrong with the VSS components.

Looks like it's time to drop this one on tech support again.

Here are the most obvious log entries. Maybe the forum regulars can offer a hint or two.

The error message in the actual backup is simply "Unknown status" but the MVPAssistant logs show a bit more.

The "Demon" log entry:

11/27/2020 09:27:21:462 AM -06:00 11160 E02160015: Error 0x2160015: A backup error.
| trace level: error
| line: 0xa340ffd3416335cf
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\da_api\backup.cpp:353
| function: da_backup::Commit
| line: 0xa340ffd3416335cf, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\da_api\backup.cpp:353, da_backup::Commit
| $module: disk_backup_vs_704
|
| error 0x70021: Failed to create volume snapshot.
| line: 0x8ba4fa0bac28c272
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\resizer\archive3\backup_partition.cpp:1311
| function: resizer::Archive3ImageBuilder::BackupPartitions
| line: 0x8ba4fa0bac28c272, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\resizer\archive3\backup_partition.cpp:1311, resizer::Archive3ImageBuilder::BackupPartitions
| $module: disk_backup_vs_704
|
| error 0x10c449: Failed to lock the volume snapshot.
| line: 0x3fec04e376b8a236
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\win_snapshot.cpp:1344
| function: win_snapshot_core::CallSbLock
| line: 0x3fec04e376b8a236, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\win_snapshot.cpp:1344, win_snapshot_core::CallSbLock
| $module: disk_backup_vs_704
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0xe000006d
| $module: disk_backup_vs_704
|
| error 0xfff0
| line: 0xbd28fdbd64edb8f1
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0xe000006d
| $module: disk_backup_vs_704

11/27/2020 09:27:21:633 AM -06:00 11160 E013C0005: Error 0x13c0005: Operation has completed with errors.

The "Backup Worker" log:

11/27/2020 09:27:21:455 AM -06:00 10944 I00000000: Pid: 9860 type=commonerror; value=?5cA??@?A backup error.$moduleAdisk_backup_vs_704$fileAe:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\da_api\backup.cpp$funcAda_backup::Commit$lineNa!r?(????Failed to create volume snapshot.$moduleAdisk_backup_vs_704$fileAe:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\resizer\archive3\backup_partition.cpp$funcAresizer::Archive3ImageBuilder::BackupPartitions$lineNI?6??v???Failed to lock the volume snapshot.$moduleAdisk_backup_vs_704$fileAe:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\win_snapshot.cpp$funcAwin_snapshot_core::CallSbLock$lineN@ ?R?*{??Unknown status.codeNm?$moduleAdisk_backup_vs_704$fileAe:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\ver2\arch\windows\win_errors.cpp$funcAFdisk::AddKstatusError$lineN(?????d??(?codeNm?$moduleAdisk_backup_vs_704$fileAe:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\common\error.cpp$funcACommon::Error::AddWindowsError$lineN3A; id=1;

 

0 Users found this helpful

Bert, the only entries in the logs that stand out for me are those referencing 'resizer'..!

function: resizer::Archive3ImageBuilder::BackupPartitions

Have you tried setting the Options > Advanced > Performance - Compression to 'None' to see if this makes any difference to this issue?  This can only be set on new backup tasks, not for an existing one.

Never eve noticed that part of the error messages. Up 'til now, I've been looking only at the VSS-related messages or parts of the messages.

Since I don't have TIBX backup configuration that I can actually use, setting up a fresh one to try turning off compression won't be a problem.

I'll fire up a backup with compression turned off and see what happens.

It still fails with the same error, and still passes through the "resizer" code even though I've set "Compression level" to "None." Also still see the same VSS error in the "Application" event log at the same time that the error appears in the "Demon" MVPAssistant log.

This takes me back to what I ran across in my first reporting of this problem, in KB63024. I was prepared to make the change outlined in that file, but decided to wait until this most recent fix was released in hope that it would fix my problem too.

Since it hasn't, I think I'll give KB63024 a spin, sometime this week when I have more time to do the recommended backup in case of catastrophic failure.

2020-11-29T09:21:09:086-06:00 11576 I00000000: -----
2020-11-29T09:21:09:086-06:00 11576 I00000000: ATI Demon started. Version: 25.6.1.34340.
2020-11-29T09:21:09:129-06:00 11576 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-11-29T09:21:09:130-06:00 11576 I00640002: Operation DELLBOX-IV-TIBX started manually.
2020-11-29T09:21:09:178-06:00 11576 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-11-29T09:21:09:179-06:00 11576 I013C0000: Operation: Backup
2020-11-29T09:22:14:007-06:00 11576 E02160015: Error 0x2160015: A backup error.
| trace level: error
| line: 0xa340ffd3416335cf
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\da_api\backup.cpp:353
| function: da_backup::Commit
| line: 0xa340ffd3416335cf, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\da_api\backup.cpp:353, da_backup::Commit
| $module: disk_backup_vs_704
|
| error 0x70021: Failed to create volume snapshot.
| line: 0x8ba4fa0bac28c272
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\resizer\archive3\backup_partition.cpp:1311
| function: resizer::Archive3ImageBuilder::BackupPartitions
| line: 0x8ba4fa0bac28c272, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\resizer\archive3\backup_partition.cpp:1311, resizer::Archive3ImageBuilder::BackupPartitions
| $module: disk_backup_vs_704
|
| error 0x10c449: Failed to lock the volume snapshot.
| line: 0x3fec04e376b8a236
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\win_snapshot.cpp:1344
| function: win_snapshot_core::CallSbLock
| line: 0x3fec04e376b8a236, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\win_snapshot.cpp:1344, win_snapshot_core::CallSbLock
| $module: disk_backup_vs_704
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0xe000006d
| $module: disk_backup_vs_704
|
| error 0xfff0
| line: 0xbd28fdbd64edb8f1
| file: e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, e:\jenkins_agent\workspace\ati-disk_backup\704\product\main\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0xe000006d
| $module: disk_backup_vs_704
2020-11-29T09:22:14:180-06:00 11576 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcedb
| file: c:\jenkins_agent\workspace\ati-main-win\1022\products\imager\demon\main.cpp:741
| function: main
| line: 0x9f2c53c72e8bcedb, c:\jenkins_agent\workspace\ati-main-win\1022\products\imager\demon\main.cpp:741, main
| $module: ti_demon_vs_34340

 

Bert, if this backup is of a single disk and multiple partitions, can you try to reduce it to a single partition in an attempt to determine which partition may be problematic.

Regards to Ernie.

BrunoC,

An interesting but tedious operation.

The C-drive has 5 partitions, one OS and4 recovery and other partitions. I created a backup config for each partition and went to work.

All 5 worked without error and they all validated correctly.

I then re-created the backup config I usually use, including all 5 partitions, started the backup and it failed immediately, with the same set of errors I reported earlier.

Strange.

Fortunately, the traditional TIB backups still work.

I was expecting a failure on one of the partitions. I'm wondering if just removing one partition from the backup will help. Start with the smallest.

In the backup task Advanced options under Performance, what happens if you change Snapshot for backup from VSS to Acronis snapshot?

 

BrunoC,

Another interesting but tedious experiment.

The primary drive has 5 partitions, 4 "utility" partitions (recovery and the like), and the OS partition. There's also a second drive with 2 partitions, the D-drive and E-drive.

With just the primary drive, I found that the OS partition plus 1 or more of the utility partitions always failed. But I was able to create a backup with just all 4 utility partitions or just the OS partition.

I had similar results with the second drive. Trying a backup with either or both of the D and E partitions with the OS partition would fail, although I can back up just the D and E partitions together or individually.

So the OS partition on its own can be backed up, but combining it with even one other partition from either drive causes the backup to fail.

I'll try some experiments with the other snapshot options available in the settings. I did a quick look but couldn't find any description of what they're for.

Fortunately, the TIB backups are still working. And, I can always fall back to TI 2019 if things fall completely apart.

 

Finally fixed it.

I simply followed the suggestion in KB 63024 and added "volsnap" to the UpperFilters in the registry key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}

I was going to try that a long time ago, but I was warned against it. Since nothing else worked, I saw no real harm in trying it.

This has the added advantage that I can now create (and presumably use) system restore points.

[If anyone is curious, I installed this fix with build 34340 installed, but before build 35860]

 

Bert, so glad to hear you've resolved it!