Use vmphysinv to read recorded label, then create barcode generation rule accordingly and import it. You will have to delete current media record first before you import it back.
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.
http://support.veritas.com/docs/278893
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.
Alternatively, mchange -m -barcode " will to change the media id to match RVSN and not the barcode listed in the volume database. This manual update to the volume database will allow an import or other operation when the media ID and barcode are mismatched.
Other workaround is Import the tape using a standalone drive. This will not read the barcode on the tape, it will only read the recorded media ID. This will allow the Phase 1 import to complete successfully. Once the Phase 2 import of the tape is complete, duplicate the images to a different tape in the library. Once the images are duplicated, the previous tape can be expired and relabeled using the new barcode.
https://forums.symantec.com/syment/board/message?board.id=21&message.id=7823
