We would not allow user to "start" a backup job when this job is running. (Stop this from our UI)
However, after we use "(POST) /jobs/{ID}?action=start" to start a job, we query by backupjobsession and find this job's status is "stopped".
Actually, query result only show previous backupjobsession's status. But EnterpriseManager's UI show current status "Starting" correctly.
I know "By default, Veeam Backup Enterprise Manager is configured to automatically collect data from added backup servers every 15 minutes.".
However, I start and query this job from EnterpriseManager. I think I should get query status "Starting" as EnterpriseManager's UI.
Or I should wait some seconds then I could get current status?
-
- Influencer
- Posts: 16
- Liked: never
- Joined: Jun 13, 2014 3:48 am
- Full Name: Cathy Hu
- Contact:
-
- Product Manager
- Posts: 20414
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: don't allow user to start a running backup job
Have you tried to query BackupTaskSessions, instead. Once you execute a job, you will see there sessions that correspond to VM(s) processed within a job. While running they will have a "InProgress" <State>, using which you can understand whether or not there are running jobs/tasks. Thanks.
Who is online
Users browsing this forum: No registered users and 2 guests