Cluster node [HyperV node name] was not found.

[lenart.plausteiner]

Hi,

I recently upgraded mine Veeam B&R v7 to Veeam B&R v8. Now I get errors like this Cluster node [*****] was not found, OR VM is no longer processed by this job.

I have v8 + Update rollup, so it's build 8.0.0.917.

Any help/hint would be appreciated.

Thanks for help.

[Vitaliy S.]

Did you do anything to your source infrastructure (like doing any updates)? Can you run a rescan job of the infrastructure via your Veeam backup console?

[lenart.plausteiner]

Hi,

I ran rescan job several times but nothing really changes. In rescan job everything OK, I see all of my host within Hyper-V cluster.

No, source infrastructure is same as before upgrade to v8.

This is from "replication job" same message is with "backup job":

[Vitaliy S.]

Please avoid posting log snippets as it is described in our forum rules when you click New Topic. If rescan job does not fix this, please open a support case with our technical team and post your case ID in this topic. Thanks!

[lenart.plausteiner]

I opened support case under # 00877535. I hope there will be quick response from your technical team.

I tried to add standalone HyperV node, which is listed within HyperV cluster, under managed servers and then I edited corensponding job. Job after this succesfully starts, but it creates full snapshot.

[Vitaliy S.]

You mean full backup, not snapshot, right? Since VM ID has changed (was obtained from the host, not from the cluster) a full backup will be required, this is excepted behavior. You will be able to do incremental backups if source infrastructure remains in-tact.

[lenart.plausteiner]

Yes sorry, Full backup.

Yes, I know that VM under this backup Job gets new ID. But it's strange that B&R can't find the old one (VM ID) under old configuration, which hasn't changed before or after upgrade od B&R.

It's strange, that if I create new backup job within that infrasturcture (old), job also fails, but I can point to the source VM I can succesfully browse for any VM.

[Vitaliy S.]

Debug logs will tell the exact reason why job discovery fails to detect VMs in the cluster, so let's wait for our support team to respond.

[lenart.plausteiner]

Hi.

An update to this problem.

Support team was very helpful.

It looks like that Veeam B&R in v8 is sensitive on using upper/lower case in server names within HyperV/Failover cluster. After correcting those names in Veeam SQL DB everything is back to normal, and "It just works".

[GladstoneRC]

This is my exact problem. Veeam sees the old server name as lower case and the new name is uppercase.

Is there a procedure to fix this?

[lenart.plausteiner]

Yes. With me Veeam support helped me alot, but If you have knowledge of SQL you can fix it on your self. Find and replace record in VeeamBackup database in table "hosts". You will see something familiar like this "HyperVHost1" with GUID 'ABDFBF1-C6D9-6A8C-7C8D-9FBC8BD78638', and then you can repair host name to excatly what what you see in Windows Failover Cluster manager lower or UPPER case as server name.

Both parameters (host an GUID) you see in Veeam realtime log, within Backup job.

I hope that this will help you.

[GladstoneRC]

Thanks Lenart, that was it !!!! All working now

Can someone from Veeam add a fix to the next release of Backup and Replication to see lowercase and UPPERCASE as the same machine.

[Vitaliy S.]

Gladstone, I will pass this info to our QA team. Thanks!