Problem with media

[thanhtd]

While I backup to tape, I received a message the following below

10/27/2010 8:57:57 AM - granted resource A00142

10/27/2010 8:57:57 AM - granted resource HP.ULTRIUM4-SCSI.000

10/27/2010 8:57:57 AM - granted resource vblhosv96-hcart-robot-tld-0

10/27/2010 8:57:57 AM - estimated 0 Kbytes needed

10/27/2010 8:57:57 AM - started

10/27/2010 8:57:58 AM - started process bpbrm (512)

10/27/2010 8:58:03 AM - connecting

10/27/2010 8:58:06 AM - connected; connect time: 00:00:03

10/27/2010 8:58:09 AM - mounting A00142

10/27/2010 8:59:06 AM - mounted; mount time: 00:00:57

10/27/2010 8:59:11 AM - Error bptm(pid=5108) incorrect media found in drive index 0, expected A00142, found A00004, FREEZING A00142

10/27/2010 8:59:11 AM - current media A00142 complete, requesting next resource Any

10/27/2010 9:00:08 AM - granted resource A00141

Please the expert fix this problem for me ?

[Marianne]

Are you using a robot without a barcode reader or does it have a barcode reader but there are no barcoded labels on the tapes?

If anyone of the above is the case, you cannot perform a normal Inventory when you return tapes to the robot - NBU will add all the media as new media, but when the tape gets loaded in the drive, it finds the media-id that was previously assigned. It freezes the tape because of the mismatch.

You can unfreeze the media (bpmedia -unfreeze -m <id>) and then perform a physical inventory on the media in the robot.

NBU Admin Guide 1 explains the process under this heading:

Using the physical inventory utility
For the robots without barcode readers or that contain media without barcodes, the inventory reports only the presence of media in a robotic library. More detailed information is required to perform automated media management. You should use the the vmphyinv utility to inventory such robots. The vmphyinv physical inventory utility inventories nonbarcoded tape libraries as follows:
■ Mounts each tape
■ Reads the tape header
■ Identifies the tape in each slot
■ Updates the NetBackup volume configuration

(Please read the rest of this section in Admin Guide 1)

You did not mention your NBU version or O/S - please find Admin Guide 1 for your O/S:

All NBU 6.5 manuals: http://www.symantec.com/business/support/index?page=content&id=TECH52878

All NBU 7 manual: http://www.symantec.com/business/support/index?page=content&id=TECH126327

[Andy_Welburn]

Altho' unlikely, unless you are also experiencing other tape drive issues? (What NetBackup sees as one tape drive is actually another one as far as the OS is concerned.)

Have you made any changes recently?

Robtest commands that can be used to test the SCSI functionality of a robot
http://www.symantec.com/business/support/index?page=content&id=TECH83129

Snippet:

"...
The easiest way to see if your operating system and NetBackup are seeing the drives in the same way is to move a tape into a drive (for example, drive 1). Then look at the NetBackup Device Monitor to determine what drive number NetBackup sees the tape in. If the device monitor sees the tape as being something other than drive 1, change the Robot Drive Number of the drive in the NetBackup Media and Device Manager so that it matches the robotic drive number in which the robtest utility shows the tape. You will need to complete this step for every drive in the configuration.
..."

Also:

Steps to verify device configuration using robtest.
http://www.symantec.com/business/support/index?page=content&id=TECH29201

[Anton_Panyushki]

I think this sort of errors might be the outcome of tape library reconfiguration adding extra drives/library frames. Please try to inventory the robot in question. If that doesn't help you,  run device configuration wizard..

[thanhtd]

Hi Mariane Van den Berg

Tape library have barcode reader and barcode label on tape

Please view below

10/27/2010 8:57:57 AM - requesting resource vblhosv96-hcart-robot-tld-0

10/27/2010 8:57:57 AM - requesting resource vblhosv96.NBU_CLIENT.MAXJOBS.vblhosv76

10/27/2010 8:57:57 AM - requesting resource vblhosv96.NBU_POLICY.MAXJOBS.vblhosv76_FS_data

10/27/2010 8:57:57 AM - granted resource vblhosv96.NBU_CLIENT.MAXJOBS.vblhosv76

10/27/2010 8:57:57 AM - granted resource vblhosv96.NBU_POLICY.MAXJOBS.vblhosv76_FS_data

10/27/2010 8:57:57 AM - granted resource A00142

10/27/2010 8:57:57 AM - granted resource HP.ULTRIUM4-SCSI.000

10/27/2010 8:57:57 AM - granted resource vblhosv96-hcart-robot-tld-0

10/27/2010 8:57:57 AM - estimated 0 Kbytes needed

10/27/2010 8:57:57 AM - started

10/27/2010 8:57:58 AM - started process bpbrm (512)

10/27/2010 8:58:03 AM - connecting

10/27/2010 8:58:06 AM - connected; connect time: 00:00:03

