cancel
Showing results for 
Search instead for 
Did you mean: 

Error bptm (pid=28619) error requesting media, TpErrno = Robot operation failed

poloc
Not applicable

hello,

 

I am using NBU 6.5.2. The master server hosts on Solaris machine.

 

The backup jobs are running correctly.

But when i tried to launch a clean job (through NBU GUI), i have had the following error:

"Error bptm (pid=28619) error requesting media, TpErrno = Robot operation failed"

 

Any idea to help me?

Note i see the cleaning tape is registered in the volume repository.

Bar code: CLN001S, media type: DLT_CLN, media id: LN001S

 

By advance, thanks for your feedback, Paul

6 REPLIES 6

RonCaplinger
Level 6

Check the Media and Device Management window in the NBU GUI:

Under Device Monitor, what type of drives are you using: DLT, DLT2, HCART, etc.?  If you clening tape is defined as DLT, but your tape drives are defined as HCART or DLT2 or anything other than DLT, you might get this message, along with some others that would indicate the mismatch.

You might also have no cleanings left on the cleaning cartridge.  Most should be or are limited to about 25 cleanings before they should be replaced.  Check the "Media" section of the GUI and locate the clenaing tape.  Then find th column "Cleanings Remaining".  If that is blank or 0, and this is not a new tape, you need to replace it.

Pedro_Alvarez
Level 2
Certified

Hello i almost have the Same problem this is the Job Detailed Log 

 

05/27/2011 10:33:02 - requesting resource telsap01-hcart3-robot-tld-1
05/27/2011 10:33:02 - requesting resource telsap07.NBU_CLIENT.MAXJOBS.telsap01
05/27/2011 10:33:02 - requesting resource telsap07.NBU_POLICY.MAXJOBS.ARCHIVES_DT_DB_DIARIO
05/27/2011 10:33:04 - granted resource telsap07.NBU_CLIENT.MAXJOBS.telsap01
05/27/2011 10:33:04 - granted resource telsap07.NBU_POLICY.MAXJOBS.ARCHIVES_DT_DB_DIARIO
05/27/2011 10:33:04 - granted resource SAY048
05/27/2011 10:33:04 - granted resource HP.ULTRIUM3-SCSI.002
05/27/2011 10:33:04 - granted resource telsap01-hcart3-robot-tld-1
05/27/2011 10:33:08 - started process bpbrm (pid=23942)
05/27/2011 10:33:08 - connecting
05/27/2011 10:33:09 - connected; connect time: 0:00:00
05/27/2011 10:33:13 - mounting SAY048
05/27/2011 12:10:42 - Error bptm (pid=23948) error requesting media, TpErrno = Robot operation failed
05/27/2011 12:12:03 - Warning bptm (pid=23948) media id SAY048 load operation reported an error
05/27/2011 10:40:29 - current media SAY048 complete, requesting next media Any
 
any idea where the problem is..... I have a Netbackup 6.0 Installed on a Sun Fire V240 Whit Solaris 9 
whit 118558-14 patch release 
 
Here some part of the bptm logs
 
06:09:38.868 [9712] <2> Human Message: Optional VxSS libraries not initialized. 
06:09:38.868 [9712] <2> VssCleanUp: vss_auth.cpp.854: Function: VssCleanUp result: 21
06:09:38.968 [9712] <2> bptm: EXITING with status 0 <----------
06:15:57.737 [9960] <2> bptm: INITIATING (VERBOSE = 0): -unload -dn HP.ULTRIUM3-SCSI.002 -dp /dev/rmt/1cbn -dk 2000016 -m SAY012 -mk
 4000521 -mds 8 -alocid 72022 -jobid -1306451016 -jm 
