Veritas NetBackup™ Troubleshooting Guide

To verify the host name and service entries in NetBackup

1. Verify that the correct client and server host names are configured in NetBackup. The action you take depends on the computer that you check.

   On Windows servers and Windows clients	Do the following: On the Server to use for backups and restores drop-down list, ensure that a server entry exists for the master server and each media server. Start the Backup, Archive, and Restore interface on the client. On the File menu, click Specify NetBackup Machines and Policy Type. In the Specify NetBackup Machines and Policy Type dialog box, click the Server to use for backups and restores drop-down list. On Windows computers, the correct server must be designated as the current master server in the list. If you add or modify server entries on the master server, stop and restart the NetBackup Request service and NetBackup Database Manager services. On the General tab, verify that the client name setting is correct and matches what is in the policy client list on the master server. Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box, click the General tab. On a master or a media server, ensure that a server entry exists for each Windows administrative client to use to administer that server. Ensure that host names are spelled correctly in the bp.conf file (UNIX) or in the servers list (Windows) on the master server. If a host name is misspelled or cannot be resolved with gethostbyname, the following error messages are logged on the NetBackup error log: Gethostbyname failed for <host_name>:<h_errno_string> (<h_errno>) One or more servers was excluded from the server list because gethostby name() failed. You can also make these changes on the appropriate tabs in the properties dialog boxes on a Windows NetBackup server See Using the Host Properties window to access configuration settings.
   On UNIX NetBackup servers and clients	Check the server and the client name entries in the bp.conf file by doing the following: Ensure that a SERVER entry exists for the master server and each media server in the configuration. The master server must be the first name in the list. If you add or modify SERVER entries on the master server, stop and restart bprd and bpdbm before the changes take effect. The bp.conf of the master server does not require the addition of other clients, other than the master server as CLIENT_NAME = master server name. The name is added by default. The bp.conf file is in the /usr/openv/netbackup directory on UNIX clients. UNIX client users can also have a personal bp.conf file in their home directory. A CLIENT_NAME option in $HOME/bp.conf overrides the option in /usr/openv/netbackup/bp.conf.
   On the master server	Verify that you have created any of the following required files: install_path\NetBackup\db\altnames files (Windows) /usr/openv/netbackup/db/altnames files (UNIX) Pay particular attention to requirements for host.xlate file entries.

2. Verify that each server and client have the required entries for NetBackup reserved port numbers.

   The following examples show the default port numbers.

   Do not change NetBackup port assignments unless it is necessary to resolve conflicts with other applications. If you do change them, do so on all NetBackup clients and servers. These numbers must be the same throughout your NetBackup configuration.

3. On NetBackup servers, check the services files to ensure that they have entries for the following:

   • bpcd and bprd

   • vmd

   • bpdbm

   • Processes for configured robots (for example, tl8cd).

     See the NetBackup Device Configuration Guide.

   Verify the NetBackup client daemon or service number, and the request daemon or service port number. The action you take depends on whether the client is UNIX or Microsoft Windows.

   On UNIX clients

   Check the bprd and the bpcd entries in the /etc/services file.

   On Microsoft Windows clients

   Verify that the NetBackup Client Service Port number and NetBackup Request Service Port number match settings in the services file by doing the following: Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box on the Network tab, select the following: The NetBackup Client Service Port number and NetBackup Request Service Port number. The values on the Network tab are written to the services file when the NetBackup Client service starts. The services file is in the following location: %SystemRoot%\system32\drivers\etc\services

4. On UNIX servers and clients, ensure that the bpcd -standalone process is running.

5. On Windows servers and clients, verify that the NetBackup Client service is running.
6. If you use NIS in your network, update those services to include the NetBackup information that is added to the /etc/services file.

7. NIS, WINS, or DNS host name information must correspond to what is in the policy configuration and the name entries. On Windows NetBackup servers and Microsoft Windows clients, do the following:

   • Check the General tab:

     Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box, click the General tab.

   • Check the Server to use for backups and restores drop-down list:

     Start the Backup, Archive, and Restore interface on the client. On the File menu, click Specify NetBackup Machines and Policy Type. In the Specify NetBackup Machines and Policy Type dialog box, click the Server to use for backups and restores drop-down list.

   • Check the bp.conf file on UNIX servers and clients.

   • Verify that reverse DNS addressing is configured.

8. Use the bpclntcmd utility to confirm the setup of the IP addresses and host names in DNS, NIS, and local hosts files on each NetBackup node.

   Note:

   FT (Fibre Transport) target devices are named based on the host name or domain name response from the device. If any alternate computer names for different VLAN network interface names appear in the SERVER/MEDIA_SERVER entries of the DNS (Domain Name System) or the host files, the primary name must appear first.

   See About the bpclntcmd utility.