Hi,
I am looking for a way to set a timeout for the Find-VBRViEntity cmdlet, as it often gets stuck indefinitely.
I have attempted to use Start-Job and Wait-Job, but it appears that this cmdlet does not function well with these methods.
Do you have any suggestions for implementing a timeout for this cmdlet?
Thanks!
-
jcolonfzenpr
- Enthusiast
- Posts: 55
- Liked: 33 times
- Joined: Dec 30, 2021 1:16 am
- Full Name: Jonathan Colon
- Location: Puerto Rico
- Contact:
Find-VBRViEntity timeout support?
Jonathan Colon
https://techmyth.blog/
https://techmyth.blog/
-
jcolonfzenpr
- Enthusiast
- Posts: 55
- Liked: 33 times
- Joined: Dec 30, 2021 1:16 am
- Full Name: Jonathan Colon
- Location: Puerto Rico
- Contact:
Re: Find-VBRViEntity timeout support?
Using a runspace was the only approach that worked.
https://github.com/AsBuiltReport/AsBuil ... .ps1#L1033
Thanks!
https://github.com/AsBuiltReport/AsBuil ... .ps1#L1033
Thanks!
Jonathan Colon
https://techmyth.blog/
https://techmyth.blog/
-
david.domask
- Veeam Software
- Posts: 3143
- Liked: 720 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Find-VBRViEntity timeout support?
Hi Jonathan,
No built-in way of setting a timeout, so use runspace like you're doing, it will be the best option right now.
Out of curiosity, is this happening only with very large VMware environments or you see it even with fairly small environments? ( < 1000 VMs)
Similarly, does it happen with every Find-VBRViEntity parameter or only ones that may return many results like -VmsAndTemplates?
No built-in way of setting a timeout, so use runspace like you're doing, it will be the best option right now.
Out of curiosity, is this happening only with very large VMware environments or you see it even with fairly small environments? ( < 1000 VMs)
Similarly, does it happen with every Find-VBRViEntity parameter or only ones that may return many results like -VmsAndTemplates?
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: No registered users and 1 guest