https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNDY2IiwiaGFzaCI6IjJhODRjY2VkLWYwMTQtNDhlYy05OWNjLTlmYjNkODMyNzU1YyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Backup Jobs fail after upgrade from ESX to ESXi

Challenge

After upgrading VMware servers, all backup jobs have the following error:

"Invalid SoapPath link: "/vmfs/volumes/YourPath" 'Text' is an invalid XmlNodeType."


Cause

The issue occurs because we are not able to use local storage on an ESXi server as the target for a repository because Windows cannot write to a VMFS volume.

Solution

You have a couple options.  You can still use local storage of the ESXi host for your backups but you have to do it at the OS level.  You would need to create a VMDK and attach it to a VM residing on that host and make the VMDK the size necessary to store your backups.  You can then create a Windows or Linux repository depending on the OS you are using, to write to that storage through the OS level.

More information

This is a common issue when upgrading from ESX 4.1 to ESXi 5.0. This can also occur when switching from any version of ESX to ESXi.
KB ID:
1466
Product:
Veeam Backup & Replication
Version:
5.x, 6.x
Published:
2011-12-27
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.