Restores failing since Update2 of VBR

[Jeff L]

Updated VBR to update 2, now all our Endpoint backups fail restores with error:

"Restore failed: unable to find assembly Veeam.Backup.Model, Version=9.0.0.0,Culture=neutral, PublicKeyToken=bfd684de2276783a."

No updates are available for VEB. (currently running 1.5.306)

[JaxIsland7575]

Did you open a support case through the Control Panel in VEB? I would want to get a set of logs over to support then post the case # in this thread for tracking.

[Dima P.]

Hi Jeff,

Indeed, please submit a support case thru the VEB's Control Panel and post the case ID to this thread, so I could pass it direclty to QA. Thanks in advance

[Jeff L]

From the restore client or from live client?

[Dima P.]

Now I am confused. If the recovery was not working how you’ve managed to restore the machine? I was under impression that you got this error while running a Bare Metal Recovery.

[Jeff L]

I meant from the restore ISO (the BMR side) or from the live client that the backups are running from.

The client is still live, I regularly test the restore process.

[Dima P.]

Understood, thanks. Alive client works then.

[Jeff L]

Support case raised, 01894613

[Anguel]

For me a backup failed with a similar error. The endpoint had not been online for a longer time, so the backup returned a similar error:

Code: Select all

Full backup file merge failed Error: Die Assembly "Veeam.Backup.Model, Version=9.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a" kann nicht gefunden werden.

This means that the assembly cannot be found in German.
Then I ran backup again and it seems to run ok now.
I'm using latest updates for VBR and VEB.
Feel free to forward this to support if interested, I don't have time to report such bugs as this takes time.

[Jeff L]

Still with support, but looks like it could be related to the copy job on VBR;

The orginal backup works, the copy backup fails with the error.

[Jeff L]

All resolved! the solution was to disable the copy backup job. The explanation?
"The thing is that backup copy job is working continuously and it blocks backup files (vbk,vib and so on) for read\write operations.
Disabling the job unlocks the files and allows Endpoint to read them. If you plan to run a restore in future, please disable Backup copy job. It doesn't happen always, but in case of such error the first step is to disable a backup copy job."

[Dima P.]

Hi guys,

True, backup copy job may affect merge process of the VEB. I’ve just talked to QA team: this behavior was marked as a bug and will be fixed in upcoming versions of Veeam Backup and Replication 9.5 and Veeam Agent for Windows 2.0