Skip to main content

This is the data shown in VSPC → Protected Data → Computers → Managed by Backup Server.

Maybe I’m missing something obvious.

/protectedWorkloads/virtualMachines = on-prem virtual machines (vSphere, Hyper-V, AHV, oVirt, Promox)
/protectedWorkloads/publicCloud/virtualMachines = cloud virtual machines (AWS, Azure, GCP)
/infrastructure/backupAgents = agents managed by console
 

Best place you can look is here for the API reference - Veeam Service Provider Console REST API Reference


Thanks Chris, already combed that from cover to cover. That’s where I got the other endpoints from. 😥


Sounds good.  Don’t use the API myself so cannot point you in the right direction.  Maybe check the forums to see if there are any posts there or get in touch with support.

Forums - https://forums.veeam.com

 


@ianm , 

 

Doesn’t https://helpcenter.veeam.com/docs/vac/rest/reference/vspc-rest.html?ver=9#tag/Backup-Agents 

do what you need? Can you explain what’s missing a bit more clearly?


Endpoint /infrastructure/backupAgents just brings back computers with agents managed by the VSPC itself. Or at least it does for me, ie. I see the same list as the VSPC provides in Protected Data → Computers → Managed by Console.

I want the information in Protected Data → Computers → Managed by Backup Server.

 


Got it, thanks for clarifying -- I’m not expert on VSPC API as I don’t work with VSPC much, but I think the endpoint you need is further down:

 

https://helpcenter.veeam.com/docs/vac/rest/reference/vspc-rest.html?ver=9#tag/Protected-Workloads/operation/GetProtectedComputersManagedByBackupServer

Looks like there’s a separate set of endpoints for ‘Managed by Backup Server’

 


Sweet, how did I miss that!


Well, I missed it too at first blush :)

Hope it works out well for you, and I think more than anything we can take some steps to improve discoverability in our API reference docs (search is pretty good, but have some ideas on how we could allow for natural discovery better)


Great to see that screenshot as we use VSPC but I have not explored the API much.  Hopefully this fixes your issue Ian.