Veeam Explorer for MSSQL; Question to Veeam KB2284

[sandsturm]

there is a Veeam KB2284 (https://www.veeam.com/kb2284) which describes a problem with passing credentials during a DB restore with Veeam explorer for MSSQL. This KB exists since 2017 and I can't believe that we're the only company which has problems with this. On the one hand, its just tedious to always type in the credentials, on the other hand, we try to automate as many things as possible in our company and we can't do this automation for DB cloning or restore tests (via powershell) for example, because of this problem described in the KB. Is there any chance, that this will be solved in a future release?

thx a lot
sandsturm

[PetrM]

Hello,

Yes, the only available workaround now is to input credentials explicitly and there are no plans to change the behavior in future releases.

In most cases we prioritize features depending on number of similar requests, let's consider your question as +1 to implement it.

Thanks!

[LittleNickey]

We got the following error when we were going to restore a SQL database:

Access is denied: unable to pass current account's context to the mount server, please supply credentials and try again.

Just as outlined in KB2284 it works if we instead provide the same credentials instead of passing them using "Use current account".

According to the KB the cause is:

Veeam Explorer for Microsoft SQL Server is unable to pass/delegate the current user security token to a remote mount server.

However, I'd say that isn't the cause as much as it is the problem...
Does anyone have any insight in why this occurs? Is it a firewall issue? Credential multihop issue?

[HannesK]

Hello,
yes, that's known as issue 251944. Unfortunately, we have no timeline when this can be fixed.

Best regards,
Hannes

[LittleNickey]

Hello,

Yes, the only available workaround now is to input credentials explicitly and there are no plans to change the behavior in future releases.

In most cases we prioritize features depending on number of similar requests, let's consider your question as +1 to implement it.

Thanks!

@HannesK and @PetrM thanks for the reply and that it is a known issue. Do you have any insight into the root cause?

[PetrM]

Hello,

Basically, the main reason is the technical complexity of the fix which literally means to redesign the current architecture of solution. I think the closest explanation could be "credential multihop" issue. There is no problem to pass context directly from explorer to the local mount server just once but the chain of components becomes longer when the remote mount server comes into action: explorer -> local mount server -> Veeam B&R server -> remote mount server.

Thanks!