I contacted Veeam support and their response was to run an active full against the VMs that are failing - which seems to be the go-to response for all my recent tickets with them. I decided to go one better carved out some new ReFS storage for some new extents, a new SOBR, and a new backup job for these VMs. I'm running into the same issues.
Again, VMs live on the same hosts, in the same storage arrays, and are being backed up with the same job configurations on the same VBR server using the same proxies. Given this information, I'm inclined to believe it's not a network problem.
Some of my errors:
Code: Select all
Error: Failed to deserialize area object because its type is unknown: [1073741824].
Unable to retrieve next block transmission command. Number of already processed blocks: [1].
Failed to download disk '<VMName>-flat.vmdk'.
Reconnectable protocol device was closed.
Failed to upload disk. Skipped arguments: [vmfssan>];
Agent failed to process method {DataTransfer.SyncDisk}.
Error: Failed to process {Invoke} command
Details:
Agent: Failed to parse VCP command arguments: Attribute 'value' is not found
Failed to read VCP command from the stream
Reconnectable protocol device was closed.
Agent failed to process method {DataTransfer.BackupText}.
Error: Invalid packet size. Payload size: [1544880264]. Allocation size: [1048832]
Unable to retrieve next block transmission command. Number of already processed blocks: [0].
Failed to download disk '<VMName>-flat.vmdk'.
Reconnectable protocol device was closed.
Failed to upload disk. Skipped arguments: [vmfssan>];
Agent failed to process method {DataTransfer.SyncDisk}.
Error: The filename, directory name, or volume label syntax is incorrect.
Failed to open storage for read/write access. Storage: [<Extent>\<Job>\<VMName>.vm-09?�?-?ڐ?2].
Failed to backup text locally. Backup: [VBK: 'veeam:0:35e09ba0-4ac4-89d0 (ID)\summary.xml@Extent[b24c7ce744a1-acb5a4c1]<Extent>\<Job>\<VMName>.vm-09?�?-?ڐ?2'].
Agent failed to process method {DataTransfer.BackupText}.