Direct SAN/NFS issue

[matteu]

Hello,

I have an issue and same for 2 collegues on differents clients with différent hardware to implement direct SAN.
On the proxy, if we select automatic detect datastore, it's not working and in the logs we can see something like : "LUN is not accessible" during rescan.
If we force datastore it's working.

Is there a difference between V11 and previous version during detection? We have this issue only since V11.
On Netapp storage and IBM or Huawei too.

Thanks

[foggy]

Do you have a case open for this? We'd like to take a look at the logs.

[restore-helper]

Had the same problem when we migrate from netapp FAS 8040 (ontap 9.7) to AFF250 (ontap 9.9).
Had to set the datastores to manually on the proxy otherwise it would fail over to NBD.
Sorry I have no case open, but at the moment there is no time for this. Might open a case in January.
Would be I terested to find out the source of the problem

[restore-helper]

Is the user may be talking about the same problem?
vmware-vsphere-f24/backup-using-hotadd- ... 78184.html

[rennerstefan]

Had to set the datastores to manually on the proxy otherwise it would fail over to NBD.

Hi,

What do you mean by saying you set it manually to the proxy? Are u talking about backup from storage snapshots or about direct San backup?
A case would be good indeed to better understand the behavior you see.

Thanks

[dasfliege]

Similar problem here. I've opened the thread which is linked above and am already working with veeam support since days. But it doesn't seem that veeam is aware that there may is a general issue.
Thanks for the hint that fixing the datastores in the proxy settings fixes the issue. Were you able to select multiple datastores, or is it only working if you select a single datastore?

[dasfliege]

Manually select the datastores (also multiple) fixes the problem. I've reported the findings to veeam support, so they can escalate the case and hopefully fix the bug.

[matteu]

Support case : 05151204

I don't use storage snapshot.
I mean about manual select production datastore.

[foggy]

Thanks for opening a case. Since there are already a few of you experiencing similar behavior it might be an issue on our side.

[restore-helper]

Hi,

What do you mean by saying you set it manually to the proxy?

I mean in the proxy settings select the datastores manually (all your NFS data stores). The default is automatically selection.

[matteu]

Hello, do you have some news about this issue ?

[ghaxians]

Hi,

Same issue with directSAN not being used in automatic mode (goes to NBD) unless we manually select/set the datastores.

Case is 05141657.

New logs should be added tomorrow morning, French time.

[foggy]

Hello Gilles, based on the provided logs, the issue is in Veeam B&R not being able to get info about the volumes on a proxy server during host discovery ('Access is denied' error). Support engineer will ask you for some additional troubleshooting and we are also reviewing other cases with similar symptoms. An ask for those who haven't yet opened a case - please do it.

[restore-helper]

Unfortunate time to ask for this, since I will be on vacation until 10.1. 2022 . But I can open a case then, if the problem is still not resolved.

[dasfliege]

Problem is not resolved yet, but as manually selecting the datastores is a decent workaround, this doesn't seem to have high priority at veeam.
I'm constantly testing stuff and provide fresh logs to support. As the issue is easily reproducable, i don't think that it should be too hard to find the root cause and solve it.

[foggy]

Logs do help but our engineers need to perform additional checks to track the issue down, please be patient. Thanks for your assistance with troubleshooting this.

[matteu]

thanks to keep us informed

[matteu]

Hello,
Is there some news about this issue ?
My collegue said me it's working with built in admin account but this is an other workaround.

[veremin]

Since you have a support ticket opened, it's better to request an update within it. We have an established procedure for working with the technical issues: logs -> support case -> escalation to the the different support tier -> escalation to the R&D (but only if the bug is confirmed and reproduced).

Kindly follow it, as this is not support forum and people behind it are not versed in reading logs or troubleshooting technical issues.

So I'm wondering whether there was a resolution provided by your support engineer? If not, you might want to escalate the case.

[matteu]

Sorry, I mean for other people with the same issue.

[foggy]

The issue seems to have different causes. In one of the cases, the root cause was the duplicated BIOS UUID in the database resulting in the wrong proxy selection. In another case, failover occurred due to the inability to successfully complete the Host Discovery session due to WinDefender activity locking the server. Please continue working with your engineer to track down the issue in your particular environment. Thanks!