Instant Recovery fails at power on

[acoromi]

Hi.

I have a Windows XP VM backup. I can restore the backup normally, and the VM powers on with absolutely no issues. But when i want to test the backup doing an Instant Recovery, the job holds several minutes on the step "Registering VM" and finally stops with an error saying that Cannot power on the VM.

At the vCenter side, it reports this:

Failed to power on vm
Unable to retrieve the current working directory: 9 (Bad file descriptor). Check if the directory has been deleted or unmounted.


Any ideas?

Thanks.
Amado.

[Gostev]

Hello, this is not a known issue and it was not reported before. Please submit full logs to our support for investigation, as explained when you click New Topic. Thanks.

[acoromi]

Just isolated the issue. It's very strange.

It happens when the vPowerNFS is located on no-local hard disk. When a local hard disk (C:) is used, all runs perfect.

I have a iSCSI Lun presented to the Veeam server as F: drive letter. This drive runs smoothly, with no problems at all: you can read, copy, create files, etc.
But if i set "F:" as the vPower NFS destination, vCenter can't power on the VM, displaying that error.

Is this normal? Maybe vPower NFS ONLY runs on local storage??

Thanks!

Amado.

[Gostev]

No, it should be fine using iSCSI LUN as well. This is no different from local drive from OS/application perspective, unless this LUN has some issues with certain operations that you cannot perform with Windows Explorer. If you'd like us to investigate this, please send fulll logs to our support. Thanks!

[Alexey D.]

By the way, can you create a VM on that storage using vSphere client?

[Gostev]

From what is written above I assume Amado is talking about NTFS LUN attached to Veeam Backup server.

[acoromi]

Yes

[acoromi]

Well, finally i get the issue fixed. I think it could be considered a bug. Let me explain.

If i set "F:\" as a vPower NFS destination, the error shows up. But if i set "F:\any_directory", then all runs perfect!.

Well i write this here to help anybody with the same issue.

Thanks to all.

Amado.

[Gostev]

Thanks for this information, Amado!

[cnicholson]

I'm having this same problem on our Veeam 5 server (D:\ set for the vPowerNFS dir, UNC server for backup dest, so that's not related), where do I change this?

[Gostev]

In setup, or in the corresponding registry value under Veeam Backup & Replication registry key... don't forget to restart Veeam vPower NFS service after changing the value.

[real_tarantoga]

If I set "F:\" as a vPower NFS destination, the error shows up. But if i set "F:\any_directory", then all runs perfect!.

Thank You Amado! I have just run into the same problem.

... don't forget to restart Veeam vPower NFS service after changing the value.

As the registry key lies in the HKLM hive, a simple service restart wouldn't work?! I can't verify this - I have just rebooted the server.

Together with the replication option, there are good choices for different ways securing our uptime critical virtual servers!

Thanks for that!
Stefan

[Alexey D.]

As the registry key lies in the HKLM hive, a simple service restart wouldn't work?!

Stefan, restarting the service should be sufficient.

[Fiskepudding]

Just wanted to chip in that we have the same problem. Running v 6.0.0.181

It worked fine until i changed the vPower NFS location to another root drive.
Instant recovered VM failed at power on.

As stated by acoromi, creating anny subfolder and pointing to that solved this issue.

Mabye somthing to put on a fixlist?

Thanx acoromi

[foggy]

Espen, this is already on the list and will be addressed in one of the future updates. Thanks.