Schedule issue

RESTful knowledge exchange

Schedule issue

Veeam Logoby sumwu » Sun Jan 18, 2015 5:49 am

We are using Veeam 7.0 yet we hit a problem using its API

From API, a Task ID is assigned to each job triggered by API call.
e.g. using API to edit the schedule of a VM, Task-ID 1 is assigned and the schedule is modified

However, when API calls the 101th time, Task-ID 101 is assigned and NO schedule is modified
Could anyone help?
sumwu
Veeam Software
 
Posts: 59
Liked: never
Joined: Tue Apr 02, 2013 7:55 am
Full Name: Sum Wu

Re: Schedule issue

Veeam Logoby v.Eremin » Mon Jan 19, 2015 9:55 am

As far as I remember, there used to be a sporadic problem in RESTful API with tasks starting from 100. However, if you follow the best practices and react promptly, closing tasks with delete request, you should not come across this issue. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Schedule issue

Veeam Logoby sumwu » Tue Jan 20, 2015 4:10 am

With your recommendation, we have tried this but the issue persists

For example,

When task ID is less than 100,
We used a POST to edit a job  we used DELETE to remove the task (as recommended); the job has been edited

When task ID is greater than 100,
We used a POST to edit a job  we used DELETE to remove the task (as recommended); the job has NOT been edited

Are these the correct steps?
sumwu
Veeam Software
 
Posts: 59
Liked: never
Joined: Tue Apr 02, 2013 7:55 am
Full Name: Sum Wu

Re: Schedule issue

Veeam Logoby v.Eremin » Tue Jan 20, 2015 8:48 am

The main idea was not to reach numbers bigger than 100 by closing tasks in appropriate fashion. Anyway, it might be worth updating to v8 first, as there are many RESTful API improvements and enhancements introduced in that version. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Schedule issue

Veeam Logoby Mardock » Thu Jan 22, 2015 10:38 am

Hi,
I have noticed the same issue with API v7.
I have upgraded to veeam API v8 but the issue never go away.

If I make DELETE request after Task has finished then the Task ID counter doesn't reset.
So when I reach a Task with an ID greater then 100 then the server response with a task that remains in the "running" state forever.

The only way to reset the task id counter is to reboot the veeeam API service.

Thanks,
Mardock.
Mardock
Influencer
 
Posts: 19
Liked: never
Joined: Thu Jul 10, 2014 3:40 pm

Re: Schedule issue

Veeam Logoby v.Eremin » Thu Jan 22, 2015 3:11 pm

I was slightly wrong when said that by closing tasks via delete request the counter should decrease. It's not the case.

Anyway, we've just checked the described behaviour and been unable to confirm the issue. So, please, open a ticket with our support team and provide its number here.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin


Return to RESTful API



Who is online

Users browsing this forum: No registered users and 3 guests