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.

<strong>Troubleshooting</strong> with the Debug Logs<br />

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

This problem is more likely to occur with non-barcoded robotic media. The <strong>NetBackup</strong><br />

media id of the Backup Exec media required <strong>for</strong> the restore can be obtained from the<br />

<strong>NetBackup</strong> job progress log. For example:<br />

13:50:01 (11.xxx) Media id A00000 is needed <strong>for</strong> the restore.<br />

The <strong>NetBackup</strong> Media Manager volume database can be queried to determine the<br />

ADAMM GUID (ADAMM GUID field of a Media Manager volume database record), the<br />

description and residence (robot and slot number) of the media id. (The media id is<br />

A00000 in the above example.) The Backup Exec cartridge label of the media can be<br />

determined from the “description” field of the <strong>NetBackup</strong> Media Manager volume<br />

database record.<br />

If the ADAMM GUID (corresponding to the media id in the <strong>NetBackup</strong> Media Manager<br />

volume database) is the same as the GUID obtained from the adamm.log<br />

(C4B3BBAE-8B29-4823-ACE5-EBD546E1574B, in the above example), then the wrong<br />

media may be present in the robot and slot indicated by the <strong>NetBackup</strong> Media Manager<br />

volume database. Verify whether the correct Backup Exec media, identified by ADAMM<br />

GUID and cartridge label, is actually present in the robot and slot as indicated by the<br />

<strong>NetBackup</strong> Media Manager volume database record (corresponding to media id A00000,<br />

in the above example).<br />

A physical inventory of the robot can be per<strong>for</strong>med to update the <strong>NetBackup</strong> Media<br />

Manager volume database. Refer to the section “Updating the Media Manager Volume<br />

Database with Respect to Backup Exec Media” in the <strong>NetBackup</strong> DataCenter System<br />

Administrator’s <strong>Guide</strong>.<br />

If the ADAMM GUID corresponding to the media id in the <strong>NetBackup</strong> Media Manager<br />

volume database is not the same as the GUID obtained from the adamm.log, then<br />

different ADAMM GUIDs are associated with the same media id in the <strong>NetBackup</strong> Media<br />

Manager volume databases of the locally configured drives.<br />

Run beconv with the -check_consistency option, to detect inconsistencies in the<br />

<strong>NetBackup</strong> Media Manager volume database. Refer to the section “Using beconv with the<br />

-check_consistency Option” in the <strong>NetBackup</strong> DataCenter System Administrator’s <strong>Guide</strong>.<br />

492 <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!