Hello,
I am working on a small automation for VBR v13 and need to check capacity of Exagrid servers.
I can see in /api/v1/backupInfrastructure/repositories/states that ExaGrid is listed as a filterable repo type, but cant seem to make it load any values.
Am i missing something or is the implementation not finished yet ?
In VBR console they are listed normally within Backup Repositories, so i dont understand why they are not included in the base api call .
Thanks
-
Boriso
- Lurker
- Posts: 2
- Liked: never
- Joined: Feb 09, 2026 11:20 am
- Full Name: Boris Boris
- Contact:
-
Andreas Neufert
- VP, Product Management
- Posts: 7358
- Liked: 1584 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Exagrid capacity info via API
For us as application the available data on free space on a deduplication device is not an accurate rating and so we do not publish this information. You would need to go to the storage and check on the disk usage in the backend. The filesystem that we see are not reporting the actual free disk space as you can write many times more data then the available physical disk space because of the deduplication engine.
-
Boriso
- Lurker
- Posts: 2
- Liked: never
- Joined: Feb 09, 2026 11:20 am
- Full Name: Boris Boris
- Contact:
Re: Exagrid capacity info via API
@Andreas but you do collect it, its shown in the Backup repositories tab, so why not expose it ?
I understand the complexity of deduplication, but i need approximate value that you are already collecting.
I understand the complexity of deduplication, but i need approximate value that you are already collecting.
-
oleg.feoktistov
- Veeam Software
- Posts: 2044
- Liked: 687 times
- Joined: Sep 25, 2019 10:32 am
- Full Name: Oleg Feoktistov
- Contact:
Re: Exagrid capacity info via API
Hi,
Implementation for dedup appliances was not finished yet, but the fact that you see ExaGrid type in the available filters is the issue on our side.
Our plan is to add dedup repositories (including ExaGrid) in the next release, so at that point the approximation of their capacity should be available at /api/v1/backupInfrastructure/repositories/states endpoint as it is in the console UI.
Best regards,
Oleg
Implementation for dedup appliances was not finished yet, but the fact that you see ExaGrid type in the available filters is the issue on our side.
Our plan is to add dedup repositories (including ExaGrid) in the next release, so at that point the approximation of their capacity should be available at /api/v1/backupInfrastructure/repositories/states endpoint as it is in the console UI.
Best regards,
Oleg
Who is online
Users browsing this forum: No registered users and 1 guest