Backup task completed successfully but has warnings, unknown status and error messages..
Hi all,
Just purchased Acronis True Image 2018 a few days ago, set it up and ran a few backups (by clicking backup manually) to make sure everything is working well. So far everything has been great, however last night was the first time the job ran by itself as per my scheduled task and although it says it completed successfully I am still concerned about some of the warning and error messages.
The current setup is this. I have a Synology wired up to my gigabit router, the desktop that was doing the backup is also connected to the router via a gigabit. These backups normally do not take long at all and during my initial setup it was working flawlessly when manually running the backup.
Any help with these warning and error messages would be appreciated.
Here is a copy of the scheduled backup that was ran >
2017-09-26T02:00:02:041+10:00 20236 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 2017-09-26T02:00:02:042+10:00 20236 I00640002: Operation SSD_500GB_OS started by schedule. 2017-09-26T02:00:02:042+10:00 20236 I00640000: Operation description: C Drive OS Backup (Weekly on Tue at 2:00 AM). 2017-09-26T02:00:02:296+10:00 20236 W001000CA: Error 0x1000ca: Failed to obtain path of the snapshot manager volume. | trace level: warning | line: 0x14181c22ef45ab6f | file: k:\9207\core\fdisk\volume_w.cpp:485 | function: win_vol_handler::VolGetPath | line: 0x14181c22ef45ab6f, k:\9207\core\fdisk\volume_w.cpp:485, win_vol_handler::VolGetPath | $module: ti_demon_vs_9207 | | error 0x9: Unknown status. | line: 0x2aacb7b2ab852ac | file: k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40 | function: Fdisk::AddKstatusError | line: 0x2aacb7b2ab852ac, k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError | code: 0x2 | $module: ti_demon_vs_9207 | | error 0xfff0: The system cannot find the file specified | line: 0xbd28fdbd64edb8f1 | file: k:\9207\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, k:\9207\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x80070002 | $module: ti_demon_vs_9207 2017-09-26T02:00:02:298+10:00 20236 W001000CA: Error 0x1000ca: Failed to obtain path of the snapshot manager volume. | trace level: warning | line: 0x14181c22ef45ab6f | file: k:\9207\core\fdisk\volume_w.cpp:485 | function: win_vol_handler::VolGetPath | line: 0x14181c22ef45ab6f, k:\9207\core\fdisk\volume_w.cpp:485, win_vol_handler::VolGetPath | $module: ti_demon_vs_9207 | | error 0x9: Unknown status. | line: 0x2aacb7b2ab852ac | file: k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40 | function: Fdisk::AddKstatusError | line: 0x2aacb7b2ab852ac, k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError | code: 0x2 | $module: ti_demon_vs_9207 | | error 0xfff0: The system cannot find the file specified | line: 0xbd28fdbd64edb8f1 | file: k:\9207\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, k:\9207\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x80070002 | $module: ti_demon_vs_9207 2017-09-26T02:00:02:298+10:00 20236 W001000CA: Error 0x1000ca: Failed to obtain path of the snapshot manager volume. | trace level: warning | line: 0x14181c22ef45ab6f | file: k:\9207\core\fdisk\volume_w.cpp:485 | function: win_vol_handler::VolGetPath | line: 0x14181c22ef45ab6f, k:\9207\core\fdisk\volume_w.cpp:485, win_vol_handler::VolGetPath | $module: ti_demon_vs_9207 | | error 0x9: Unknown status. | line: 0x2aacb7b2ab852ac | file: k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40 | function: Fdisk::AddKstatusError | line: 0x2aacb7b2ab852ac, k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError | code: 0x2 | $module: ti_demon_vs_9207 | | error 0xfff0: The system cannot find the file specified | line: 0xbd28fdbd64edb8f1 | file: k:\9207\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, k:\9207\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x80070002 | $module: ti_demon_vs_9207 2017-09-26T02:00:02:299+10:00 20236 W001000CA: Error 0x1000ca: Failed to obtain path of the snapshot manager volume. | trace level: warning | line: 0x14181c22ef45ab6f | file: k:\9207\core\fdisk\volume_w.cpp:485 | function: win_vol_handler::VolGetPath | line: 0x14181c22ef45ab6f, k:\9207\core\fdisk\volume_w.cpp:485, win_vol_handler::VolGetPath | $module: ti_demon_vs_9207 | | error 0x9: Unknown status. | line: 0x2aacb7b2ab852ac | file: k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40 | function: Fdisk::AddKstatusError | line: 0x2aacb7b2ab852ac, k:\9207\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError | code: 0x2 | $module: ti_demon_vs_9207 | | error 0xfff0: The system cannot find the file specified | line: 0xbd28fdbd64edb8f1 | file: k:\9207\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, k:\9207\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x80070002 | $module: ti_demon_vs_9207 2017-09-26T02:00:04:006+10:00 20236 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 2017-09-26T02:00:04:018+10:00 20236 I013C0000: Operation: Backup 2017-09-26T02:00:04:020+10:00 20236 I0064000B: Priority changed to Low. 2017-09-26T02:00:04:240+10:00 20236 I000B03F0: Create Backup Archive From: Disk 1 To file: "nas://MAPASYNOLOGY.MAPA/Backups/SSD_500GB_OS.tib" Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\USERNAME\AppData\Local\Temp, C:\Users\USERNAME\AppData\Local\Microsoft\Windows\INetCache, C:\Users\USERNAME\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\USERNAME\AppData\Local\Opera Software, C:\Users\USERNAME\AppData\Local\Mozilla\Firefox\Profiles, C:\Windows\CSC 2017-09-26T02:00:04:243+10:00 20236 I000101F8: Pending operation 173 started: 'Creating partition image'. 2017-09-26T02:00:07:443+10:00 19704 I00640000: Writing full version to file: SSD_500GB_OS_full_b9_s1_v1.tib 2017-09-26T02:00:08:535+10:00 20236 I000101F8: Pending operation 173 started: 'Creating partition image'. 2017-09-26T02:05:44:570+10:00 20236 I000101F8: Pending operation 173 started: 'Creating partition image'. 2017-09-26T02:05:44:589+10:00 20236 I000B0000: Deleting backup file with path nas://MAPASYNOLOGY.MAPA/Backups/SSD_500GB_OS_full_b8_s1_v1.tib. 2017-09-26T02:05:44:699+10:00 20236 I00640000: The following backups have been successfully created: "nas://MAPASYNOLOGY.MAPA/Backups/SSD_500GB_OS_full_b9_s1_v1.tib" 2017-09-26T02:05:44:771+10:00 20236 I013C0006: Operation has succeeded.