10/27/2010 8:58:09 AM - mounting A00142

10/27/2010 8:59:06 AM - mounted; mount time: 00:00:57

10/27/2010 8:59:11 AM - Error bptm(pid=5108) incorrect media found in drive index 0, expected A00142, found A00004, FREEZING A00142

10/27/2010 8:59:11 AM - current media A00142 complete, requesting next resource Any

10/27/2010 9:00:08 AM - granted resource A00141

10/27/2010 9:00:08 AM - granted resource HP.ULTRIUM4-SCSI.000

10/27/2010 9:00:08 AM - granted resource vblhosv96-hcart-robot-tld-0

10/27/2010 9:00:09 AM - mounting A00141

10/27/2010 9:01:03 AM - mounted; mount time: 00:00:54

10/27/2010 9:01:08 AM - Error bptm(pid=5108) incorrect media found in drive index 0, expected A00141, found A00000, FREEZING A00141

10/27/2010 9:01:08 AM - current media A00141 complete, requesting next resource Any

10/27/2010 9:06:04 AM - granted resource A00131

10/27/2010 9:06:04 AM - granted resource HP.ULTRIUM4-SCSI.000

10/27/2010 9:06:04 AM - granted resource vblhosv96-hcart-robot-tld-0

10/27/2010 9:06:06 AM - mounting A00131

10/27/2010 9:07:00 AM - mounted; mount time: 00:00:54

10/27/2010 9:07:06 AM - positioning A00131 to file 1

10/27/2010 9:07:17 AM - positioned A00131; position time: 00:00:11

10/27/2010 9:07:17 AM - begin writing

10/27/2010 10:22:03 AM - end writing; write time: 01:14:46

the requested operation was successfully completed(0)

I don't know why, a few tape have error about media, While a few another tape still write data is ok.

[Gangadhar]

Try changing the media slot manually from tape library

[Andy_Welburn]

NB thinks is in the tape library slots.

Try re-inventorying the robot with update.

It is also possible that the library has lost track of what is where so may also be a good idea to power cycle the library also so that it can re-read its contents.

[Zahid_Haseeb]

What i face some time when the tape cartridge got corrupted OR tape cartridge life become complete the tapes thn getting freeze when we put them in the tape drives/Tape library.

Would you kindly share the bptm logs ?

[mph999]

Mariane is correct ...

10/27/2010 8:59:11 AM - Error bptm(pid=5108) incorrect media found in drive index 0, expected A00142, found A00004, FREEZING A00142

The library has loaded what it thinks is A00142.  When NBU reads the media header it finds it is tape A00004.

This could happen through various reasons, including :

(1)

The library is in fact loading the wrong tape.  I would recommend a power cycle of the library, allow it to inventory itself and then run a full inventory in NBU.

(2)

The tape was labelled bu NBU before a physical barcode label was attached.  The default barcodes if there is no physical barcode on the tape start with A00000 .  I see that the tapes you have issues with :

A00000

A00004

These are low numbers, so I suspect this is what has happened.

(3)

The barcode label has been swapped round.

Martin

[Marianne]

As Andy suggested, if there was a problem with device mapping at some point in time this could also happen.

If robot drive numbers were mapped to wrong O/S device names and two drives were loaded with new tapes at more or less the same time, the writing of the internal labels would have been swapped around....

What you need to do 1st is to power cycle the robot and run an Inventory. You now know that the robot and NBU agrees on external label and slot number.

Next, as Andy suggested, you have to verify the internal label.

Find in the Media GUI the slot number for media id A00142.

Open cmd and use robtest to move the tape into a drive. (See Andy's post for a detailed TN on robtest.) Say for example this tape is in slot 10.

In the cmd window, cd <install-path>\veritas\volmgr\bin

> robtest

(select robot number)

s s10                ### show slot number to ensure media id in slot

s d                   ### show drives to ensure drives are empty

m s10 d1         ### move tape in slot 10 to drive 1

############ wait for mount and 'tape ready'

Open another cmd and cd .....volmgr\bin

Check drive status with the following command

vmoprcmd -d ds

Let us know what the output is - we will take it from there....

In 1st cmd, unload tape and return to slot:

unload d1

###### wait for unload to complete

m d1 s10

q

q

REMEMBER that robtest will make robot unusable to normal NBU operations (like backups).

[thanhtd]

Hi all

Thanks everyone, I had fixed this problem.

[Andy_Welburn]

Don't keep it a secret, tell us how!

[Marianne]

Please tell us what the problem was and how it was solved - we need to know!

[thanhtd]

Hi all

I run a power cycle of the library, allow it to inventory itself and then run a full inventory in NBU.

Then, I right click on each tape, unfreeze it  and select label but not select " Verify media label before performing operation" to again labeling tape.

[Zahid_Haseeb]

thanhtd kindly mark the post as solution if your problem is resolved