The only thing that is truly backup job independent and truly unique, even 
across servers, is the image id, and it's format is

clientname_successfulstarttime

We used job id for our reporting app, until we found out that:
a. jobid can easily become non-unique by overwriting the jobid file in 
/usr/openv/netbackup/db/jobs
b. jobid is definitely not unique across servers.

As long as you don't mix clientnames across servers, the above will be 
truly unique.  And even if you backed up the same client on two different 
servers, they would have to back up at EXACTLY the same time to make it 
non-unique.  To make it truly unique, you could combine it with master 
name, of course.

At 11:06 AM 5/25/2001 -0700, Fairchild, David wrote:
>Were building a reporting tool (For Netbackup 3.4) and need to know if JOB
>ID is unique. If not how often will it be repeated and what is the maximum
>number of characters we could expect? As of today they look unique, but
>would like to be certain.
>
>Thanks
>
>:::::::::::::::::::::::::::::::
>David Fairchild
>Enterprise Consulting Services
>First American Corporation
>(714)800-3027
>(714)235-5330
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

---
W. Curtis Preston
Principal Consultant for Storage Designs, your storage experts
Webmaster: http://www.backupcentral.com Phone: 760 631 7991