Unable to install backup agent : cannot connect to <HOSTNAME> Error: Unable
to get BIOS UUID
Connectivity is confirmed (can telnet to hostname + port), credentials are
confirmed. What could be the problem? How do I troubleshoot such a generic
error message?
I've got the same error on a test machine, didn't try it on my productive system yet.
Using Veeam B&R 9.5 Update 3 and a (clean) Debian7.1. Had Veeam agent installed before, tried updating and this error came up.
Removed the VAL and it's the same error (obviously)
It's likely to be a bug. Please open a support case so the team can confirm it, and post your case ID. When you contact support team you can mention that your case is likely to be related to another case, and it would be beneficial for both parties if they could pass it directly to the owner of the case # 02433497.
Ran into the same issue. Opened case with support (02456223) and was told that this is a bug. Was advised to go back to managing/running backups from physical server.
Hopefully the next release will work as advertised.
Hopefully the next release will work as advertised.
VBR requires managed host to provide its BIOS UUID. If BIOS UUID cannot be obtained neither via dmidecode, nor from /sys/class/dmi/id/product_uuid, then VBR won't be able to install the agent and put the host into a managed mode. That might happen on some VPS systems, for example. Would you provide more details on your setup please?
Hello, I have just installed the trial version and I get the same error.
The host that I'm trying to add is a centos6 machine on KVM hypervisor (Proxmox).
the file /sys/class/dmi/id/product_uuid does not exists and
Issue has been known for months - just received a response to my follow-up ticket (#02691539) and was told this is is a known limitation. Agent for Linux 2.0 system requirements (https://helpcenter.veeam.com/docs/agent ... tml?ver=20) have been amended after people started to ask about this issue:
** Required for Veeam Agent management — a valid UUID must be obtainable either from dmidecode | grep -i uuid or from /sys/class/dmi/id/product_uuid.
Doesn't seem quite fair to add a requirement after customers have already bought licenses not knowing about this. Afterall, manageability through B&R is the most important new feature in v2.
Can you confirm that this is being worked on? Developing an alternative for a DMI-provided UUID is not rocket science ...
Can we get a hotpatch for this please? I've put in about six hours of prep (million firewalls to contend with etc) just to get our agent backup test system deployed, and now this (really surprising) bug has smacked all the work to a dead stop.
Edit: worth noting the test system is a Supermicro Atom system (A1SAi). Using the cheap stuff for testing, although we run numerous Atom systems and will need to be able to back those up.
'If you truly love Veeam, then you should not let us do this ' --Gostev, in a particularly Blazing Saddles moment
As I suggested in my support ticket, the following can easily be used without collisions and does not require product_uuid to be present which apparently it isn't in some Supermicro systems:
echo $(dmidecode) $(ifconfig -a) | md5sum
'If you truly love Veeam, then you should not let us do this ' --Gostev, in a particularly Blazing Saddles moment
True, this one provides unique id, however the id has to be more or less peristent and should not change very often. NIC replacement will cause changes in this case, and I believe that NICs do burn out occasionally. R&D team is aware if the issue and we are looking for ways to resolve it.
What about using /etc/machine-id - it's generated at install time and doesn't change afterwards
This should work, however in this case if you deploy VMs from a single template you will have to change it to avoid duplicates. Alternative option would be to generate our own unique id before agent installation, if no other suitable id has been found.
Long story short:
Oracle RMAN Backups will not run unless the user being used can read `/sys/class/dmi/id/product_uuid`
This is the proper way to do that
`sudo chmod 444 /sys/class/dmi/id/product_uuid`
The ERROR that leads to this looks like the following…
`:: Session failed: Failed to license host: unable to get BIOS UUID with host plug-in due to lack of permissions.
Use --set-credentials plug-in configuration option as root.`
*It does NOT need to be ran by root as the error is suggesting and is bad practice. It’s a file that veeam is only using to make a license count.*
Thanks for sharing this information with us, we'll think about possible options to reflect the way of solving that issue in the corresponding error message or on our help center.
' --Gostev, in a particularly Blazing Saddles moment