PowerShell Direct

[nmdange]

I have a few SQL VMs behind a firewall. I can see the following in the backup log:
4/13/2018 2:07:15 AM :: Failed to inject guest runtime using guest interaction proxy, failing over to PowerShell Direct

There's not much in the documentation about this functionality. Is there any reason why I would not want to use PowerShell Direct? Do I lose any functionality vs. placing a guest interaction proxy in the same subnet?

If there's no issue with PowerShell Direct, is there any way I can tell Veeam to use that first? I can't see anything related to PowerShell Direct in the backup job settings. It would be nice to tell Veeam not to try to use a proxy that I know won't work.

[veremin]

If I'm not mistaken, PowerShell Direct should be utilized, only when there is no network connection to backed up VM.

You won't lose anything, if you stick with network mode.

Check this article for more information.

Thanks.

[nmdange]

Right I'm just wondering if I can tell Veeam to use PowerShell Direct first so it doesn't try to connect and fail.

[veremin]

Add the following regkey and set it to 1:

Code: Select all

HvVssPowerShellDirectPriorityOverNetwork: <DWORD>

Thanks.

[nmdange]

I assume that is set on the Veeam server (what reg key path?) and then would apply to all VMs?

[veremin]

By default, all VB&R specific registry keys should be added in HKLM\SOFTWARE\VeeaM\Veeam Backup and Replication, unless otherwise is stated.

Correct, the order will be inversed for all VMs.

Thanks.

[TheOnlyWizard17]

Hi,

It would be nice if for Application-aware processing you could choose whether VBR should use/try Powershell Direct and/or Networking (\\<VM>\Admin$)...
Now, it always uses networking and only tries again using PoSh Direct if it's available... Since we lock down our VMs so "normally" VBR will be unable to do networking into the VM, it takes longer to next try PoSh and eventually succeed with that. Also, if you could choose which to try and in which order, you could speed up that trial and error-process per VM.

[HannesK]

Hello,
the choice is already available Please see the answer above

Best regards,
Hannes

[TheOnlyWizard17]

Hi Hannes, Veremin,

That's great !
Thanx...
Is there documentation somewhere where ALL Veeam registry-keys would be listed and documented what they do ? I've had many encounters with Veeam Support and some here on the forum where "unknown" registry-keys were the solution to an issue/feature request. That way we could first check that list if a solution is already available before going support/forum ?

[Gostev]

These forums are the best source. Just use search before you post

[StanoSedliak]

Is the powerShell direct working only with Windows OS or also with Linux please?
I found this:
https://bp.veeam.com/vbr/Support/S_Hype ... ction.html


But I didn't found any info in user guide about this limitation, do someone know how it is also for v12 and 11?
Actually I don't have any lab with hyper-v.

Thank you!

[PetrM]

Hi Stano,

Only Windows VMs, the requirement comes from PowerShell Direct itself, more info can be found here.

Thanks!