Forum Discussion

Mark_Hill's avatar
Mark_Hill
Level 4
18 years ago

Barcode and label problems on imported tapes...

Hey Guys, Im in the process of brining back in 110 tapes that didnt come over properly in our upgrade process to 6.0

Anyway, Im having trouble importing some of them:

21/03/2007 9:38:30 AM - Error bptm(pid=18525) Media mounted has media id of 2399L3, but 002399 was requested. Must add 2399L3 to Media Manager volume database and retry.
21/03/2007 9:38:30 AM - Error bpimport(pid=14921) Status = cannot perform specified media import operation.
21/03/2007 9:38:30 AM - end Import; elapsed time: 00:11:39
cannot perform specified media import operation(176)

When i go to use 2399L3 as the imported tape name, I get another box wanting to add another manual entry to the emm database.

Now I dont really want to go and have duplicate entries for when is essentially the same tape.

Anyone got any ideas on how I can solve this one and import the tape? DO I have to delete the emm db entry and create the new 2399L3 one?

Cheers
7.1.x and Earlier
Backup and Recovery
NetBackup
  • Rakesh_Khandelw's avatar
    Rakesh_Khandelw
    Level 6
    18 years ago
    Check your media ID generation rule. You may want to delete the current one or create a new one to match EVSN and RVSN of media IDs in question.

    STATUS CODE 176: An import of a media fails with "cannot perform specified media import operation" when importing a tape from a different VERITAS NetBackup (tm) environment with Media ID Generation rules in effect for either environment.

    Details:
    Overview:
    STATUS CODE 176: An import of a media fails with "cannot perform specified media import operation" when importing a tape from a different NetBackup environment, with Media ID Generation rules in effect for either environment.

    Troubleshooting:
    Examine if a Media ID Generation Rule is being used at either site for the applicable robots. If Media ID Generation settings differ between sites, NetBackup may inventory the media with a Media ID that is different than the actual recorded Media ID if that media is moved to another site. This is what causes the errors seen below. The media must have the same NetBackup Media ID at both sites.

    Examine Media ID Generation Rules by following these steps:
    1. Within the Windows NetBackup Administration Console, expand Media and Device Management in the left pane
    2. Right Click Media and select Inventory Robot to access the Robot Inventory Screen
    3. In the Advanced Options of the Robot Inventory screen, Click Media ID Generation

    Note: In earlier versions of NetBackup 4.5, the Media ID Generation rules are accessible directly from the Inventory Robot screen.


    Master Log Files:
    Import Log:
    9/7/2005 11:15:11 AM - begin Import operation
    9/7/2005 11:15:14 AM - started process bptm (1560)
    9/7/2005 11:15:14 AM - started process bptm (1560)
    9/7/2005 11:15:14 AM - mounting 000001
    9/7/2005 11:15:56 AM - Error bptm(pid=1560) Media mounted has media id of 0001L1, but 000001 was requested. Must add 0001L1 to Media Manager volume database and retry.
    9/7/2005 11:15:58 AM - Error bpimport(pid=3560) Status = cannot perform specified media import operation.
    9/7/2005 11:15:59 AM - end Import operation; operation time: 00:00:48
    cannot perform specified media import operation(176)

    Media Server Log Files:
    BPTM
    13:31:27.022 <16> load_media: Media mounted has media id of 0001L1, but 000001 was requested. Must add 0001L1 to Media Manager volume database and retry.
    13:31:27.037 <2> getsockconnected: host=tsbcka service=bpcd address=172.27.18.119 protocol=tcp reserved port=13782
    13:31:27.037 <2> getsockconnected: Connect to tsbcka on port 900
    13:31:27.037 <2> logconnections: BPCD CONNECT FROM 172.27.18.119.900 TO 172.27.18.119.13782
    13:31:27.162 <2> io_close: closing D:\Program Files\VERITAS\NetBackup\db\media\tpreq/000001, from .\bptm.c.13417
    13:31:27.162 <2> tpunmount: tpunmount'ing D:\Program Files\VERITAS\NetBackup\db\media\tpreq/000001
    13:31:27.272 <2> TpUnmountWrapper: SCSI RELEASE
    13:31:27.475 <2> bptm: EXITING with status 176 <----------


    Resolution:
    Perform the following steps on the site where the media are being imported:

    1. Within the Media section of the NetBackup Administration Console, delete the media in question that cannot be imported. This will allow the media to be re-inventoried properly.
    2. Change the Media ID Generation configuration (for the applicable robots) to match that of the other site. This may mean simply removing Media ID Generation rules temporarily, if they are not in use in the other NetBackup environment.
    3. Reinventory the media from step 1, using the "Update Volume Configuration" option
    4. Revert the Media ID Generation rule back to its former setting as needed. However, when media is imported from another site, this may need to be changed once again.

    With the media inventoried as the proper Media ID, the import should now proceed as expected.

    Caution: Always be sure that media is imported as soon as possible after inventory, so that it is not left unassigned and overwritten by a backup job.

    http://support.veritas.com/docs/278893
  • Rakesh_Khandelw's avatar
    Rakesh_Khandelw
    Level 6
    18 years ago
    STATUS CODE: 176: Unable to import media after a barcode change when using an ACS library. Veritas NetBackup (tm) automatically synchronizes the barcode to match the media ID.


    http://support.veritas.com/docs/279257
  • Gerald_W__Gitau's avatar
    Gerald_W__Gitau
    Level 6
    18 years ago
    Seems like you have media ID generation problems. You need to check that the Library can read extended bar code. What has happened here is Netbackup is reading the last 6 barcode characters i.e 2399L3 while you want it to read 002399.
     
    Goto media ID generation and click on new. Enter the robot number (e.g 0 or whatever it is). On bar code length enter 8. On media ID generation rule rule enter the following complete with the colons; 1:2:3:4:5:6
     
    This will force netbackup to read the media as 002399 and not 2399L3. Inventory the robot.
     
    I hope this helps.

    Message Edited by Gerald Wanjohi Gitau on 03-23-200710:37 AM

  • Yasuhisa_Ishika's avatar
    Yasuhisa_Ishika
    Level 6
    18 years ago
    Well, it seems that current config is right because requested media id is 002399.
    But media id written on media header is 2399L3. This volume was added and labeled without media id generation rule.
     
    Mark,
    To compele import, delete the volume 002399 and add it with media id 2399L3 anyhow(add manualy, temporary deletion of media id generation rule, or vmphyinv).

    Message Edited by Yasuhisa Itoh on 03-25-200711:26 PM