Hi all,
I upgraded my Veeam B&R v10 to v11 today.
I tried to restore guest file from any Linux virtual machine
and I received error:
Failed to mount restore point.
Could not find file c:\Program Files\Common Files\Veeam\Backup and Replication\Mount Service\VeeamAgent64
But restore guest file from any Windows virtual machine is OK.
Workaround:
Copy file VeeamAgent64 (as Administrator) from folder:
c:\Program Files\Veeam\Backup and Replication\Backup
to folder:
c:\Program Files\Common Files\Veeam\Backup and Replication\Mount Service\
I think that this problem is caused by bug in upgrade of v11...
-
- Influencer
- Posts: 11
- Liked: 3 times
- Joined: Jan 01, 2006 1:01 am
-
- Veteran
- Posts: 1143
- Liked: 302 times
- Joined: Apr 27, 2020 12:46 pm
- Full Name: Natalia Lupacheva
- Contact:
Re: Veeam B&R v11 restore error and workaround
Hi Vladimir,
Thank you for the detailed description of the issue. Passed this issue to QA and will come back to you when we get any news.
Thanks!
Thank you for the detailed description of the issue. Passed this issue to QA and will come back to you when we get any news.
Thanks!
-
- Veteran
- Posts: 1143
- Liked: 302 times
- Joined: Apr 27, 2020 12:46 pm
- Full Name: Natalia Lupacheva
- Contact:
Re: Veeam B&R v11 restore error and workaround
@vladimirh,
could you please open a support case and share its ID with us?
We have checked the issue on our side but couldn't reproduce it. The logs analysis is required here and that's why we need a Support case.
Thanks!
could you please open a support case and share its ID with us?
We have checked the issue on our side but couldn't reproduce it. The logs analysis is required here and that's why we need a Support case.
Thanks!
-
- VP, Product Management
- Posts: 6035
- Liked: 2860 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: Veeam B&R v11 restore error and workaround
I'm curious if you've attempted a reboot since the v11 upgrade completed. I had a similar issue with the upgrade in my lab, although in a different component.
After the upgrade if I attempted to import or update any Linux credential with that used an SSH private key, I would get an error and the logs indicated that it was looking for a file in a path where the file simply didn't exist and thus failing, however the file was available in another path.
I thought about manually moving the file to see what would happen, but as the upgrade did not prompt me to reboot my system, but rebooting is a common step after many upgrades, I decided to just try that first and indeed, after the reboot, the problem went away and the file was found in the correct location. If it just so happens you haven't rebooted since the upgrade, it might be worth a try.
After the upgrade if I attempted to import or update any Linux credential with that used an SSH private key, I would get an error and the logs indicated that it was looking for a file in a path where the file simply didn't exist and thus failing, however the file was available in another path.
I thought about manually moving the file to see what would happen, but as the upgrade did not prompt me to reboot my system, but rebooting is a common step after many upgrades, I decided to just try that first and indeed, after the reboot, the problem went away and the file was found in the correct location. If it just so happens you haven't rebooted since the upgrade, it might be worth a try.
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], Semrush [Bot] and 64 guests