Host-based backup of VMware vSphere VMs.
Post Reply
masonit
Service Provider
Posts: 325
Liked: 23 times
Joined: Oct 09, 2012 2:30 pm
Full Name: Maso
Contact:

Backup issues after vCenter upgrade to 6.7

Post by masonit »

Hi

We have started to see backup issues on mainly large vms after upgrading vcenter to 6.7 (not U1). We are seeing the same errors on 2 virtual environments where both have vCenter version 6.7. Esxi hosts are not yet updated.

Case: 03293359
Error: VDDK async operation error: 2....
Cause: This happens on vms with atleast 5-6 harddisks. In vcenter 6.7, VMware have set a hard read buffer size limit (32 MB) that is not possible to change. When backup runs parallel on a vm with many harddisks this read buffer size is overcommited and backup fails. More info https://support.unitrends.com/Unitrends ... /000005944

Case: 03295615
Error: NTFS file: failed to read 16777216 bytes at offset 16779072 Failed to upload disk.
Cause: Started to happen after vCenter was upgraded to 6.7. Still investigating root cause with Veeam support.

VBR 9.5 update 3a

VMware strikes again! :(

\Masonit
TrevorBell
Veteran
Posts: 364
Liked: 17 times
Joined: Feb 13, 2009 10:13 am
Full Name: Trevor Bell
Location: Worcester UK
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by TrevorBell »

Hi,

Always best to open a support case. You will be surprised how quickly most cases get resolved once the logs are inspected by support.

Thanks

Trev
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by foggy »

Magnus already has a case opened and, as far as I can see, some of the engineer's suggestions did help, so it is being further investigated.
Kristien
Novice
Posts: 3
Liked: never
Joined: Feb 24, 2019 10:59 am
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by Kristien »

Hi, i know this is an old topic but what was the solution? I have the same problem :
Processing FILES_01 Error: NTFS file: failed to read 16777216 bytes at offset 0
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.

Support suggests to do a check disk but the machine can't go offline in this period.
Andreas Neufert
VP, Product Management
Posts: 6707
Liked: 1401 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by Andreas Neufert » 1 person likes this post

Veeam support provided a hotfix for the customers with that issue. This hotfix was later integrated in our Update 4. So please download and install Update 4a as a solution.
jrbaumann
Enthusiast
Posts: 41
Liked: 2 times
Joined: Oct 18, 2018 12:37 pm
Full Name: Jeff Baumann
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by jrbaumann »

Andreas,

Just wanted to mention that we are on 9.5 4a and are seeing this issue as well on multiple servers. I am opening a case with Veeam support now.

Jeff
masonit
Service Provider
Posts: 325
Liked: 23 times
Joined: Oct 09, 2012 2:30 pm
Full Name: Maso
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by masonit »

Solution for us was a regfix that we got from support. Update 4a did not solve our issue. Not sure if I should add the regfix here..?

\Masonit
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by foggy »

Hi Magnus, I'd first consulted with support since it was supposed that the fix was included in subsequent updates.
jamcool
Enthusiast
Posts: 67
Liked: 11 times
Joined: Feb 02, 2018 7:56 pm
Full Name: Jason Mount
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by jamcool »

what was the regfix?
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup issues after vCenter upgrade to 6.7

Post by foggy »

Hi Jason, please contact support directly to verify the issue and get the fix, if applicable. Thanks!
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Lewpy, Semrush [Bot] and 55 guests