Paul, what Veeam B&R build number are you currently at? There used to be an issue regarding disk digests size exceeding the RPC call limit causing similar error, it was addressed in one of the patches. If that is not the case, it's better to contact our technical team directly for deeper logs analysis. Thanks.
Cedric, please contact technical support directly. Paul's case was closed due to inactivity from his side and as I can get from the case notes, there was something to do with some old VM that was not backed up but had not been deleted from backup files due to the fact that 'Remove deleted VMs data from backup' setting was not enabled. This might not be your case though, you'd better open your own case and provide the logs for review. Thanks.
Thanks for the input, that very well may be my issue as well as I have removed a vm in recent history. I will open a ticket and post new forum post if it something obvious that might be helpful to others.
Sorry guys, I never get notifications of replies to my posts here so wasn't aware this had been commented on. Yes, in our case it appeared to be related to a deleted VM & I think has since been resolved by removing that deleted VM from the copy job.
Is this issue still there with Veeam B&R version : 8.0.0.2030 ? I'm backing up 5 VMs in one job, and one machine is giving this warning each time after the backup is done.
"Failed to perform post-backup application-specific VSS processing Details: RPC function call failed. Function name: [BlobCall]. Target machine: [abc.abc.abc.abc]. RPC error:The remote procedure call failed. Code: 1726"
We had a situation where a backup copy job of 8TB of VMs was stalling the data transfer because it would error out daily on the following error: Failed to perform backup file verification
After calling support (Case # 01131058) they had me extend the "Copy Every" window and push the health checks to two months. After saving the settings and telling it to restart the job, data is now flowing... Question now is will this happen again....?
I guess I will have to wait until the last day in November to find out but I wanted to hear from you guys on this...
Anyone see this before? The client has a decent pipe to the internet as its copied 250gigs in just one day.....
What are the recommended settings for this type of config?
I have a suggestion.... If the verification needs to finish before the job will complete, have it auto extend copy window, that is for jobs that don't have scheduled start and stop times.
The issue you're facing is not necessarily related to corrupted backup chain. It might be caused by inability of backup copy job to finish verification in the allowed window. So, it might be worth double checking that.