Discussions specific to the VMware vSphere hypervisor
Post Reply
foggy
Veeam Software
Posts: 16832
Liked: 1361 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to retrieve next block transmission command

Post by foggy » Oct 01, 2017 10:31 pm

If nothing from this thread helps, I'd follow the advice of you engineer. What Veeam B&R version are you running, btw?

Andreas Neufert
Veeam Software
Posts: 2872
Liked: 499 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Oct 02, 2017 6:00 am

Hi, during my 6+ years with Veeam, this error popped up once in a while at my customers and was in most of the cases fixed by updating ESXi and VDDK Kit to newest update/version.
VDDK newest version => Install latest Version and Update of Veeam Backup & Replication.

A typical indicator that this can be fixed with this approach is, that the Veeam retry was successful always and produced valid backups.

If you can not backup at all with this error, there are several other things to check. See above:
Check if DNS is working with FQDN names for ESXi hosts correctly
and check the following Veeam KB entry that list all kind of things that could lead into the error: https://www.veeam.com/kb2008

kingsize
Influencer
Posts: 18
Liked: 1 time
Joined: Apr 21, 2017 6:28 pm
Full Name: King Size
Contact:

Re: Unable to retrieve next block transmission command

Post by kingsize » Oct 02, 2017 6:28 pm

foggy wrote:If nothing from this thread helps, I'd follow the advice of you engineer. What Veeam B&R version are you running, btw?
I am using veeam 9.5, I am sure when I am going to update to 9.5 Update 2, it will not fix this issue.

kingsize
Influencer
Posts: 18
Liked: 1 time
Joined: Apr 21, 2017 6:28 pm
Full Name: King Size
Contact:

Re: Unable to retrieve next block transmission command

Post by kingsize » Oct 02, 2017 6:33 pm

Andreas Neufert wrote:Hi, during my 6+ years with Veeam, this error popped up once in a while at my customers and was in most of the cases fixed by updating ESXi and VDDK Kit to newest update/version.
VDDK newest version => Install latest Version and Update of Veeam Backup & Replication.
ESXI is patched to the latest 6.0 HPE version.
DNS is working correctly
I already tried all of them written here: https://www.veeam.com/kb2008

It seems that the disk is corrupt. Engineer is telling me to check the vmdk file with vmkfstools.
http://www.vi-toolkit.com/wiki/index.ph ... air_a_disk

Alternativelly, I would suggest deploying vCenter and try to clone the VM. It's the bulletproof test which shoud show us what is wrong with the disk.

The problem is that I don't have storage left. Any recommendations? I need 300GB storage for the clone.

Andreas Neufert
Veeam Software
Posts: 2872
Liked: 499 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Oct 02, 2017 6:34 pm

Maybe. vddk error 13 is a infrstructure error of a code we get from vmware (vddk kit).

If the software update of ESXi host or version/update of veeam that include new vddk kit do not fix the issue you need to work on your infrastructure (maybe with vmware). You can check the above mentioned KB entry for tips and starting points.


Our Support can help here (this is not a support forum).

Andreas Neufert
Veeam Software
Posts: 2872
Liked: 499 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Oct 02, 2017 6:35 pm 1 person likes this post

thx for the feedback. we posted at same time.

kingsize
Influencer
Posts: 18
Liked: 1 time
Joined: Apr 21, 2017 6:28 pm
Full Name: King Size
Contact:

Re: Unable to retrieve next block transmission command

Post by kingsize » Oct 02, 2017 6:42 pm

Andreas, I have to check the disk. I have never done that before. Is there any manual on how to do it? Does the VM needs to be offline? Only thing I know is that I have to connect trough Putty with my esxi hosts and thats it...

Andreas Neufert
Veeam Software
Posts: 2872
Liked: 499 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Oct 02, 2017 7:04 pm

Here is an example I found at google http://blog.asiantuntijakaveri.fi/2012/ ... k.html?m=1

And here an exaple for console access by ssh
https://pubs.vmware.com/vsphere-51/inde ... t.3.6.html

Andreas Neufert
Veeam Software
Posts: 2872
Liked: 499 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Oct 02, 2017 7:06 pm

And if you have trouble with backing up the vm at all, you can download our Agent for Linux/Win with 30 days trial to create an image level backup on Operating System level.

kingsize
Influencer
Posts: 18
Liked: 1 time
Joined: Apr 21, 2017 6:28 pm
Full Name: King Size
Contact:

Re: Unable to retrieve next block transmission command

Post by kingsize » Oct 08, 2017 10:42 am

Ok so I will boot up with the recovery veeam agent iso on the effected VM. I will make a backup to the NAS.
After this has finished, I make a new vm with disk on the NAS. I boot up from the recovery veeam agent and restore from backup.

It should work?

Or do I have to install the veeam agent on the server and make a backup?

kingsize
Influencer
Posts: 18
Liked: 1 time
Joined: Apr 21, 2017 6:28 pm
Full Name: King Size
Contact:

Re: Unable to retrieve next block transmission command

Post by kingsize » Nov 04, 2017 5:42 pm

Got if fixed by myself. Anyone that is facing this issue, let me know. I can help you out.

davidkillingsworth
Enthusiast
Posts: 33
Liked: 4 times
Joined: Nov 21, 2011 5:41 am
Location: Hong Kong
Contact:

Re: Unable to retrieve next block transmission command

Post by davidkillingsworth » May 25, 2018 11:29 am

For anybody that has this issue again, you should check what virtual NIC card your Veeam backup server and your proxy's are using.

I just had this issue bite us again. We had this about 3 or 4 years ago and I even found my old comment about how I fixed it before in this or another thread by changing the VM guest virtual nic card to VMX3.

We bought a new server and setup a new VMware esxi 6.7 host. We tried replicating all of our VM guests onto it from two other older hosts (vmware esxi 5.1), one of which is going to be retired because the server hardware has run out of warranty.

From one VM host, all of the VM guests replicated fine. However, on another VM host, we had one very large VM guest that would fail every time we tried the replication.

Error was:
Error: Invalid packet size. Payload size: [1167126733]. Allocation size: [1048832] Unable to retrieve next block transmission command. Number of already processed blocks: [29574]. Failed to download disk. write: An existing connection was forcibly closed by the remote host Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.
I searched through this thread and decided to shut down both my existing Veeam server and the one proxy that I had setup on the new VM host. I changed the virtual NIC cards from E1000 or E1000E to VMX3. After re-configuring the IP address inside the Vm guest and rebooting, I was able to successfully run the replication job without any problem.

E1000 strikes again!!!!

Post Reply

Who is online

Users browsing this forum: No registered users and 21 guests