cancel
Showing results for 
Search instead for 
Did you mean: 

Pid

arjun7
Level 4

What is Pid ? how to see the Pid details? how Pids are useful while troubleshooting?

2 ACCEPTED SOLUTIONS

Accepted Solutions

Deb_Wilmot
Level 6
Employee Accredited Certified

Pids are Process ID's.

 

They're useful when troubleshooting because we know which process ID to look for in the log file as there may be hundreds/thousands of them.

 

You can view the pids by runnin the following:

  bpps -x (UNIX)

  bpps (Windows)

 

Example output UNIX:

Saber >> bpps -x
NB Processes
------------
    root   538     1   0   Dec 31 ?           0:05 /usr/openv/netbackup/bin/bpcd -standalone
    root   534     1   0   Dec 31 ?           0:03 /usr/openv/netbackup/bin/vnetd -standalone
    root   640     1   0   Dec 31 ?           2:30 /usr/openv/netbackup/bin/nbaudit
    root   771     1   0   Dec 31 ?           3:32 /usr/openv/netbackup/bin/nbstserv
    root   531     1   0   Dec 31 ?           0:30 /usr/openv/netbackup/bin/private/nbatd -c /usr/openv/var/global/vxss/eab/data
    root   841     1   0   Apr 02 ?           4:52 /usr/openv/netbackup/bin/nbars
    root   554     1   0   Dec 31 ?           3:38 /usr/openv/netbackup/bin/nbdisco
    root 29198   787   0 08:07:58 ?           0:05 /usr/openv/netbackup/bin/admincmd/bpstsinfo -DPSPROXY
    root   703     1   0   Dec 31 ?           0:00 /usr/openv/pdde/pdag/bin/mtstrmd
    root   618     1   0   Dec 31 ?          20:19 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
    root   630     1   0   Dec 31 ?           6:34 /usr/openv/netbackup/bin/nbevtmgr
    root   706     1   0   Dec 31 ?          22:52 /usr/openv/netbackup/bin/nbemm
    root   709     1   0   Dec 31 ?           2:40 /usr/openv/netbackup/bin/nbrb
    root   743   741   0   Dec 31 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbjm
    root   725     1   0   Dec 31 ?           1:15 /usr/openv/netbackup/bin/bprd
    root   731     1   0   Dec 31 ?           0:02 /usr/openv/netbackup/bin/bpcompatd
    root   752   749   0   Dec 31 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem
    root   749     1   0   Dec 31 ?           2:23 /usr/openv/netbackup/bin/nbpem
    root   741     1   0   Dec 31 ?           3:43 /usr/openv/netbackup/bin/nbjm
    root   746   745   0   Dec 31 ?           1:53 /usr/openv/netbackup/bin/bpjobd
    root   745     1   0   Dec 31 ?           0:05 /usr/openv/netbackup/bin/bpdbm
    root   930     1   0   Apr 02 ?           0:33 /usr/openv/netbackup/bin/nbvault
    root   860   749   0   Apr 02 ?           0:03 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup
    root   787     1   0   Apr 02 ?           5:17 /usr/openv/netbackup/bin/nbrmms
    root   838     1   0   Apr 02 ?           7:03 /usr/openv/netbackup/bin/nbim
    root   940     1   0   Apr 02 ?           1:01 /usr/openv/netbackup/bin/nbsvcmon
    root   828     1   0   Apr 02 ?           1:13 /usr/openv/netbackup/bin/nbsl
    root   933     1   0   Apr 02 ?           0:32 /usr/openv/netbackup/bin/nbcssc -a NetBackup
    root  1221   749   0   Apr 02 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
    root  1220   745   0   Apr 02 ?           0:04 /usr/openv/netbackup/bin/bpdbm


MM Processes
------------
    root   722     1   0   Dec 31 ?           0:26 vmd


Shared Symantec Processes
-------------------------
    root   528     1   0   Dec 31 ?           0:03 /opt/VRTSpbx/bin/pbx_exchange
Saber >>

The 2nd column from the right is the child, the 3rd column from the right is the parent.

Now Windows:

