NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
◆ Make sure all recommended NetBackup patches have been installed. Check the
VERITAS support web site for current patch information. (Go to
www.support.veritas.com, then select “NetBackup” followed by “files and
updates”.)
◆ If failure occurs when executing a user-directed backup from a client, make sure a
user-directed backup schedule exists at the master server.
◆ When working with NetBackup database extensions, make sure that the
applicable database product has the correct permissions allowing NetBackup to
write to the progress log on the client.
3. Check the services file.
On Windows, verify that the
%SystemRoot%\system32\drivers\etc\services file has the correct entries
for bpcd, bpdbm, and bprd.
Also, verify that the NetBackup Client Service Port number and NetBackup Request
Service Port number on the Network tab in the NetBackup Client Properties dialog
match the settings in the services file. To display this dialog, start the Backup,
Archive, and Restore interface and click NetBackup Client Properties on the File
menu. The values on the Network tab are written to the services file when the
NetBackup Client service starts.
Also, see “Verifying Host Names and Services Entries” on page 25.
4. On Windows, verify that the recommended service packs are installed.
5. When the base NetBackup BusinesServer or DataCenter license key expires, daemons
(such as bprd and bpdbm) will terminate on the NetBackup server. If these daemons
are not running, you are likely to encounter status code 25 errors in the
Administration GUIs. Install a valid base NetBackup license key, restart the daemons,
and restart the GUI.
NetBackup Status Code: 26
Message: client/server handshaking failed
Explanation: A process on the server encountered an error when communicating with the
client. This error indicates that the client and server were able to initiate communications,
but encountered difficulties in completing them. This problem can occur during a backup
or a restore.
Recommended Action: Determine which activity encountered the handshake failure by
examining the All Log Entries report for the appropriate time period. Determine the client
and server that had the handshake failure.
76 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows