Noticed this on a 740 that's only got 1 DLT. Veritas netbackup is scheduling bkp jobs with ndmp, from a sun box. There've been some odd failures where the tape fails to unload after the bkp, recently. ndmpd status doesn't show any sessions active when that happens though. Right now I'm seeing 2 ndmp sessions; I don't recall that before, and I'm wondering if this means netbackup is having problems. The ip addr is the sun box running nb, for both sessions; there's a bkp running while I'm looking at this. 6.1.3R2
statler> ndmpd status ndmpd ON. Session: 47 Active version: 2 Operating on behalf of primary host. tape device: nrst0a mover state: Idle data state: Idle data operation: None Session: 36 Active version: 2 Operating on behalf of primary host. tape device: not open mover state: Paused data state: Active data operation: Backup statler> sysstat 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 8% 16 0 0 465 10 0 27 0 442 >60 7% 38 0 0 466 47 35 0 0 438 >60 statler> ndmpd probe 47 ndmpd ON. Session: 47 isActive: TRUE protocol version: 2 effHost: Local authorized: TRUE client addr: 206.229.36.82:52341 spt.device_id: none spt.ha: -1 spt.scsi_id: -1 spt.scsi_lun: -1 tape.device: nrst0a tape.mode: Read/Write mover.state: Idle mover.mode: Read mover.pauseReason N/A mover.haltReason N/A mover.recordSize: 0 mover.recordNum: 0 mover.dataWritten: 0 mover.seekPosition: 0 mover.bytesLeftToRead: 0 mover.windowOffset: -1 mover.windowLength: -1 mover.position: 0 mover.connect.addr_type:LOCAL data.operation: None data.state: Idle data.haltReason: N/A data.connect.addr_type: LOCAL data.bytesProcessed: 0 statler> ndmpd probe 36 ndmpd ON. Session: 36 isActive: TRUE protocol version: 2 effHost: Local authorized: TRUE client addr: 206.229.36.82:51967 spt.device_id: none spt.ha: -1 spt.scsi_id: -1 spt.scsi_lun: -1 tape.device: not open tape.mode: Read only mover.state: Paused mover.mode: Read mover.pauseReason EOM mover.haltReason N/A mover.recordSize: 64512 mover.recordNum: 242736 mover.dataWritten: 15659384832 mover.seekPosition: 0 mover.bytesLeftToRead: 0 mover.windowOffset: -1 mover.windowLength: -1 mover.position: 0 mover.connect.addr_type:LOCAL data.operation: Backup data.state: Active data.haltReason: N/A data.connect.addr_type: LOCAL data.bytesProcessed: 15659709440 statler>
bash-2.03# bpps -a | grep stat root 3281 1 0 17:03:55 ? 12:39 bptm -w -pid 3273 -c statler -den 13 -rt 8 -rn 0 -stunit statler-dlt -cl statle root 3273 1 0 17:03:54 ? 0:00 bpbrm -backup -mt 3 -to 0 -S netback -c statler -hostname statler -ru root -cl bash-2.03#
-- Dave Toal Systems Architect Thomson & Thomson N. Quincy, MA
Toal, Dave wrote:
Noticed this on a 740 that's only got 1 DLT. Veritas netbackup is scheduling bkp jobs with ndmp, from a sun box. There've been some odd failures where the tape fails to unload after the bkp, recently. ndmpd status doesn't show any sessions active when that happens though. Right now I'm seeing 2 ndmp sessions; I don't recall that before, and I'm wondering if this means netbackup is having problems. The ip addr is the sun box running nb, for both sessions; there's a bkp running while I'm looking at this. 6.1.3R2
statler> ndmpd status ndmpd ON. Session: 47 Active version: 2 Operating on behalf of primary host. tape device: nrst0a mover state: Idle data state: Idle data operation: None Session: 36 Active version: 2 Operating on behalf of primary host. tape device: not open mover state: Paused data state: Active data operation: Backup statler> sysstat 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 8% 16 0 0 465 10 0 27 0 442 >60 7% 38 0 0 466 47 35 0 0 438 >60 statler> ndmpd probe 47 ndmpd ON. Session: 47 isActive: TRUE protocol version: 2 effHost: Local authorized: TRUE client addr: 206.229.36.82:52341 spt.device_id: none spt.ha: -1 spt.scsi_id: -1 spt.scsi_lun: -1 tape.device: nrst0a tape.mode: Read/Write mover.state: Idle mover.mode: Read mover.pauseReason N/A mover.haltReason N/A mover.recordSize: 0 mover.recordNum: 0 mover.dataWritten: 0 mover.seekPosition: 0 mover.bytesLeftToRead: 0 mover.windowOffset: -1 mover.windowLength: -1 mover.position: 0 mover.connect.addr_type:LOCAL data.operation: None data.state: Idle data.haltReason: N/A data.connect.addr_type: LOCAL data.bytesProcessed: 0 statler> ndmpd probe 36 ndmpd ON. Session: 36 isActive: TRUE protocol version: 2 effHost: Local authorized: TRUE client addr: 206.229.36.82:51967 spt.device_id: none spt.ha: -1 spt.scsi_id: -1 spt.scsi_lun: -1 tape.device: not open tape.mode: Read only mover.state: Paused mover.mode: Read mover.pauseReason EOM mover.haltReason N/A mover.recordSize: 64512 mover.recordNum: 242736 mover.dataWritten: 15659384832 mover.seekPosition: 0 mover.bytesLeftToRead: 0 mover.windowOffset: -1 mover.windowLength: -1 mover.position: 0 mover.connect.addr_type:LOCAL data.operation: Backup data.state: Active data.haltReason: N/A data.connect.addr_type: LOCAL data.bytesProcessed: 15659709440 statler>
bash-2.03# bpps -a | grep stat root 3281 1 0 17:03:55 ? 12:39 bptm -w -pid 3273 -c statler -den 13 -rt 8 -rn 0 -stunit statler-dlt -cl statle root 3273 1 0 17:03:54 ? 0:00 bpbrm -backup -mt 3 -to 0 -S netback -c statler -hostname statler -ru root -cl bash-2.03#
-- Dave Toal Systems Architect Thomson & Thomson N. Quincy, MA
It's all the way normal : one session is for the tape drive and the other for the arm of the robot. look for my output when I have two tape drives : << nac1> ndmpd status ndmpd ON. Session: 36 Active version: 4 Operating on behalf of primary host. tape device: nrst0a mover state: Idle data state: Idle data operation: None Session: 35 Active version: 4 Operating on behalf of primary host. tape device: nrst1a mover state: Idle data state: Idle data operation: None Session: 34 Active version: 4 Operating on behalf of primary host. tape device: not open mover state: Idle data state: Idle data operation: None
bye.