Please enter search query.
Search <product_name> all support & community content...
Article: 100019078
Last Published: 2009-01-26
Ratings: 0 0
Product(s): NetBackup & Alta Data Protection
Problem
LTO media is frozen the second time it is used. A "Medium Identifiers" error is reported.Error Message
io_open: FREEZING media id 0182L1, Medium identifiers do not matchSolution
Issue:
Media is being frozen on the second backupattempt due to medium identifiers do notmatch.
Troubleshooting:
This has been known to occur whenusing NetBackup with a IBM 3581 LTO Ultrium 2 tape drive at firmware revision67U1.
Upon first load of new media, the drive is expected to generate andwrite the media information to the header area of the tape before it releasesthe drive to NetBackup for write operations. NetBackup then scans thisinformation and updates the EMM (Enterprise Media Manager) database with themedium manufacturer and medium serial number. There are certain situationswhere the drive is released to NetBackup before this information is written.
When NetBackup does not find this information on the tape, it writesgeneric information ([MedMfgr], [MediumSerialNumber]) to the EMM database beforewriting the first backup. After the first backup is written, the drive is thengenerating and writing the manufacturer and serial numbers to the media. WhenNetBackup uses this media for subsequent operations, the header is scanned andthe new information on the media does not match what is in the EMM, therefore,NetBackup will generate a medium identifier mismatch and freeze themedia.
LogFiles:
<install_path>\NetBackup\logs\ bptm
13:14:26.395[3200.3450] <2> set_job_details: LOG 1178564713 16 bptm 3200 FREEZINGmedia id 0182L1, Medium identifiers do notmatch
Resolution:
In configurations where this issue isseen with NetBackup, the issue has been known to be resolved after downgradingto firmware revision 5AT0. The latest revision release also may resolvethis issue. Visit IBM's site to determine the latest firmware release availablefor the IBM 3581 LTO Ultrium 2 tape drive.
If the firmware cannot bedowngraded/updated, the following workaround has been noted:
Media is being frozen on the second backupattempt due to medium identifiers do notmatch.
Troubleshooting:
This has been known to occur whenusing NetBackup with a IBM 3581 LTO Ultrium 2 tape drive at firmware revision67U1.
Upon first load of new media, the drive is expected to generate andwrite the media information to the header area of the tape before it releasesthe drive to NetBackup for write operations. NetBackup then scans thisinformation and updates the EMM (Enterprise Media Manager) database with themedium manufacturer and medium serial number. There are certain situationswhere the drive is released to NetBackup before this information is written.
When NetBackup does not find this information on the tape, it writesgeneric information ([MedMfgr], [MediumSerialNumber]) to the EMM database beforewriting the first backup. After the first backup is written, the drive is thengenerating and writing the manufacturer and serial numbers to the media. WhenNetBackup uses this media for subsequent operations, the header is scanned andthe new information on the media does not match what is in the EMM, therefore,NetBackup will generate a medium identifier mismatch and freeze themedia.
LogFiles:
<install_path>\NetBackup\logs\ bptm
13:14:26.395[3200.3450] <2> set_job_details: LOG 1178564713 16 bptm 3200 FREEZINGmedia id 0182L1, Medium identifiers do notmatch
Resolution:
In configurations where this issue isseen with NetBackup, the issue has been known to be resolved after downgradingto firmware revision 5AT0. The latest revision release also may resolvethis issue. Visit IBM's site to determine the latest firmware release availablefor the IBM 3581 LTO Ultrium 2 tape drive.
If the firmware cannot bedowngraded/updated, the following workaround has been noted:
- Addnew media and perform a robot inventory.
- Writea small, test backup to the new media (Note: it may be necessary to move allother media to "standalone" to force selection of this new media)
- Usebpexpdate to manually expire the image on the new media.
- Performa "Quick Erase" on the new media. This will force an EMM database updatewith the medium manufacturer and serial number. Note: A "Quick Erase"erases the media header, making any previously written data on that mediairretrievable.
- Backupsand restores should now work normally for the media inquestion.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.