06:15:57.745 [9960] <2> bptm: EMMserver_name = telsap07
06:15:57.745 [9960] <2> bptm: EMMserver_port = 1556
06:15:57.745 [9960] <2> send_brm_msg: PID of bpxm = 9960
06:15:57.746 [9960] <2> nbjm_media_request: Passing job control to NBJM, type UNLOAD
06:15:57.750 [9960] <2> VssGetFQDNHostName: vss_auth.cpp.3997: Function: VssGetFQDNHostName. Search name 
06:15:57.750 [9960] <2> VssInit: vss_auth.cpp.716: Function: VssInit. Using Cached entries FALSE
06:15:57.751 [9960] <2> Human Message: Optional VxSS libraries not initialized. 
06:15:57.751 [9960] <2> VssCleanUp: vss_auth.cpp.854: Function: VssCleanUp result: 21
06:15:57.757 [9960] <2> taolog: can't register signal handler
06:15:59.862 [9960] <2> RequestMultipleResources: returning
06:15:59.862 [9960] <2> parse_resource_strings: MEDIADB 1 72022 SAY012 4000521 ------ 20 1306494442 0 0 0 0 0 0 4 90 0 16 1024 0 0 0
06:15:59.862 [9960] <2> parse_resource_strings: Parsed message type 15, version 1, 21 parameters
06:15:59.862 [9960] <2> parse_resource_strings: VOLUME 1 SAY012 4000521 SAY012 BD_TELSAP1_Y_2_RMAN HP F68IQ3H679 24 8 1 3 0 {0000000
0-0000-0000-0000-000000000000} 0
06:15:59.862 [9960] <2> parse_resource_strings: Parsed message type 16, version 1, 14 parameters
06:15:59.862 [9960] <2> parse_resource_strings: DRIVE 2 HP.ULTRIUM3-SCSI.002 2000016 MXP07081VR /dev/rmt/1cbn -1 -1 -1 -1 0 0 0 0 *N
ULL* *NULL* *NULL* *NULL* 1 0
06:15:59.862 [9960] <2> parse_resource_strings: Parsed message type 17, version 2, 19 parameters
06:15:59.862 [9960] <2> parse_resource_strings: STORAGE 0 *NULL* 0 0
06:15:59.862 [9960] <2> parse_resource_strings: Parsed message type 18, version 0, 4 parameters
06:15:59.862 [9960] <2> nbjm_media_request: Job control returned to BPTM
06:15:59.862 [9960] <2> drivename_open: Called with Create 1, file HP.ULTRIUM3-SCSI.002
06:15:59.863 [9960] <2> drivename_lock: lock established
06:15:59.863 [9960] <4> create_tpreq_file: symlink to path /dev/rmt/1cbn
06:15:59.873 [9960] <2> drivename_write: Called with mode 2
06:15:59.879 [9960] <2> process_tapealert: TapeAlert returned 0x00000000 0x00000000 (from tapealert_and_release)
06:15:59.879 [9960] <2> really_tpunmount: tpunmount'ing /usr/openv/netbackup/db/media/tpreq/drive_HP.ULTRIUM3-SCSI.002
06:16:33.316 [9960] <4> create_tpreq_file: symlink to path /dev/rmt/1cbn
06:16:33.332 [9960] <2> process_tapealert: TapeAlert returned 0x00000000 0x00000000 (from tapealert_and_release)
06:16:33.334 [9960] <2> tapealert_and_release: SCSI RELEASE
06:16:33.334 [9960] <2> drivename_unlock: unlocked
06:16:33.334 [9960] <2> drivename_close: Called
 
i will apreciate your help 
 
Best Regards 

RonCaplinger
Level 6

If I am reading this correctly, you are getting a TapeAlert of 0x0000000.  Based on what I read in this post, the TapeAlert flag is actually an 8.

Based on this article, TapeAlert 8 means "Not Data Grade", meaning that a cleaning tape was mounted instead of a data tape.  Is SAY012 supposed to be a data tape or a cleaning tape?

MamaCeceTram
Level 3

I am experiencing the similar error message. Can anyone give advice?

Jun 28, 2011 8:11:02 PM - Error bptm (pid=3800) error requesting media, TpErrno = Robot operation failed
Jun 28, 2011 8:11:03 PM - Warning bptm (pid=3800) media id T01468 load operation reported an error
Jun 28, 2011 8:08:08 PM - current media T01468 complete, requesting next media Any
Jun 28, 2011 8:08:27 PM - current media -- complete, awaiting next media Any. Waiting for resources.
          Reason: Drives are in use, Media server: tck_backup03.hlsc,
          Robot Type(Number): TLD(0), Media ID: N/A, Drive Name: N/A,
          Volume Pool: TCK-SL500, Storage Unit: tck_backup03-hcart3-robot-tld-0, Drive Scan Host: N/A,
          Disk Pool: N/A, Disk Volume: N/A
Jun 28, 2011 9:37:24 PM - Waiting for scan drive stop HP.ULTRIUM3-SCSI.003, Media server: tck_backup03.hlsc
Jun 28, 2011 9:46:07 PM - Waiting for scan drive stop HP.ULTRIUM3-SCSI.003, Media server: tck_backup03.hlsc
Jun 28, 2011 9:56:07 PM - Waiting for scan drive stop HP.ULTRIUM3-SCSI.003, Media server: tck_backup03.hlsc
Jun 28, 2011 10:01:08 PM - Waiting for scan drive stop HP.ULTRIUM3-SCSI.003, Media server: tck_backup03.hlsc
Jun 28, 2011 10:07:11 PM - Waiting for scan drive stop HP.ULTRIUM3-SCSI.003, Media server: tck_backup03.hlsc
Jun 28, 2011 10:11:17 PM - end writing
An extended error status has been encountered, check detailed status  (252)

sarsingh
Level 4

do you have correct media labels configured

MamaCeceTram
Level 3

smileyAfter we had the vendor come out and replace several drives we have not encounter any further tape issues. Thanks for everyone feedback. Att least mey issue is!