15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

econv Error Messages<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

Message: No device of the appropriate type found <strong>for</strong> this media<br />

Explanation: <strong>NetBackup</strong> does not have any drives configured that match the base media<br />

type of the Backup Exec media.<br />

For example: If the Backup Exec media has media type dlt, there should be at least one<br />

<strong>NetBackup</strong> drive whose drive type is dlt, dlt2 or dlt3.<br />

Recommended Action: Configure drives of the appropriate drive type. Use the Device<br />

Configuration Wizard or another device configuration interface in <strong>NetBackup</strong>.<br />

Message: Media is not assigned to the local <strong>NetBackup</strong> media server<br />

Explanation: This happens when beconv associates a Backup Exec media with a volume<br />

record in the Media Manager volume database either by a barcode, GUID, or slot match,<br />

but the volume is not assigned to the local <strong>NetBackup</strong> media server. This situation is<br />

detected when the volume record in the Media Manager volume database is assigned, but<br />

the volume is not present in the <strong>NetBackup</strong> media database of the local host. This is an<br />

error condition, because Backup Exec media will only be mounted on the local host. Such<br />

Backup Exec media should only be assigned to the local <strong>NetBackup</strong> media server.<br />

Recommended Action: Examine the Media Manager volume record and determine to<br />

which media server it is assigned. There is no direct method to obtain the assigned media<br />

server, other than by checking all media servers. The status field in the volume record<br />

indicates the application owner. If it does not need to be assigned to that media server,<br />

manually expire the media and run beconv again.<br />

Caution Do not unassign media in Media Manager. Unassigning volumes in Media<br />

Manager may lead to inconsistencies between the application media database<br />

and the Media Manager volume database, leading to possible data loss.<br />

Message: A mismatch between media type and robot type detected<br />

Explanation: This happens when beconv associates Backup Exec media with a volume<br />

record in the Media Manager volume database either by a barcode or GUID match, but<br />

the robot type of the record does not have a drive available to match the media type of the<br />

Backup Exec media.<br />

For example: The Backup Exec ADAMM database says that Backup Exec media<br />

BE-Media, having barcode EFG00, media type dlt, is in Backup Exec robot Exabyte-210.<br />

Backup Exec robot Exabyte-210 corresponds to Media Manager robot tld (0). The Media<br />

Manager volume database <strong>for</strong> robot tld(0) contains a media record EFG000, having<br />

barcode EFG00, media type 4mm, belonging to robot tl4(1).<br />

This is an error because a Backup Exec media of type dlt, having barcode EFG00 cannot be<br />

associated with a Media Manager volume record having media type 4mm. Backup Exec<br />

media cannot be associated with a Media Manager volume record of an incompatible<br />

robot type.<br />

474 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> - <strong>Windows</strong> NT/2000<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!