- Service Provider
- Posts: 41
- Liked: 6 times
- Joined: Jun 10, 2019 12:19 pm
- Full Name: Daniel Johansson
PS C:\Scripts> Get-VBOEntityData -type Site -Repository $repo
Get-VBOEntityData : This request operation sent to net.tcp://127.0.0.1:9191/Repository did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
At line:1 char:1
+ Get-VBOEntityData -type Site -Repository $repo
+ CategoryInfo : NotSpecified: (:) [Get-VBOEntityData], TimeoutException
+ FullyQualifiedErrorId : System.TimeoutException,Veeam.Archiver.PowerShell.Cmdlets.DataManagement.GetVBOEntityData
There should be less than 350 sites in the Sharepoint backup in that repository, and the total size of the repository is around 2 TB. The server was idle before doing this query. Querying for users on that server/repo work fine (400 users). On another VBO server I get random timeouts both querying for sites (around 400) and users (around 250), one time it works and the next it times out. That server was idle too. Both servers have a single organization and the repositories are on SMB shares. The shares are on the same fileserver, but I don't think the problem is in that end. There is no shortage of bandwidth or other resources. On the VBO vms the CPU consumption of Veeam.Archive.Proxy goes up quite a bit when running these queries, up to 40-50% typically, then stays there for a while (a few minutes) even after the query has errored out. It all seems rather random.
Would it be possible to raise the 60 second timeout or make it configurable? Or is there some better solution? We really need to get this working to get billing data. Can we check directly in the repo databases somehow?
- Veeam Software
- Posts: 3317
- Liked: 665 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
You should be able to add the following, where 600 defines the timeout (in this case 10 minutes). Keep in mind, to change this, you need to shut down all VBO365 services, change the value and start them again.
Code: Select all
<Veeam> <Archiver> .... <WCF OperationTimeout="600" /> .... </Archiver> </Veeam>
Veeam Certified Architect (VMCA)
- Product Manager
- Posts: 6047
- Liked: 697 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
PowerShell and REST API calls are done against the VBO controller so it should be enough on the controller only as far as I recall
Users browsing this forum: No registered users and 1 guest