by collinp » Tue Jul 08, 2014 1:19 am people like this post
I have noticed that after upgrading to 184.108.40.2061, my jobs take longer to process. I am running onhost with the MS VSS provider. The jobs pause for quite some time on the "updating auxiliary data backup_doc" and "updating auxiliary data writer_doc" before the backups again. Are there some extra checks on the backup process with the latest patch?
by collinp » Tue Jul 08, 2014 1:32 pm people like this post
Nothing has been changed. The jobs process quickly at the beginning of the backup window and then as jobs pile on to where there are 15 jobs or more running simultaneously, most Hyper-v and VMware jobs hang with the messages updating auxiliary data... If I reboot the B&R server, the jobs begin processing quickly again. I currently have concurrent tasks set to 2 on each Hyper-v host and max snapshots per CSV also set at 2.
A strange twist is I enabled Parallel Processing last night and the jobs processed more timely and I did not get the hangs on updating auxiliary data... Something is happening when more and more simultaneous jobs pile up (even though I have throttles in place). Parallel processing made the jobs run quicker and less jobs piled up as a result.
by v.Eremin » Tue Jul 08, 2014 2:22 pm people like this post
According to the QA team, there might be multiple reasons of job hanging during the said step, one of which is long backup chain, etc. However, it's hard to say which one appears in your particular case.
Thus, if you can't cope with job updating auxiliary data slowly, then, you should open a ticket with our support team and let them observe live performance.
by electro » Thu Feb 26, 2015 3:44 pm people like this post
Hello, I didn't find any topic about problems with the v8 patch 1 issues. Maybe someone could help me. I have a cluster of two Windows server 2012 R2 hosts, their are running 13 virtual machines. Veeam is installed on a virtual machine with Windows server 2012 R2 with latest updates, backup repository is a VHDX disk attached via SCSI controller. So recently i updated veeam backup and restore 220.127.116.11.817 version to 18.104.22.168.917 and issues began that installation day. After updating my backup got stuck on "updating auxiliary data writer_doc", after 14 hours of waiting I canceled that backup task. I created a new task with to backup only one VM. It got stuck on procesing, procesing speed just dropped and that's all. No errors, events or what so ever. Tried to uncheck The "Enable application-aware procesing" and "Enable guest file system indexing", still backup task hangs. By the way both hosts have latest windows updates and all updates that veeam recommends.
by v.Eremin » Fri Feb 27, 2015 9:31 am people like this post
Unfortunately, OP has never come back to update the topic with found resolution. Neither has he provided his support ticket number, so, I can't track the case. Thus, keep working with the support team on addressing that.
By the way, as you can see, the problem of slow update of auxiliary data has been reported before, so, I doubt that is directly related to version 8 patch 1.
by feelgoodeule » Mon Jun 15, 2015 8:33 am people like this post
Somebody can give me a hint on this one?
Setting: Hyper-V Cluster to back up, backupserver still with Veeam B&R Version 22.214.171.1241
Issue: Some VM (Windows Server 2012, Windows 2008 R2 with Oracle on them) stuck when beeing processed. The last step I see in the details of the running backup: "Updating auxiliary data writer_doc", a warning before that saying "Failed to flush change tracking data. " The backup of the particulary VM gets stucked with that, leaving other VMs in the same Job "pending". So I don't have any Backup, the whole job is freezed, I have to cancel the job. If I create a new job with just the erroneous VM, same result. If I create a new job with the same settings for another VM , everything is fine.
We face this behaviour since the last weekend without having changed neither the VM (last booted months ago), nor the backupserver. Before that everything went fine.
Any help appreciated, I have not opened a support case yet.
by feelgoodeule » Thu Jun 25, 2015 12:27 pm people like this post
Here is the Case # 00943173
In the meantime I updated to Veeam B&R v8 U2b. Same thing. I found out, that the problem only exists when I add VMs through SCVMM-Host-VM. When I add directly the Hosts, the same VM gets backed up. Still it is not clear too, what made the issue appear suddenly, after months of smooth functioning.
I still have no response from the support team, they hoped that the update would do the trick. But it didn't.
by Dima P. » Thu Jun 25, 2015 2:33 pm people like this post
Michael, Thank you for the heads-up! I am quite surprised that update to the latest version did not solve the issue. I’ve noticed you have uploaded the fresh portion of debug logs – let’s await for support’s team investigation results.