Invalid datastore path

KB ID:
1110
Product:
Veeam Backup & Replication
Version:
5.x
Published:
Last Modified:
2013-02-19

Challenge

A SureBackup/Instant Recovery session fails with the error "Unable to access the virtual machine configuration: Invalid datastore path"

[timestamp]          Getting virtual lab configuration
[timestamp]          Starting virtual lab routing engine
[timestamp]          Name: Publishing
[timestamp]          Name: Publishing (Backup creation point: 7/8/2011 7:36:12 PM, type: full)
[timestamp]          Name: Updating configuration

[timestamp]          Fail     Name: Registering
                               Unable to access the virtual machine configuration: Invalid datastore path 'netfs://192.168.27.23//VeeamBackup_Name/Name_fa8225689fd149fa84f2a65862487589/Name.vmx'.
[timestamp] PM Fail   
                               Unable to access the virtual machine configuration: Invalid datastore path 'netfs://192.168.27.23//VeeamBackup_Name/Name_fa8225689fd149fa84f2a65862487589/Name.vmx'.
[timestamp]          Sending email report
[timestamp]          server: Unregistering
[timestamp]         server: Cleaning up redo logs
[timestamp]          server: Unpublishing
[timestamp]          Stopping virtual lab routing engine
[timestamp]          Fail   
                               Unable to access the virtual machine configuration: Invalid datastore path 'netfs://192.168.27.23//VeeamBackup_Name/Name_fa8225689fd149fa84f2a65862487589/Name.vmx'.
[timestamp]          Job finished

 

Solution

To resolve:

1. Open the vSphere client directly to the host we are running Virtual Lab/Instant Recovery on
2. Click Configuration and Storage, and unmount the VeeamBackup_<Veeamserversname>
3. Then restart the management agents on this host
4. Reboot the Veeam server.

Rate the quality of this KB article: 
5 out of 5 based on 2 ratings

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:

Submit