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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Status Codes<br />

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

Explanation: A request was made to the <strong>NetBackup</strong> Request Manager service or<br />

<strong>NetBackup</strong> Database Manager service by an invalid media server or <strong>Windows</strong> <strong>NetBackup</strong><br />

Remote Administration Console.<br />

Recommended Action: Examine the <strong>NetBackup</strong> All Log Entries report <strong>for</strong> the time of this<br />

error to determine which system was trying to connect to the master server.<br />

If the server is a valid media server, verify that the storage unit <strong>for</strong> the media server is<br />

defined. Also, verify that the server or <strong>Windows</strong> <strong>NetBackup</strong> Remote Administration<br />

Console has a server list entry on the master server.<br />

Add the media server to the list on the Servers tab in the Master Server Properties dialog<br />

(see “Using the Host Properties Window” on page 40).<br />

If a server or <strong>Windows</strong> <strong>NetBackup</strong> Remote Administration Console has more than one<br />

host name (<strong>for</strong> example, if it has multiple network interfaces), verify that the master<br />

server has a server list entry <strong>for</strong> each of them.<br />

If you change the server list on a <strong>Windows</strong> master server, stop and then restart the<br />

<strong>NetBackup</strong> Request Manager and <strong>NetBackup</strong> Database Manager services.<br />

<strong>NetBackup</strong> Status Code:<strong>NetBackup</strong> Status Code: 39<br />

Message: client name mismatch<br />

Explanation: The name that the client used in a request to the <strong>NetBackup</strong> server did not<br />

match the client name configured in the policy on the server.<br />

Recommended Action: Change either the <strong>NetBackup</strong> client name setting on the client (see<br />

the applicable <strong>NetBackup</strong> users guide) or the one in the policy configuration on the server<br />

so the two match.<br />

<strong>NetBackup</strong> Status Code: 40<br />

Message: network connection broken<br />

Explanation: The connection between the client and the server was broken. This status<br />

code can also appear if the connection is broken between the master and media server<br />

during a backup.<br />

Recommended Action:<br />

1. Try pinging the client from the server. If this is not possible, check <strong>for</strong> loose<br />

connections or other network problems.<br />

2. Verify that the server list settings are correct on both the client and the server. If the<br />

backup involves a media server, verify that these entries are correct on both the<br />

master and media server. For example, if a media server does not have a server list<br />

entry <strong>for</strong> the master, it does not accept connections from the master.<br />

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