Backup fails with Failed to save file content.

[aurorait]

We have a backup that is failing with the error:

Code: Select all

Failed to save file content. Access is denied RPC function call failed. Function name: [DoRpcWithBinary]. Target machine: x.x.x.x

This backup is backing up 17 VM's so we don't want to redo the entire backup. The backup has been running fine for weeks and then started having this error. We have rebooted the server that has Veeam Backup & Replication installed, but it still errors out.

[nbarsotti]

This just started happening to my server last night too. Do you have a resolution?

[aurorait]

Nothing yet. I checked my MIcrosoft Updates and nothing had been installed last night. No changes have been made on the server from what we can tell.

[Vitaliy S.]

Please avoid posting log snippets as requested when you click New Topic. If you want to troubleshoot this issue further, please open a support case with our support team and include your support case ID here, instead of logs.

[totalhavoc]

Have you had any luck with this? My server just started doing the same thing. I submitted a support request but I figured this may be quicker

[Gostev]

Someone please let us know the support case ID for this issue. Otherwise, we will never know the resolution and will be unable to assist future posters. People are quick to post issues, but very few return to update the topic with the resolution - which is one of the reasons why we require support case ID (allows us to look up the resolution in future). Thanks!

[tsightler]

My understanding is that this is a known issue and that development is working on a hotfix to address it. It appears to have something to do with the size of the metadata file (.vbm) that causes it to fail.

[jhalscott]

Any resolutions? We just started having this problem yesterday afternoon. This forum post appaers to be all there is on the Internet about it. We just opened a support incident, but haven't heard anything back yet.

[Sethbartlett]

It typically means that your VBM file is too big to push across RPC. I believe our team is working on addressing this currently. As a workaround, you will want to reduce your number of restore points/split vms up in the job as the limit seems to be around 4 MB in size of the VBM.

[seiniku]

Is there a hotfix out for this yet? I have run into this problem yet again, after recreating all my jobs less than a month ago. Support ID 5163841

[Gostev]

If you have the support case open for this issue, you will get the hotfix as soon as it is available.

[TimeKnight]

I am having this same problem. Hoping the fix will be available soon. Support ID 5170297

[jctong]

this is happening to me too... havent had one good backup since 1/26
also does anyone ever check the online ticketing system, i get an autoreply message then nobody follows up

[Vitaliy S.]

What is you support ticket number?

[jctong]

Thank you for contacting Veeam Customer Support. Your Support Case has been opened and is 5170391.

[jctong]

got replied back by veeam support:

"We currently have a known issue that if the VBM file grows over 4 MB in size the job will fail with DoRPCWithBinary RPC Function call. The current work around is to break your jobs up into smaller groupings to prevent the VBM to grow to this size."

i guess the first time i read it in one of the previous posts, i didnt want to believe that that was the _only_ solution... but i guess it is, for now.

similar situation as OP... my job has 135 VMs, just going to be a big pain to have to split it up then put it back as one job once the patch is ready. splitting it up is going to hurt your dedupe and compression and since each job is independent of each other, you're going to need a whole ton of free disk space if you decide to keep the old jobs around to be able to restore from until they get aged away.

any eta for patch? maybe i can just go w/o for a couple days so i dont have to make a bunch of smaller jobs (i doubt i have the disk space to accomodate anyway...)

[Vitaliy S.]

Juan Carlos, this patch is currently being validated by our QC team, so it should be available very soon.

[kocher]

Hi,
I am having the same issue. Is there any news about a fix?

Thanks,
Kristian

[Vitaliy S.]

Kristian, it's better to contact our support team directly to be notified on this hotfix availability.

[TimeKnight]

I saw that patch 3 (6.0.0.181) is starting to trickle out. Does anyone know if patch 3 addresses this problem?

[jctong]

hard to say.. i got an email saying that i should check here periodically: v6 Known Issues and Patches

but it makes no mention of our specific problem. i think i'm going to be forced to recreate my jobs (use the workaround to split them up) if a patch doesnt arrive by the end of this week

[foggy]

Yes, patch 3 includes the fix for this issue.

[Gostev]

v6 patch #3 addresses this issue.

[iqit]

I just confirmed that this patch + reboot fixed this issue for me.