NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
◆ Verify that the Windows TCP/IP service specifies the domain server that resolves
names for the subnet that contains the NetBackup servers.
7. If the preceding steps do not resolve this problem, see “Resolving Network
Communication Problems” on page 21.
8. If NetBackup is using multiple network interfaces with slave servers, make sure the
interface names appear in the client’s /usr/openv/netbackup/bp.conf file.
NetBackup Status Code: 63
Message: process was killed by a signal
Explanation: A kill signal was sent to the client process.
Recommended Action: This is usually caused by someone intentionally terminating a
backup.
NetBackup Status Code: 64
Message: timed out waiting for the client backup to start
Explanation: The client did not send a ready message to the server within the allotted
time.
Recommended Action:
1. On all but Macintosh clients, enable bpcd debug logging as follows:
a. Create a bpcd debug log directory on the client.
b. Increase the debug or log level as explained in the debug log topics in Chapter 3.
2. On Macintosh clients, check the inetd and bpcd debug logs. Both logs are created
automatically.
◆ Check the inetd log to see if NetBackupListen is running.
◆ Check the bpbkar and tar messages in the bpcd log file.
To increase the logging level, set the loglevel parameter in the mac.conf file
to a higher value.
3. On a Windows client, create the bpbkar debug log directory on the client.
4. On Windows clients, verify that the NetBackup Client service is running.
5. Retry the backup and examine the debug logs for clues on the cause of the failure.
92 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows