cancel
Showing results for 
Search instead for 
Did you mean: 

Error at full backup after upgrade

vpa
Level 3

This installation is upgrade from previous verison 2016, not sure exactly. Now VSR 18 SP1. Backup tried full backup, because it is first run of task in new version. I'Ve been trying this 3 weeks and same error. After a few hours (7-10) an error is happened. 

Result (0xec8f17b7 23 VPRO_ERROR_CREATE_IMAGE Args [2] Arg (0xbab000d 57 Drive Backup of Local Disk (*:\), ESP (*:\), System (C:\)) Arg (0xbab0012 Result (0xebab0005 18 ERROR_ERRORS_EXIST Args [4] Arg (0xbab0012 Result (0xe7d1001f 27 FILEACCESS_ERROR_CANT_WRITE Args [1] Arg (0xbab0012 Result (0xebab03f1 14 ERROR_OS_ERROR Args [1] Arg (0xbab000d 16 Neplatný podpis.);)<9 1.0-*-*-* >);)<9 1.0-*-*-* >) Arg (0xbab0012 Result (0xe7d10046 30 FILEACCESS_ERROR_CANT_SET_SIZE Args [1] Arg (0xbab0012 Result (0xebab03f1 14 ERROR_OS_ERROR Args [1] Arg (0xbab000d 31 Došlo k neočekávané chybě sítě.);)<9 1.0-*-*-* >);)<9 1.0-*-*-* >) Arg (0xbab0012 Result (0xe7d1001f 27 FILEACCESS_ERROR_CANT_WRITE Args [1] Arg (0xbab0012 Result (0xebab03f1 14 ERROR_OS_ERROR Args [1] Arg (0xbab000d 16 Neplatný podpis.);)<9 1.0-*-*-* >);)<9 1.0-*-*-* >) Arg (0xbab0012 Result (0xe7d10046 30 FILEACCESS_ERROR_CANT_SET_SIZE Args [1] Arg (0xbab0012 Result (0xebab03f1 14 ERROR_OS_ERROR Args [1] Arg (0xbab000d 31 Došlo k neočekávané chybě sítě.);)<9 1.0-*-*-* >);)<9 1.0-*-*-* >);)<18 1.0-Backup-Image-* >);)<18 1.0-Backup-Image-* >
Details:
Source: Veritas System Recovery

Some of errors are in Czech description - my translation is here: 0xbab000d 16 Neplatný podpis. = Invalid signature.; 0xbab000d 31 Došlo k neočekávané chybě sítě. = There was an unexpected network error.

21 REPLIES 21

Markus_Koestler
Moderator
Moderator
   VIP   

Whats the target of the backup job? A NAS device?

Yes, it is Synology. A week later I've been tried full backup job at different timerange and ot was succesfull. A week ago has been made automatic upgrade W10 to version 1809 (really) and from that time the problem is again with no solution, different time range doesn't help anymore.

Markus_Koestler
Moderator
Moderator
   VIP   

One thing you could try is rebooting the NAS, in case you didn't try that already.

Has been made, BTW upgraded to last version, didn't help.

Markus_Koestler
Moderator
Moderator
   VIP   

I quite sure Windows 1809 is not yet supported by VSR, according to https://www.veritas.com/content/support/en_US/doc/VSR_18_SCL only 1803 is supported as of now. So to raise a case you'll have to wait a little bit. Hopefully Veritas will release a VSR 18 SP2 with support for 1809.

criley
Moderator
Moderator
Employee Accredited

@Markus_Koestler

@vpa

Yes, the 1809 build will be fully supported when we release SP2 for VSR 18. The release of SP2 is currently planned towards the end of November.

I know, but same problem was in 1803 too and without solution.

Markus_Koestler
Moderator
Moderator
   VIP   

Well for me it looks like a network or NAS device issue. We had similar errormessages in the past but after switchting NAS devices or limiting traffic to the NAS device everything worked out fine.

criley
Moderator
Moderator
Employee Accredited

I agree, this looks like some sort of network issue to me. The errors (cannot set file size etc) point towards this.

You could try and split the backup into small chunks (4GB for example) to see if this helps. This can be done by editing the advanced options within the backup job.

I have 3857MB set. Message is shown after more that 8 hours, usually at night. Not at the same time, when I compare different tries.

criley
Moderator
Moderator
Employee Accredited

@vpa

So the backup runs for more than 8 hours? How much data are you backing up?

This is almost certainly a network issue. I would suggest that you investigate the network path between the 2 devices, including network card settings.

400GB. I will try to find time and run backup with such setting to see job in time when error happens.

 

Nothing new found. I tlooks that it has nothing to do with network, it looks that main error is Invalid signature (in translation). Files are created at store with tmp extension at end of backup it shows error message above.

criley
Moderator
Moderator
Employee Accredited

@vpa

OK, but you said previously that it takes at least 8 hours to backup 400GB - this suggests some network issue in your environment. This is really slow.

The alternative is that you wait for the release of SP2. If that does not help, probably best to open a support case for this issue.

vpa
Level 3

Windows 10 1809, all updates till yesterday, ie 11.12.2018. SSR 18 SP2.

Has been removed such 60GB from HDD, so there is such 344GB (377GiB) of data. After 8:18 hours I have successful backup again with size 277GB. 

