Troubleshooting guide

Appendix B, Networks and Hostnames 273
The destination client name is a factor only if an administrator is pushing a restore to a
client from a server. For a user restore, destination client and requesting client are the
same. For an administrator restore, the administrator can specify a different name for the
destination client.
By the time these names appear in the bprd activity log, the requesting client name has
been translated into the client’s configured name.
Depending on the particulars of the restore request (for example, from root on a server,
from a client, to an alternate client, and so on), the name used to connect back to the client
to complete the restore is either the client’s peername or its configured name.
When modifying client names in NetBackup classes to accommodate specific network
paths, the administrator needs to consider:
◆ The client name as configured on the client. For example, on UNIX this is
CLIENT_NAME in the client’s bp.conf file. On a Windows client, it is on the General
tab of the NetBackup Configuration dialog box. To open this dialog box, click
Configure on the Actions menu in the Backup, Archive, and Restore interface.
◆ The client as currently named in the class configuration.
◆ Existing client backup and archive images as recorded in the images directory on the
master server. On a UNIX server, this is the /usr/openv/netbackup/db/images
directory. On a Windows NT/2000 NetBackup server this is the
install_path\NetBackup\db\images directory.
All of the above can require manual modification by the administrator if a client has
multiple network connections to the server and restores from the client fail due to a
connection-related problem.
On UNIX, the public domain program traceroute (not included with NetBackup) often
can provide valuable information about a network’s configuration. Some system vendors
include this program with their systems.
If Domain Name Services are used and the (possibly unqualified) name that the
NetBackup client obtains through its gethostname() library function is unknown to the
Domain Name Service (DNS) on the master server, the master server can be unable to
reply to client requests. Whether this situation exists, depends on how the client and the
server are configured. If gethostname()on the client returns host names that are not
qualified to the extent that DNS on the master server can resolve them, then you will
encounter problems.
Although a possible solution is to reconfigure the client or the master server DNS hosts
file, this is not always desirable. For this reason, NetBackup provides a special file on the
master server. This file is:
/usr/openv/netbackup/db/altnames/host.xlate (UNIX)
install_path\NetBackup\db\altnames\host.xlate (Windows NT/2000)