The veeam backup version is patched to 13.0.1.2067 after that few proxy servers are not getting updated.
Failed to upgrade host components. Error: 'The process cannot access the file because it is being used by another process. Failed to invoke rpc command (The process cannot access the file because it is being used by another process.) (Failed to invoke rpc command)' (0:00:10)
Best answer by Chris.Childerhose
Are there backup jobs running using the Proxies? If so, you might need to wait on them to finish. If that is not the case, try rebooting the proxies and upgrade again.
+21Are there backup jobs running using the Proxies? If so, you might need to wait on them to finish. If that is not the case, try rebooting the proxies and upgrade again.
+13Have you tried to reboot both the proxies and the VBR server? And are you using the VSA or VBR on Windows? And can you verify, that only one VBR server has access to all the components you have in use?
First option - if the reboot doesn’t help - is to open a Veeam support case to speed up the troubleshooting Once that is done, you can check the following in the meantime:
Did you make sure that you update all the firewall rules? With v13, a lot has changed there.
Did you check the required permissions of all service accounts in use?
Did you verify the compatibility of all components prior to upgrading? Especially with VSA you will not be able to work with Kerberos as you did before.
Please feel free to keep us posted on this!
+4yes - make sure no backups are running, try rebooting the proxies and backup server, also make sure the console isn’t open ..sometimes this will cause an issue.
+2Rebooting is solid advice, it won’t update locked files.
+21Great and glad to hear that fixed it. 😉
+4awesome! when all else fails reboot
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.