NetBackup status code: 25
Message: cannot connect on socket
Explanation: A process that timed out while it connects to another process for a particular operation. This problem can occur in the following situation: when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. (On Windows, these daemons are the NetBackup Request Manager and the NetBackup Database Manager services.)
It can also occur in the following situations: the network or server is heavily loaded and has slow response time or an evaluation license key for NetBackup expired. However, the most common cause of this error is a host name resolution problem.
The following are other possible causes of this error caused by network connectivity issues or a required process such as pbx_exchange not running.
nbjm is unable to connect to bpcd on the media server
nbpem is unable to connect to nbproxy
bptm on the media server is unable to connect to nbjm on the master server.
You cannot perform an immediate backup operation.
These errors are caused either by network connectivity issues or if a required process such as pbx_exchange is not running.
Recommended Action: Do the following, as appropriate:
Verify that bpcompatd, vnetd, and Private Branch Exchange (PBX) are running. Information on how to start PBX is available.
See "Resolving PBX problems" in the NetBackup Troubleshooting Guide.
The following information applies only to a UNIX or Linux NetBackup master server:
Verify that the bprd and the bpdbm processes are running. If these processes are not running, start them. On a Windows master server, verify that the NetBackup Request Manager and the NetBackup Database Manager services are running. If these services are not running, start them.
If these processes or services are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred.
Do one of the following:
If you cannot view the report or you get a cannot connect on socket error, verify again that the NetBackup Database Manager service or daemon is running. Then, create a debug log directory for bpdbm, retry the operation, and check the resulting debug log.
If you view the report and do not find a problem-related entry, create the debug log directories for the related processes that were running when the error first appeared. (This process frequently is bpbrm.) Then, retry the operation and check the resulting debug logs.
Verify that the server list specifies the correct master server.
The following information applies only to Windows systems:
The master server is designated in the drop-down in the Specify NetBackup Machines and Policy Type dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click on the File menu.
The following information applies only to UNIX and Linux systems:
The master server is the first SERVER entry in the
bp.conffile.Check the following Veritas Support website to ensure that all recommended NetBackup patches are installed:
If failure occurs when you run a user-directed backup from a client, make sure that a user-directed backup schedule exists at the master server.
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.
The following information applies only to UNIX systems:
If bpdbm has quit when the shutdown script runs on a media server, carefully read the
K77netbackupscript. It contains details on how to prevent this problem. The script is in/usr/openv/netbackup/bin/goodies.
If you change the server list on a master server, stop, and restart the following: The NetBackup Database Manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows).
Check the
servicesfile.The following information applies only to UNIX systems:
Verify that the
/etc/servicesfile (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and bprd.
On Windows, verify that the
%SystemRoot%\system32\drivers\etc\servicesfile has the correct entries for bpcd, bpdbm, and bprd.Also, verify that the following numbers match the settings in the
servicesfile: The and the on the Network tab in the NetBackup Client Properties dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click on the File menu. The values on the Network tab are written to theservicesfile when the NetBackup Client service starts.See Verifying host names and service entries in NetBackup in the NetBackup Troubleshooting Guide.
On Sun Solaris, verify that all operating system patches are installed
See the Operating Notes section of the NetBackup Release Notes.
On Windows, verify that the recommended service packs are installed.
When the base NetBackup license key expires, daemons (such as bprd and bpdbm) terminate on the NetBackup server. If these daemons are not running, you are likely to encounter status code 25 errors in the Administration console. Install a valid base NetBackup license key, restart the daemons, and restart the console.
For NetBackup Snapshot Client, the following applies: When many devices are configured on a media server, it may take a long time for the bptpcinfo command to generate the file
3pc. When the backup is run for the first time, the backup may fail with status 25. Make sure that the/usr/openv/volmgr/database/3pc.conffile exists. If it does, rerun the backup. If the backup fails again, run the bptpcinfo manually to generate the file3pc, then try the backup again.In the Auto Image Replication (A.I.R.) scenario, the error can occur if insecure communication is disabled in NetBackup after the trust relationship between the 8.1 and 8.0 master servers is established. If you want to continue with the host connection, do one of the following:
In the NetBackup Administration Console on the master server host, select the option.
Specify the nbseccmd -setsecurityconfig -insecurecommunication on command.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.