C:\Program Files\Veritas\NetBackup\bin>bpps
* NBMASTER1                                              4/06/14 09:19:24.176
COMMAND           PID      LOAD             TIME   MEM                  START
nbcssc           1168    0.000%           28.594   16M   3/03/14 09:30:50.807
bpcompatd        1200    0.000%           38.391   11M   3/03/14 09:30:52.414
spad             1420    0.000%         6:16.648   18M   3/03/14 09:31:13.864
spoold           1912    0.000%         5:54.621   89M   3/03/14 09:31:21.414
dbsrv11          1980    1.538%        23:34.258   34M   3/03/14 09:31:22.288
vnetd            3788    0.000%            7.519  6.6M   3/03/14 09:31:55.922
bpinetd          4296    0.000%            4.586  9.7M   3/03/14 09:32:09.556
bpcd             4364    0.000%           10.233  8.3M   3/03/14 09:32:11.038
NBConsole        5804    0.000%         1:06.066   53M   3/03/14 09:50:40.497
nbsl             4856    0.000%            1.045   28M   4/06/14 09:19:14.707
bmrd             4060    0.000%            0.109   14M   4/06/14 09:19:21.602
bmrbd            5060    3.077%            0.124   10M   4/06/14 09:19:22.366
.....[cut out the rest]

 

BTW - TID's are different.  They're thread ID's.  Multithreaded processes can have numerous threads associated with them.  Knowing the thread ID helps to follow the individual threads as lines right next to each other may not be associated with the same call.

 

I.e. here is an example of a TID (using vxlogview output):
11/05/13 00:20:13.351 [Application] NB 51216 nbpem 116 PID:753 TID:15 File ID:116 [jobid=664 job_group_id=664 client=abc123 type=4 server=saber task=ID:1015d7538 CTX:1015ac0a0 policy=abc123] [Error] V-116-85 backup of client abc123 exited with status 48 (client hostname could not be found)

In this case if I wanted to see what was going on with this call, I would follow TID 15.

The trouble shooting guide has more information on troubleshooting NetBackup.  Check out the 7.6 Guide as we've made a lot of improvements to it. :)

 

 

 

View solution in original post

Marianne
Level 6
Partner    VIP    Accredited Certified

Have a look at this definition: http://en.wikipedia.org/wiki/Process_ID 

It NBU terms, you may have more than one backup running on a media server at the same time. 
Each backup job will have its own bpbrm and bptm process on the media server. Same goes for all NBU processes on master, media server(s) and client(s).

NBU makes troubleshooting easier by adding PID for each job/stream in the log file. This means that when you troubleshoot a specific job, you only need to find the PID for that job in the log that you are looking at and ignore other PIDs. 

NBU makes it even easier by displaying PIDs for the different processes (e.g. bpbrm, bptm, bpbkar, etc) in Activity Monitor.

View solution in original post

4 REPLIES 4

Deb_Wilmot
Level 6
Employee Accredited Certified

Pids are Process ID's.

 

They're useful when troubleshooting because we know which process ID to look for in the log file as there may be hundreds/thousands of them.

 

You can view the pids by runnin the following:

  bpps -x (UNIX)

  bpps (Windows)

 

Example output UNIX:

Saber >> bpps -x
NB Processes
------------
    root   538     1   0   Dec 31 ?           0:05 /usr/openv/netbackup/bin/bpcd -standalone
    root   534     1   0   Dec 31 ?           0:03 /usr/openv/netbackup/bin/vnetd -standalone
    root   640     1   0   Dec 31 ?           2:30 /usr/openv/netbackup/bin/nbaudit
    root   771     1   0   Dec 31 ?           3:32 /usr/openv/netbackup/bin/nbstserv
    root   531     1   0   Dec 31 ?           0:30 /usr/openv/netbackup/bin/private/nbatd -c /usr/openv/var/global/vxss/eab/data
    root   841     1   0   Apr 02 ?           4:52 /usr/openv/netbackup/bin/nbars
    root   554     1   0   Dec 31 ?           3:38 /usr/openv/netbackup/bin/nbdisco
    root 29198   787   0 08:07:58 ?           0:05 /usr/openv/netbackup/bin/admincmd/bpstsinfo -DPSPROXY
    root   703     1   0   Dec 31 ?           0:00 /usr/openv/pdde/pdag/bin/mtstrmd
    root   618     1   0   Dec 31 ?          20:19 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
    root   630     1   0   Dec 31 ?           6:34 /usr/openv/netbackup/bin/nbevtmgr
    root   706     1   0   Dec 31 ?          22:52 /usr/openv/netbackup/bin/nbemm
    root   709     1   0   Dec 31 ?           2:40 /usr/openv/netbackup/bin/nbrb
    root   743   741   0   Dec 31 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbjm
    root   725     1   0   Dec 31 ?           1:15 /usr/openv/netbackup/bin/bprd
    root   731     1   0   Dec 31 ?           0:02 /usr/openv/netbackup/bin/bpcompatd
    root   752   749   0   Dec 31 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem
    root   749     1   0   Dec 31 ?           2:23 /usr/openv/netbackup/bin/nbpem
    root   741     1   0   Dec 31 ?           3:43 /usr/openv/netbackup/bin/nbjm
    root   746   745   0   Dec 31 ?           1:53 /usr/openv/netbackup/bin/bpjobd
    root   745     1   0   Dec 31 ?           0:05 /usr/openv/netbackup/bin/bpdbm
    root   930     1   0   Apr 02 ?           0:33 /usr/openv/netbackup/bin/nbvault
    root   860   749   0   Apr 02 ?           0:03 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup
    root   787     1   0   Apr 02 ?           5:17 /usr/openv/netbackup/bin/nbrmms
    root   838     1   0   Apr 02 ?           7:03 /usr/openv/netbackup/bin/nbim
    root   940     1   0   Apr 02 ?           1:01 /usr/openv/netbackup/bin/nbsvcmon
    root   828     1   0   Apr 02 ?           1:13 /usr/openv/netbackup/bin/nbsl
    root   933     1   0   Apr 02 ?           0:32 /usr/openv/netbackup/bin/nbcssc -a NetBackup
    root  1221   749   0   Apr 02 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
    root  1220   745   0   Apr 02 ?           0:04 /usr/openv/netbackup/bin/bpdbm


