cancel
Showing results for 
Search instead for 
Did you mean: 

Strange jobid (#4294967295) not showing in GUI

robertojd
Level 2
Hello everyone, this is my first post here but I'm a long-time reader. You've helped me more than once without even knowing it, so thanks!

Now it's time to make all of you guys a question. We have an old NetBackup 5.1 master server on a Sun box (output from uname -a: SunOS master_server_name 5.8 Generic_117350-38 sun4u sparc SUNW,Sun-Fire) and since yesterday we've notice there's a job with jobid number 4294967295. This jobid doesn't show in the Java GUI though. I think this is the maximum value allowed for a backup jobid (a 32 bit value). But what does it mean?


This is the output I get from bpdbjobs:
$ bpdbjobs -report -most_columns | grep 4294967295
4294967295,,,,,,,,0000000000,0000000000,0000000000,,,,,,,0,,,,,,,,master_server_name,,,,0,0,0,0,,,,,,,,,,,,,,0,0,,,,,0,

(I'm changing the real name of this server to master_server_name due to information constraints).


This is the output for this jobid and the previous one from bpdbjobs:
$ bpdbjobs -jobid 4294967295
Segmentation Fault
$ bpdbjobs -jobid 4294967294
JobID State Stat Policy Schedule Client Dest Media Svr Started Elapsed
Segmentation Fault


So no output when specifying this number as a jobid. But when I do the same with bperror I get this output:
$ bperror -jobid 4294967295
1241448024 1 2 4 media_server_1 -1 0 0 *NULL* bptm successfully wrote 5 of 5 multiplexed backups, total Kbytes 387283 at 22751.909 Kbytes/sec
1241448264 1 2 4 media_server_2 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 32 at 4000.000 Kbytes/sec
1241448744 1 2 4 media_server_3 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 8176 at 22338.798 Kbytes/sec
1241448745 1 2 4 media_server_4 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 2752448 at 4246.248 Kbytes/sec
1241448839 1 2 4 media_server_5 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 23092014 at 28935.040 Kbytes/sec
1241448974 1 2 4 media_server_6 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 13985780 at 12397.224 Kbytes/sec
1241450289 1 2 4 media_server_7 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 12027469 at 4896.117 Kbytes/sec
1241455133 1 2 4 media_server_8 -1 0 0 *NULL* bptm successfully wrote 1 of 2 multiplexed backups, total Kbytes 48295768 at 6085.162 Kbytes/sec
1241457249 1 2 4 media_server_9 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 546828 at 4415.886 Kbytes/sec
1241460430 1 2 4 media_server_10 -1 0 0 *NULL* bptm successfully wrote 1 of 1 multiplexed backups, total Kbytes 100307689 at 8483.056 Kbytes/sec
[...]

And so on with similar lines. From date 1241448024 I know this thing started on Mon May 4 16:40:24 2009 (catalog's backup finished at 16:18:26, and next backup job started at 16:21:33, so I can't see if they're related or not. There are no jobs that started or finished at 16:40:24).

Does anyone know what kind of job/error is this? Any help that could point me to an explanation would be greatly appreciated.

Best regards,
Roberto.
2 REPLIES 2

Yasuhisa_Ishika
Level 6
Partner Accredited Certified
Job ID 4294967295 may be inadequate if you really run out job id number to 2^32.
It seems "bperror -jobid 4294967295" picks up log entry which jobid filed is "-1".
I recommend you to ignore this job and delete by "bpdbjobs -delete".
And check /usr/openv/netbackup/db/jobs/jobid. This file keeps last job id.

robertojd
Level 2
Thank you for your reply. This issue is really weird: the job had normally dissapeared due to log expiration and this morning I've found the exact same job while running a bpdbjobs report.