True Image 2017 New Generation Premium - New errors in log.
I updated to 2017 True Image New Generation Premium from 2017 True Image.
I have backups run online morning and evening. Everyday, they say " " but the log has errors.
A) This set repeats over and over again:
trace level: warning
| line: 0xd8b61c024c929587
| file: k:\6116\products\imager\demon\app.cpp:1022
| function: TiDemonDaCommit::OnVssRetryableCallback
| line: 0xd8b61c024c929587, k:\6116\products\imager\demon\app.cpp:1022, TiDemonDaCommit::OnVssRetryableCallback
| $module: ti_demon_vs_6116
|
| error 0x10c442: Failed to start creating the volume snapshot.
| line: 0x3fec04e376b8a17f
| file: k:\6116\fdisk\win_snapshot.cpp:1161
| function: win_snapshot_core::CallSbLock
| line: 0x3fec04e376b8a17f, k:\6116\fdisk\win_snapshot.cpp:1161, win_snapshot_core::CallSbLock
| $module: ti_demon_vs_6116
|
| error 0x10c46b: VSS writer 'Registry Writer' with class ID 'AFBAB4A2-367D-4D15-A586-71DBB18F8485' has failed to process the snapshot.
| line: 0x3fec04e376b89d84
| file: k:\6116\fdisk\win_snapshot.cpp:142
| function: `anonymous-namespace'::ObtainVSSFailReasonSuberror
| line: 0x3fec04e376b89d84, k:\6116\fdisk\win_snapshot.cpp:142, `anonymous-namespace'::ObtainVSSFailReasonSuberror
| $module: ti_demon_vs_6116
B) Eventually the backup finishes..
2017-01-30 06:06:16:022 64224 D00170000: Slice 6A8A1CCF-FF15-49D2-A4E0-4FE58ED8AA66 is started
2017-01-30 06:06:16:054 64224 D00170000: Backed up 667 bytes
2017-01-30 06:06:16:054 64224 D00170000: Slice 6CFD1E90-2A47-43F9-950D-ECE4B0660FEB is started
2017-01-30 06:06:16:156 57092 D00030408: Verify result for certificate is 19.
2017-01-30 06:06:16:156 57092 D00030000: SSL connection using AES256-SHA
2017-01-30 06:06:17:059 64224 D000B0000: Exiting backup operation...
2017-01-30 06:06:17:176 64224 D000B0000: Exited backup operation
2017-01-30 06:06:17:176 64224 D000B0000: Preparing for cleanup...
2017-01-30 06:06:17:477 64224 D000B0000: Starting actual cleanup operation...
2017-01-30 06:06:18:036 64224 I00000000: Error 0x0
Do I have problem?
Also, why to all of the "Verify Certificate" errors end in "Verify Result for Certificate is 19" ? My research shows that return code seems to indicate a "self signed certificate" in chain.
I am running:
True Image 2017 New Genearation Premium Build 6116
Windows PRO 10 Version 1607 (OS Build 14393.693) (up to date)
HP Envy with I7 processor
Norton Internet Security (Up to date)
|
Folder backups with Online Backup.
On the GUI screen select (click Options) and the bottom of the window then, Advanced tab. click on Perrformance and network. make certain that the Snapshot for backup option is set as VSS without writers.
If the above option is set correctly you can try settimg the option to Acronis snapshot and see if that clears up the errors.
Thanks!!
Snapshot for backup option was set to just VSS. Changed it to ... without writers.
I will let you know results.
Curious, what is the difference?
Joe, see KB 59440: Acronis True Image 2017: 'Snapshot for backup' option overview for more information on these Snapshot options.
Thanks for the reference and info!
What is interesting is this line, under "VSS, without writers":
This option is default for file-level backups.
My install was an upgrade from the first 2017, and in neither case did I change the option, BUT VSS was there before I changed it at your suggestion.
Joe, it is difficult to be absolutely certain about what that setting was set to when you first installed ATIH 2017 - I have just checked one of my own tasks with ATIH 2017 NG which I had previously upgraded from ATIH 2017 build 5554, and my settings were just VSS like yours.
The KB document has only just been released and makes me wonder if the setting for "VSS, without writers" is now the default setting for new tasks for file-level backups, but older tasks just have "VSS"?
Steve, I think you are right about old tasks created in previous versions carying over to NG are bringing the default VSS setting with them.
I just created a new file/folder backup as a test - default was stilll VSS for me. This was an upgrade of NG over 5554.
Perhaps it changes to VSS without writers when it's saved, but it definitely shows "VSS" when setting up the new file/folder backup.
There is definately something going on here with this. In my case my install was a clean install and creating a new task does bring the default VSS without writers option.
Mine is also a clean install and it works same as Enchantech...VSS without writers is the default for file/folder backups.
Bummer, looks like it could be an overlooked item in the upgrade process. I'm guessing it assumes the old method of vss to be the default choice of the user. I will submit feedback.
Hello Everyone,
The intended default snapshot setting is "VSS" for disk/partition/Entire PC backups and "VSS without writers" - for file-level backups.
The option "VSS without writers" was introduced specifically for files and folders backups to save up to several minutes of time when VSS writers would be doing their jobs. Less data needs to be copied (incremental backups, small size of the source data) - more noticeable is the benefit from "VSS without writers" option. Complete VSS snapshot with all the writers in a usual home setup is needed only when backing up a system drive. In rare cases, when backing up files/folders of an application that uses transactions and at the same time has a VSS writer, for example, Microsoft SQL Server, the snapshot method should be changed from "VSS without writers" to "VSS" to ensure data consistency in the backup.
When the "New Generation" is installed over v5554 and older, VSS setting is not touched for existing backup tasks and remains "VSS". This is expected behavior.
However, when creating new file/folder backup tasks it was intended that the new default choice would be applied - "VSS without writers". There must be some issue with that scenario in general or in particular Bobbo's case. After we receive the feedback, we will look into it.
Regards,
Slava
Slava, thanks again for confirming this behaviour for VSS versus VSS without writers, I see that this is documented in KB 59440: Acronis True Image 2017: 'Snapshot for backup' option overview but I hadn't picked on the point that the defaults are different depending on the difference in what's being backed up.
Thanks Slava,
I went through the process this morning and it's working like you described now! I don't know why it was defaulting to VSS for file/folder backups the other day, but I have rebooted since then and tried 2 tests this morning with new file/folder backups and both started with VSS without writers. I'll keep an eye on this and if it happens again, I'll be sure to submit feedback and a system report. Maybe it needed that one time to set things straight after the upgrade, I'm not really sure.
Hello Steve, glad that I could be helpful here!
Bobbo, as with Active Protection, Acronis Notary and ASign, investigation of issues with this new VSS setting is a priority. If any abnormal behavior reproduces consistently, do not hesitate to send a system report, we will be waiting it.
Of course, this only applies to the VSS option itself: reports about backups failing due to an issue with Microsoft VSS infrastructure outside of Acronis would be processed with lower priority.
Regards,
Slava