RPC issues with latest Windows Updates?

[rjiupat]

Has anyone else seen an issue with some backups failing after applying the latest Windows Updates? I applied updates yesterday to our (non-domain joined) Veeam servers, and to half of our DCs. Today I see that all of the DCs failed to back up last night with this error:

4/13/2022 10:12:46 PM :: Task failed. Failed to expand object <DC_name>. Error: Host '<HyperV_Cluster>' either not a cluster or cluster services is unavailable.

The rest of the VMs in that job did succeed. Additionally, a replication job failed completely, with the same error.

I have submitted a support request (ID 05390787 ) but meanwhile wondering if anyone else has hit this. If you haven't applied the latest patches you might hold off a day or two. In gathering the logs my remote Veeam server gave an RPC error, which I know is one of the big vulnerabilities patched this month.

Edit: fixed case ID

[Mildur]

Hi Rjiupat

Thanks. The case number looks wrong.
Can you post the right one, please?

[rjiupat]

Fixed it!

[Mildur]

Thanks. I see you opened the case two hours ago.
Let us give support some time to analyze the provided logs.

[rjiupat]

Update - it seems to have been DNS. Support identified the issue and it seems to be working again.

I should have known, it's always DNS.

[Mildur]

Thanks for the update.

I'm glad you could resolve it.

[rcapone]

Hi rjiupat,

Could you expand a bit on the DNS issue you fixed? All my backups have started failing with the same error message - "Task failed. Failed to expand object <SERVER_NAME>. Error: Host 'HYPER-V_CLUSTERNAME>' either not a cluster or cluster services is unavailable.". I've checked everything I can think of. DNS is resolving the cluster & host names correctly, the cluster is running normally, and there are no errors in the event logs. The cluster passes validation, so I'm fairly confident that's not the problem. I'm hoping to get this resolved, but if I must open a ticket, I will.

Thanks.

[Mildur]

Hi Roger

In rjiupat's case the dns entry for the cluster hostname was missing.
If DNS is resolving your cluster, please open a case with our support and upload the log files.

Thanks
Fabian