- Log in to post comments

Axho, welcome to these User Forums.
The key issue with the error messages in your task log is related to the Microsoft VSS snapshot service being used for the backup.
I would suggest downloading the Acronis VSS Doctor program and running this to see what issues this picks up on your computer - take the option to attempt to repair issues if this is provided.
- Log in to post comments
In reply to Not sure about the trace… by truwrikodrorow…

Is K: the mapped drive letter of the Synology NAS?
No, the Synology is mapped to S: and a second volume is mapped to V:
Also to note, I have a third Synology volume which is labeled as "Backups" and this is not mapped to the PC at all. Instead, within True Image 2018 for destination I selected "NAS" option and I typed in the credentials for the Synology, tested the connection and it worked and backups have no problem going there and deleting the old previous backup.
- Log in to post comments
In reply to Axho, welcome to these User… by truwrikodrorow…

Thanks as well steve, I'll check out Acronis VSS Doctor and see what it finds and report back here
- Log in to post comments

Just wanted to update that after running Acronis VSS Doctor, it detected one issue with one of my VSS Shadow Volumes on C:.. I ran the fix for it and reboot the PC and after running some test backups I no longer get the errors or warnings.
- Log in to post comments

Axho, glad that the VSS Doctor was able to fix the problem you were seeing, thanks for giving feedback.
- Log in to post comments