So I think that must be problem somewhere with a backup size. The biggest backup size I have is 320GB from August (9:57 hours).

Looks like i have the same problem, just installed the latest backup service packlast week and now getting:

Result (0xec8f17b7 23 VPRO_ERROR_CREATE_IMAGE Args [2] Arg (0xbab000d 93 Laufwerk-Backup von System-reserviert (*:\), Local Disk (*:\), SSD-BOOT (C:\), HDD-DATA (D:\)) Arg (0xbab0012 Result (0xe4f30158 28 SYMTRACK_VSS_E_PROVIDER_VETO Args [2] Arg (0xbab000d 19 VSS_E_PROVIDER_VETO) Arg (0xbab0006 0x80042306);)<18 1.0-Backup-Image-* >);)<18 1.0-Backup-Image-* >
DENTFL-Details: 
DENTFL-Quelle: Veritas System Recovery

or

Result (0xec8f1c50 29 VPRO_ERROR_CREATE_FILE_BACKUP Args [2] Arg (0xbab000d 24 Backup eigener Dokumente) Arg (0xbab0012 Result (0xe4f30158 28 SYMTRACK_VSS_E_PROVIDER_VETO Args [2] Arg (0xbab000d 19 VSS_E_PROVIDER_VETO) Arg (0xbab0006 0x80042306);)<23 1.0-Backup-FileFolder-* >);)<23 1.0-Backup-FileFolder-* >
DENTFL-Details: 
DENTFL-Quelle: Veritas System Recovery

The VSS error looks for me like an source system issue  -- any idea?

Markus_Koestler
Moderator
Moderator
   VIP   

Wir haben auch diese Fehler gehabt, ein Reboot der Maschinen hat das gelöst.

criley
Moderator
Moderator
Employee Accredited

@HausGeist

That seems to be a different VSS error you are seeing. This may or may not be relevant: https://support.microsoft.com/en-gb/help/2582068/vss-e-provider-veto-error-message-when-you-create-v...

If not, please provide more details on exactly what you are backing up and how often you see this error.

You should also refer to the windows event logs for more detailed VSS errors.

I am not using a Windows Server 2008 but instead a normal client OS Windows 10.
The recent error is still: (backup of "My Documents")

Result (0xec8f1c50 29 VPRO_ERROR_CREATE_FILE_BACKUP Args [2] Arg (0xbab000d 24 Backup eigener Dokumente) Arg (0xbab0012 Result (0xe4f30158 28 SYMTRACK_VSS_E_PROVIDER_VETO Args [2] Arg (0xbab000d 19 VSS_E_PROVIDER_VETO) Arg (0xbab0006 0x80042306);)<23 1.0-Backup-FileFolder-* >);)<23 1.0-Backup-FileFolder-* >
DENTFL-Details: 
DENTFL-Quelle: Veritas System Recovery

It occures in the case of an FileSystem backup of files.
Also the DiskImages backups fail with error:

Result (0xec8f17b7 23 VPRO_ERROR_CREATE_IMAGE Args [2] Arg (0xbab000d 93 Laufwerk-Backup von System-reserviert (*:\), Local Disk (*:\), SSD-BOOT (C:\), HDD-DATA (D:\)) Arg (0xbab0012 Result (0xe4f30158 28 SYMTRACK_VSS_E_PROVIDER_VETO Args [2] Arg (0xbab000d 19 VSS_E_PROVIDER_VETO) Arg (0xbab0006 0x80042306);)<18 1.0-Backup-Image-* >);)<18 1.0-Backup-Image-* >
DENTFL-Details: 
DENTFL-Quelle: Veritas System Recovery

One symptome is that before backup the Windows VSS Service was running, afterwards not.
It starts after update to SSR 18 R2 --- on the Windows 10 patches i have no control, those come from Microsoft.
For this feedback i stated a manual backup:

Result (0x6c8f1f63 29 VPRO_INFO_MANUAL_BACKUP_START Args [1] Arg (0xbab000d 93 Laufwerk-Backup von System-reserviert (*:\), Local Disk (*:\), SSD-BOOT (C:\), HDD-DATA (D:\));)<9 1.0-*-*-* >
 DENTFL-Details: 
 DENTFL-Quelle: Veritas System Recovery

The backup failed because VSS blocked it. The EventVwr show:

Volumeschattenkopie-Dienstfehler: Unerwarteter Fehler "CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1,0xc0000000,0x00000003,...)". hr = 0x80070005, Zugriff verweigert
. 

Vorgang:
   Automatisch freigegebene Schattenkopien werden entfernt
   Anbieter wird geladen

Kontext:
   Volumename: \\?\Volume{308297ae-e0c1-11e1-8e88-005056c00008}\
   Ausführungskontext: System Provider

 Today I did try it again (manually restartet VSS daemon) -- Windows EventVwr looks so far OK:

Volume "SSD-BOOT" (\Device\HarddiskVolumeShadowCopy13) ist fehlerfrei. Es ist keine Aktion erforderlich.
Volume "HDD-DATA" (\Device\HarddiskVolumeShadowCopy14) ist fehlerfrei. Es ist keine Aktion erforderlich.

What is different --- this is now the Q1-2019 FullBackup, before it was a incremental backup attempt. If that fail again i will know in a weeks time. (i have setup quarterly full and weekly inremental backups of the disks).