First backup failed

[ferrus]

I've installed the Agent on a Linux blade server, added a trial license to the B&R console, created a Protection Group & Backup Job.

Everything worked perfectly, but when I run the backup job it fails with the following error:

Code: Select all

Failed to generate certificate for *servername*: BIOS UUID has been modified, please rescan the host

I've tried re-scanning the host - but the same error occurs each time.
This is the first time we've used a Veeam agent. Has anyone seen this error, or know the cause of it?

[PTide]

Hi,

Have you contacted support already? If so then please post your case ID.

Thanks

[ferrus]

No call yet - just scouting for quick solutions.
I'll place a call now.

[brodavdoug]

hello, I have exactly the same problem, did you find the solution ?

[ferrus]

Placed a support call a fortnight ago.
Originally, the solution from Veeam support was going to be a manual database update - but they've since advised that the issue is more complex, and may require a custom fix.

The case ref is 02469547, if you want to be considered for the same fix.

[brodavdoug]

Thanks I'll add it as comment in my service request thanks again !

[ferrus]

@brodavdoug

Quick update - just received a msg to say it's been confirmed as a bug.
Good to know that it's not an issue with our config/infrastructure.

Quite exciting - think I'm up to 3 or 4 Veeam bugs found now. If I reach 10, I hope I get a free pen

[PTide]

ferrus,

Good thing is that only one bug is related to VAL, maybe we should really put a bounty Thank you for bringing the update for fellow users.

[ferrus]

Final update to say the problem has now been resolved, by Veeam support.

Simple fix for RHEL7, custom patch for RHEL6.
I believe a permanent solution may be in the next version.

Quote case ref #02469547 if you have the same error.

[zilmar]

Hi Ferrus,

Is this custom patch for RHEL6 available for download anywhere? Or should I open a case?

Thanks!

[wishr]

Hi Zilmar,

Welcome to Veeam Community Forums and thanks for posting!

Yes, please reach out to our support team to get the fix.

Thanks