Netbackup 4.5 
Solaris master/media server
Windows and solaris clients 

Our daily incrementals will sometimes just do nothing.
Job starts and connects.  12 hours later not a byte was written.
Cancel the job(s) and then the rest of the queued jobs start.
I can see this much from bperror.  Where should we look to find out why this
is happening?

============================================================================
Msvr:/usr/openv/netbackup/logs#bperror -U -jobid 129302
    TIME            SERVER/CLIENT                      TEXT
10/26/2005 19:02:46 Msvr Wsrv  added backup job (jobid=129302) for client
                    Wsrv, policy Win-Serv-Inc, schedule WinIncremental
                    part 3 to NetBackup scheduler work queue
10/26/2005 19:02:46 Msvr Wsrv  started backup job for client Wsrv,
                    policy Win-Serv-Inc, schedule WinIncremental on storage
                    unit Msvr-dlt3-robot-tld-0
10/26/2005 19:02:48 Msvr Wsrv  client Wsrv handling path P:\
10/26/2005 19:07:00 Msvrbk Wsrv  begin writing backup id
                    Wsrv_1130367768, copy 1, fragment 1, to media id
                    U00018 on drive index 1
10/27/2005 07:18:54 Msvrbk Wsrv  CLIENT Wsrv  POLICY Win-Serv-Inc 
                    SCHED WinIncremental  EXIT STATUS 150 (termination
                    requested by administrator)
10/27/2005 07:18:54 Msvrbk Wsrv  backup of client Wsrv exited with
                    status 150 (termination requested by administrator)
Msvr:/usr/openv/netbackup/logs#
============================================================================
=========