praecorloth
Contributor
- Joined
- Jun 2, 2011
- Messages
- 159
Hello,
I'm trying to work with the FreeNAS API to monitor my snapshots. The test system, a 9.10.2-U5 machine, has almost 2500 snapshots. But the API only returns about 19 snapshots. And not from the beginning or end of the list of snapshots (assuming the list is generated using zfs list -t snapshot), but from a section in the middle of all of the snapshots.
I am doing something wonky here in that I have a non-FreeNAS machine replicating to this FreeNAS machine. The snapshots that are returned are not FreeNAS snapshots, which is fine, as I want to see all of the snapshots. But there are plenty more FreeNAS and non-FreeNAS snapshots to be had.
I'm in the process of spinning up another test environment that will just do FreeNAS to FreeNAS snapshots and replication, just to rule out these other snapshots as being a problem. But I thought I'd post here to see if anyone else has run into this or similar issue with the API.
The data was pulled from the API using Python 3, as well as just hitting up the storage/snapshot end point in a web browser (Chrome, Chromium, and Firefox).
I'm trying to work with the FreeNAS API to monitor my snapshots. The test system, a 9.10.2-U5 machine, has almost 2500 snapshots. But the API only returns about 19 snapshots. And not from the beginning or end of the list of snapshots (assuming the list is generated using zfs list -t snapshot), but from a section in the middle of all of the snapshots.
I am doing something wonky here in that I have a non-FreeNAS machine replicating to this FreeNAS machine. The snapshots that are returned are not FreeNAS snapshots, which is fine, as I want to see all of the snapshots. But there are plenty more FreeNAS and non-FreeNAS snapshots to be had.
I'm in the process of spinning up another test environment that will just do FreeNAS to FreeNAS snapshots and replication, just to rule out these other snapshots as being a problem. But I thought I'd post here to see if anyone else has run into this or similar issue with the API.
The data was pulled from the API using Python 3, as well as just hitting up the storage/snapshot end point in a web browser (Chrome, Chromium, and Firefox).