Disabling powershell throttling on VBR 13

[jasonede]

After just upgrading to VBR 13 I'm finding our powershell scripts are being throttled and I'm getting a TooManyRequests error. I'm sure I turned this off previously on ver 12 but can't find this in the documentation. How do I disable this throttling for local scripts?

[david.domask]

Hi jasonede,

I don't recall any specific throttling on Powershell in previous versions and haven't seen this in my testing in v13, so probably best to open a Support Case for this one. Please be sure to export logs and add them to the case. (export logs from the backup server itself please so we can get a full look at what's going on)

It's honestly not clear for me what would trigger this and quick check internally I don't see any known issues related to volume of operations from Powershell triggering this, so might be something else going on, but best to let Veeam Support review.

Please share your case number once created, thanks!

[jasonede]

Hi,

I've already opened a case Case # 07903356.

[llinasenc]

Hello,

jasonede, did you get any response?

I'm facing the same issue.

Regards,

[jasonede]

Not really. In the end I moved what I could to using the API. I didn't get an answer on the ticket as to what it was being throttled but as had a workaround left it for now. Had the same issue on 3 separate servers.

[david.domask]

@llinasenc, it would be great if you could open a case and include a copy of the script(s) you're running so we can better understand why the "TooManyRequests" response is being triggered.

@jasonede, as I see it from the case, the case had been escalated to our Advanced Support, but given the go-ahead to close as the issue seemed to subside.

Is the behavior still happening?

[jasonede]

David,

It was still happening, but we managed to work round it by moving our monitoring to JS using the API rather than powershell. It means we've lost the tape part of the monitoring at the moment, but we needed the monitoring working quickly and I didn't have time to investigate further. I'd got as far as working out when the script was scheduled and left to run then it ran initially, but then stopped after a while with that error. It also took quite a while (can't remember how long but several minutes at least) after reboots before it could be run as well.
I uploaded our script as part of the ticket. It wasn't very efficient at all and probably could be done a lot neater, but it was time to re-do it and the API (once I'd figured out what needed doing) is a lot better method for us as all the code sits on our monitoring server and so just one place to update