Using the latest VBR 11 build, I've been working with the API to pull some data centrally. I thought I'd provide some feedback of the hurdles I've come across.
I assume that potentially you are already aware of some of these pieces. But I know you appreciate feedback from the field. I'll continue adding to thread replies if I have any more feedback.
Code: Select all
- /api/v1/backupInfrastructure/repositories This call does not return cloud connect providers. It seems there is no backup infra API call that does. This call does not include the Scale Out Repos either. Which is ok, because there is another call further down. - /api/v1/backupInfrastructure/repositories/states This is the only way to get the repository capacity statistics, unlike other commands, which use an ID parameter to specify a particular object. You have to use a filter on this to return only a single repository. - /api/v1/backupInfrastructure/scaleOutRepositories There seems to no method to get the capacity data for the Scale-Out Repositories, it would be nice to be able to get this data. - /api/v1/sessions/:id If you need to get the running time, you will have to compute the difference between start and end time yourself. It would be nice if this can be part of the data set. There is no summary data for the data size for that backup. - /api/v1/sessions/:id/logs There is no summary data for the data size for that backup. Just the VM size in total. - /api/v1/backups/:id/objects This relies on the use of the backup ID which you get from the results of another API call. The response body here shows which VMs are included in this backup, but none of the key's link it back to the backup in question. So the only way to tie the backup response body (/api/v1/backups/:id) and the Backup Objects body response is via the API calls themselves, rather than within the data. It would be nice to have the backup ID in the BackupObject, so I can create a relationship between the two.