Hello, miquel.mariano
Thank you for debug logs.
The issue happened when adding HPE Morpheus VME server to backup infrastructure.
When adding the server we create a service account on every cluster node which is managed by this server. That account is used for SSH connection to cluster nodes during backup in NBD mode.
In order to do it we call execution script request on HPE side.
In logs I see that the request was successful for the 1st and 2nd cluster node:
2025-12-02 18:49:44.3375 00021 [48867] INFO | [MorpheusController]: Successfully configured SSH access to the cluster host 1, IP address "10.10.10.81"
2025-12-02 18:49:45.0680 00019 [48867] INFO | [MorpheusController]: Successfully configured SSH access to the cluster host 2, IP address "10.10.10.82"
But it failed for the 3rd node:
2025-12-02 18:49:45.0680 00019 [48867] INFO | [MorpheusController]: Configuring SSH access to the cluster host 3, IP address: "10.10.10.83"
2025-12-02 18:49:51.3399 00019 [48867] ERROR | [MorpheusController]: Failed to configure additional settings for the HPE Morpheus VM Essentials clusters: Failed to execute the script: status Failed, exit code , error: , status message: : Veeam.Vbf.Common.Exceptions.ExceptionWithDetail: Failed to execute the script: status Failed, exit code , error: , status message:
As a result we haven't created service account on the 3rd node and haven't saved SSH credentials to VBR database.
I see later in logs that for master server (Morpheus):
2025-12-03 16:53:23.2501 00006 [441867] DEBUG | [DbProvider client]: ==> Response "Get" "
https://localhost:6172/api/masterServers", "code: 200", duration: "13 msec", headers: "[]", cookies: "[]", body: "
"ServiceUserCredentialsTag\\\":null
which causes that error - A credential tag cannot be null or empty.
Could you please answer a few questions
1) Did you have any errors on Apply step when registering HPE VME server in VBR?
2) Has the server been registered in VBR if there were errors in session?
3) Is the 3rd node working - 10.10.10.83. Is it possible to ping it from VBR?
4) Have you tried to go through Edit HPE VME server wizard? Normally we have to check for missing SSH credentials and re-create them.
If editing doesn't help you can try to re-add HPE VME server to VBR and check logs for "Successfully configured SSH access" messages for all cluster nodes.
Meanwhile I will try to do reproduce similar behavior on my lab and share results. Looks like a bug on our side with managing such cases.