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 />

Networks and Hostnames B<br />

In a configuration with multiple networks and clients with more than one hostname, the<br />

<strong>NetBackup</strong> administrator must configure the policy entries carefully, at all times<br />

considering the network configuration (physical, hostnames and aliases, DNS, routing<br />

tables, and so on). This is especially true if the desire is to direct backup and restore data<br />

across specific network paths.<br />

For a backup, <strong>NetBackup</strong> connects to the host name as configured in the policy. The<br />

operating system’s network code resolves this name and sends the connection across the<br />

network path defined by the system’s routing tables.<br />

For restores from the client, the client connects to the master server. On a <strong>Windows</strong><br />

system, the master server is specified on the Servers tab of the Specify <strong>NetBackup</strong><br />

Machines dialog box (to open this dialog, start the <strong>NetBackup</strong> client user interface and<br />

click Specify <strong>NetBackup</strong> Machines on the Actions menu). The network path to the server<br />

is determined by the client’s network code that maps the server name to an IP address.<br />

Upon receipt of the connection, the server determines the client’s configured name from<br />

the peername of its connection to the server.<br />

The peername is derived from the IP address of the connection. This means that the<br />

address must translate into a host name (using the gethostbyaddr() network routine).<br />

This name is visible in the bprd debug log when a connection is made as in the line:<br />

Connection from host peername ipaddress ...<br />

The client’s configured name is then derived from the peername by querying the bpdbm<br />

process (<strong>NetBackup</strong> Database Manager service).<br />

The bpdbm process compares the peername to a list of client names generated from:<br />

1. All clients <strong>for</strong> which a backup has been attempted<br />

and<br />

2. All clients in all policies<br />

The comparison is first a simple string comparison which, if successful, is verified by<br />

comparing hostnames and aliases retrieved by using the network function<br />

gethostbyname().<br />

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

467

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

Saved successfully!

Ooh no, something went wrong!