Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to retrieve all backup data #2

Open
roymeister opened this issue Nov 20, 2017 · 2 comments
Open

Unable to retrieve all backup data #2

roymeister opened this issue Nov 20, 2017 · 2 comments

Comments

@roymeister
Copy link

Hi,

We are writing scripts to retrieve the backup space consumed per node in Unitrends backup for billing purposes.
Unfortunately we seem to be unable to get all usage data via the API, it only shows data for the last couple of days while we can see in Unitrends itself, there is data for more then a month.

We are calling the http://localhost/api/backups endpoint locally on the backup server. Is there a specific parameter we need to add in order to have it return all data?

@agonzalezm
Copy link
Contributor

You can use start_date to list backups older, try this:

http://localhost/api/backups/catalog/?sid=0&start_date=11/13/2015&end_date=11/20/2017

@polarpurple
Copy link

polarpurple commented Sep 11, 2019

http://localhost/api/backups/catalog gives me a catalog of available restore points, but seems to be limited to roughly 14 points per asset - even when in truth there could be hundreds more.

http://localhost/api/backups/catalog/?sid=0&start_date=11/13/2015&end_date=11/20/2044
Gives me an entirely different data structure that doesn't seem to be a list of restore points, but instead a job log. The events in this log stretch back to dates for which there is no available restore point.

I desperately need to list ALL of the available restore points for an asset. How do I accomplish this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants