Hi everyone,
As is metioned elsewhere in this forum there will be an updated Version v13 to the VBR RestAPI and which is still in develpment, I'm putting together some features that I would like to see, perhaps others would like to add to the list.
Equal Representaion of both Agent Backup Jobs, vSphere Backup Jobs and Tape Jobs
1. Read the complete information in a job definition - For Dokumentation purposes
2. Status of a Job: running(Percentage commpleted, could be seperated in Task and Session, see below) , stopped, enabled, disabled, failed, warning, succesful
2a. Start a Job, (task)
2b. Get the Session ID from the Task ID after creating
2c Get Progress in Percentage from the Session
3. Get Job Logs (when completed)
4. Get Task Logs (when completed)
-
- Novice
- Posts: 5
- Liked: never
- Joined: Sep 04, 2016 9:14 am
- Full Name: Chris Matthews
- Contact:
-
- Veeam Software
- Posts: 2021
- Liked: 673 times
- Joined: Sep 25, 2019 10:32 am
- Full Name: Oleg Feoktistov
- Contact:
Re: Feature requests for the Backup Server API VBR v13
Hi Chris,
Let me first note that Tape jobs are not our priority in VBR REST for v13. Agent backup jobs are, though (managed by VBR). Now, to the points you outlined:
1.Could you please clarify what kind of information you seek a job definition to contain? Description of each property or else?
2. Already available. Adding agent backup jobs should automatically enable them to reflect all of these statuses/states.
2a. Not available for any job type, noted.
2b. If you mean getting parent session id when starting a job for a VM (task), it should automatically be available once starting a job for a VM (task) is implemented.
2c, 3 and 4. Already available. Should apply to agent backup jobs once implemented.
Best regards,
Oleg
Let me first note that Tape jobs are not our priority in VBR REST for v13. Agent backup jobs are, though (managed by VBR). Now, to the points you outlined:
1.Could you please clarify what kind of information you seek a job definition to contain? Description of each property or else?
2. Already available. Adding agent backup jobs should automatically enable them to reflect all of these statuses/states.
2a. Not available for any job type, noted.
2b. If you mean getting parent session id when starting a job for a VM (task), it should automatically be available once starting a job for a VM (task) is implemented.
2c, 3 and 4. Already available. Should apply to agent backup jobs once implemented.
Best regards,
Oleg
Who is online
Users browsing this forum: No registered users and 12 guests