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>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

If none of the comparisons succeed, a more brute <strong>for</strong>ce method is used, which compares<br />

all names and aliases using gethostbyname().<br />

The configured name is the first comparison that succeeds. Note that other comparisons<br />

might also have succeeded if aliases or other “network names” are configured.<br />

If the comparison fails, the client’s hostname as returned by the gethostname()<br />

function on the client is used as the configured name. One example of why the<br />

comparison could fail is the case where the client had changed its hostname but its new<br />

hostname is not reflected in any policies yet.<br />

These comparisons are logged in the bpdbm debug log if VERBOSE is set. You can<br />

determine a client’s configured name by using the bpclntcmd command on the client.<br />

For example:<br />

# install_path\<strong>NetBackup</strong>\bin\bpclntcmd -pn<br />

expecting response from server wind.abc.me.com<br />

danr.abc.me.com danr 194.133.172.3 4823<br />

Where the first output line identifies the server to which the request is directed and the<br />

second output line is the server’s response in the following order:<br />

◆ Peername of the connection to the server<br />

◆ Configured name of the client<br />

◆ IP address of the connection to the server<br />

◆ Port number used in the connection<br />

When the client connects to the server, it sends three names to the server:<br />

◆ browse client<br />

◆ requesting client<br />

◆ destination client<br />

The browse client name is used to identify the client files to list or restore from. The user<br />

on the client can modify this name to restore files from another client. For example, on a<br />

<strong>Windows</strong> client, the user can change the client name by using the client user interface (see<br />

the user’s guide <strong>for</strong> instructions). For this to work, however, the administrator must also<br />

have made a corresponding change on the server. For more in<strong>for</strong>mation, refer to the<br />

<strong>NetBackup</strong> System Administrator’s <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>.<br />

The requesting client is the value from the gethostname() function on the client.<br />

The destination client name is a factor only if an administrator is pushing a restore to a<br />

client from a server. For a user restore, destination client and requesting client are the<br />

same. For an administrator restore, the administrator can specify a different name <strong>for</strong> the<br />

destination client.<br />

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