About conditions that cause media to freeze
|Article:HOWTO34185|||||Created: 2010-10-29|||||Updated: 2011-03-11|||||Article URL http://www.symantec.com/docs/HOWTO34185|
FREEZING media id E00109, it has had at least 3 errors in the last 12 hour(s)
Incorrect media found in drive index 2, expected 30349, \ found 20244, FREEZING 30349
NetBackup requests a media ID to be mounted in a drive. If the media ID that is physically recorded on the tape is different than the NetBackup media ID, the media freezes. This error occurs if the robot needs to be inventoried, or if bar codes have been physically changed on the media.
The drives in the robot are not configured in order within NetBackup, or they are configured with the wrong tape paths. The correct robot drive number is important to the proper mounting and use of media. The robot drive number is normally based on the relationship of the drive serial number with the drive serial number information from the robotic library. Validate this number before you consider that the device configuration is complete.
FREEZING media id 000438, it contains MTF1-format data and cannot be used for backups FREEZING media id 000414, it contains tar-format data and cannot be used for backups FREEZING media id 000199, it contains ANSI-format data and cannot be used for backups
These library tapes may have been written outside of NetBackup. By default, NetBackup only writes to a blank media or other NetBackup media. Other media types (DBR, TAR, CPIO, ANSI, MTF1, and recycled Backup Exec BE-MTF1 media) are frozen as a safety measure. Change this behavior by using the following procedure:
FREEZING media id 000067: it contains Symantec NetBackup (tm) database backup data and cannot be used for backups.
The media is intentionally frozen. You can use the bpmedia command to manually freeze media for a variety of administrative reasons. If no record exists of a specific job freezing the media, the media may have been frozen manually.
# bpmedia -unfreeze -m mediaID -h media_server
The media_server variable is the one that froze the media. If this item is unknown, run the bpmedialist command and note the "Server Host:" listed in the output. The following example shows that media server
denton froze media
# bpmedialist -m div008 Server Host = denton ID rl images allocated last updated density kbytes restores vimages expiration last read <------- STATUS -------> ------------------------------------------------------------------------ DIV08 1 1 04/22/2010 10:12 04/22/2010 10:12 hcart 35 5 1 05/06/2010 10:12 04/22/2010 10:25 FROZEN
Article URL http://www.symantec.com/docs/HOWTO34185