Skip to main content
  • EN

Hello to everyone,

 

from yesterday I am receiving this error.

 

Veeam Backup & Replication 12 Community E. (today updated to v. 12.1.2.172) installed at Windows Server 2016

VMware Tools at the Veeam Server is the newest / Kompatibility OK

Windows Updates the latest. Firewall disabled.

 

3 Jobs (to the local / virtual HDD and to the NAS Server). Everything was just fine. Same error before the Veeam Update and after the update.

 

Backup mode: Reverse incremental / VSphere VMware Tools quiescence is and was disabled

 

Credentials Test completely OK

All Infrastructure re-scanned OK

 

I have also tried to completely delete one job from disk and start a new one: still the same error.

 

Veeam Server has been rebooted many times already, other Virtual Machines will be rebooted at the evening.

 

This is what the log is showing up:

 

p06.06.2024 15:51:52.204]    <28> 000Z]    Info (3)    Waiting for backup infrastructure resources availability
v06.06.2024 15:52:37.698]    <22> 8000Y]   Error (3)    0RPC] RPC client failed to call method fInvokerTestConnection]
r06.06.2024 15:52:37.698]    <22> 3000Y]   Error (3)    ;RPC] Der RPC-Server ist nicht verfügbar. (=UNAVAILABLE)
06.06.2024 15:52:37.698]    <22> 1000Y]   Error (3)    ;RPC] An exception was thrown from thread e12956].
t06.06.2024 15:52:37.698]    <22> 2000Y]    Info (3)    RPC] Reconnecting...
f06.06.2024 15:52:37.698]    <22> 0000Y]    Info (3)    8RPC] Retrying RPC call. Attempt: o1], Method: PInvokerTestConnection]

 

Could you help please or give any direction what to check?

Thank you. Have a nice day.

 

Karel

 

 

I would first start checking the logs for the job that is failing here - C:\ProgramData\Veeam\Baclup\JobName

If that shows nothing you will need to open a support ticket as this community is not technical support.

Hi @Kralik -

There are a couple Veeam KBs on this type of error, but not to your specific one you could look at to see if the steps in them resolve your issue. 

https://www.veeam.com/kb1174
https://www.veeam.com/kb2065

Otherwise as Chris shared, your best bet is to open a Veeam Support case.

Understood.

 

We have found also, that the Filesystem of the backup HDD should be really standard NTFS and not as Veeam requested (ReFS - 64KB), so the Results were today better.

 

And after reboot of all VMs, I think, the RPC Service has been also “renewed”. 

 

I am going to search further.

 

Thank you

Great to hear @Kralik 

Good to hear the news and results.

Hi @Kralik - just wanted to follow up on this post to see if you required any more help or assistance.  If you were able to find a resolution please post it here then mark it as best answer.  If any of the above suggestions helped then please mark that as best answer including your own if that is the case.  Let us know if we can assist further.

Comment


Terms & Conditions