NetWorker Job Id

@KatH , That's a tough question. Why are you dependent on the jobID though ? If you want to store this in your DB as a primary key then just generate another unique ID instad and place that as a PK instead with the job id as one of the columns in there.

Of course, I can do that but introducing new Id will cost me a little bit more work with my loading process, and reports needs to be done for yesterday ;). Probably have no other option, because the rob retention time makes me feel the same Id may be used for new jobs in future.

As Crazyrov stated, in and by itself the JobID is meaningless once it has passed the jobsdb retention as you can't any longer reference it? However the information from the job in question still can be relevant, but you might wanna use different fields to make it unique, as there are the date/time of maybe even the nsavetime, which is the epoch time of a saveset.

But it all depends on what kind of information you even want to collect and retain?

You also prefer building and extracting something yourself instead of using the off the shelf Dell DPA solution (however still highly customizable reporting engine, consisting out of a DPA application server and a DPA datastore (the latter of which can even be clustered)), that comes free if you are using Dell DPS licensing, to report about Networker, Avamar and PPDM without needing additional licensing? As then you'd have already 1 year retention by itself, if memory serves me well for any backup meta data collected.

Can not reference it in jobsdb, but if I collect it in my RDBMS, will have the whole history since the first load time. I'm not NetWorker user, just BI engineer,  have no deep knowledge and understanding of NetWorker itself. I've got access to NEtworker REST API as a data source and need to provide numbers for failed and succeeded backups. I've concluded that I need to count save jobs to do that, but also need some data from workflow and backup jobs starting them, and they are related with job id (parent job id and root id). I have no nsavetime in rest api call result. 

As said, depending on the Dell data protection license used, you could freely use DPA instead to collect and report about all that information. Or the reporting from the NW NMC that also has reporting functionality.

Unless you have multiple data protection products and this one needs to be added as well? Or needs to be integrated into already existing data collection?

You might wanna dive deeper into the NW REST API for that, using the online Dell developer resources. As NW nowadays does not have pdf docs anymore stating how to use the NEW REST API but instead uses https://developer.dell.com/apis/2378/versions/v3/docs/GettingStarted.md.

Some references for NW (job) monitoring:
https://developer.dell.com/apis/2378/versions/v3/docs/examples/Example-8Monitoring.md

https://developer.dell.com/apis/2378/versions/v3/docs/examples/Example-9JobMonitoring.md

@barry_beckers , thank you a lot for all your advice and willingness to help! Not getting into the details - I had to use REST API as a data source and did it successfuly, though the architecture of my solution is not designen to handle ununique job ids, but I will keep on monitoring, and if it occurs, I already have some ideas how to handle it. Thank you once again!