MM Processes
------------
    root   722     1   0   Dec 31 ?           0:26 vmd


Shared Symantec Processes
-------------------------
    root   528     1   0   Dec 31 ?           0:03 /opt/VRTSpbx/bin/pbx_exchange
Saber >>

The 2nd column from the right is the child, the 3rd column from the right is the parent.

Now Windows:

C:\Program Files\Veritas\NetBackup\bin>bpps
* NBMASTER1                                              4/06/14 09:19:24.176
COMMAND           PID      LOAD             TIME   MEM                  START
nbcssc           1168    0.000%           28.594   16M   3/03/14 09:30:50.807
bpcompatd        1200    0.000%           38.391   11M   3/03/14 09:30:52.414
spad             1420    0.000%         6:16.648   18M   3/03/14 09:31:13.864
spoold           1912    0.000%         5:54.621   89M   3/03/14 09:31:21.414
dbsrv11          1980    1.538%        23:34.258   34M   3/03/14 09:31:22.288
vnetd            3788    0.000%            7.519  6.6M   3/03/14 09:31:55.922
bpinetd          4296    0.000%            4.586  9.7M   3/03/14 09:32:09.556
bpcd             4364    0.000%           10.233  8.3M   3/03/14 09:32:11.038
NBConsole        5804    0.000%         1:06.066   53M   3/03/14 09:50:40.497
nbsl             4856    0.000%            1.045   28M   4/06/14 09:19:14.707
bmrd             4060    0.000%            0.109   14M   4/06/14 09:19:21.602
bmrbd            5060    3.077%            0.124   10M   4/06/14 09:19:22.366
.....[cut out the rest]

 

BTW - TID's are different.  They're thread ID's.  Multithreaded processes can have numerous threads associated with them.  Knowing the thread ID helps to follow the individual threads as lines right next to each other may not be associated with the same call.

 

I.e. here is an example of a TID (using vxlogview output):
11/05/13 00:20:13.351 [Application] NB 51216 nbpem 116 PID:753 TID:15 File ID:116 [jobid=664 job_group_id=664 client=abc123 type=4 server=saber task=ID:1015d7538 CTX:1015ac0a0 policy=abc123] [Error] V-116-85 backup of client abc123 exited with status 48 (client hostname could not be found)

In this case if I wanted to see what was going on with this call, I would follow TID 15.

The trouble shooting guide has more information on troubleshooting NetBackup.  Check out the 7.6 Guide as we've made a lot of improvements to it. :)

 

 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Have a look at this definition: http://en.wikipedia.org/wiki/Process_ID 

It NBU terms, you may have more than one backup running on a media server at the same time. 
Each backup job will have its own bpbrm and bptm process on the media server. Same goes for all NBU processes on master, media server(s) and client(s).

NBU makes troubleshooting easier by adding PID for each job/stream in the log file. This means that when you troubleshoot a specific job, you only need to find the PID for that job in the log that you are looking at and ignore other PIDs. 

NBU makes it even easier by displaying PIDs for the different processes (e.g. bpbrm, bptm, bpbkar, etc) in Activity Monitor.

arjun7
Level 4

thank you very much to all for explaian about Pids

Marianne
Level 6
Partner    VIP    Accredited Certified

If we have answered your question, please do not mark your own post as solution.

Please be kind enough to give credit where it's due - clear the solution for your own post, then select a post that has helped you and mark that as solution.

If more than one post has helped you, you can click on 'Request Split Solution'.