NetBackup Status Code: 25
Message: cannot connect on socket
Explanation: A process timed out while connecting to another process for a particular
operation. This problem can occur when a process tries to connect to the NetBackup
Request Manager service or the NetBackup Database Manager service and the service is
not running. It can also occur if the network or server is heavily loaded and has slow
response time, or if an evaluation license key for NetBackup BusinesServer or DataCenter
has expired.
Recommended Action:
1. On the Windows master server, verify that the NetBackup Request Manager and
NetBackup Database Manager services are running. If these services are not running,
start them.
If the above services are running, examine the All Log Entries report for the time of
the failure to determine where the failure occurred.
If you cannot view the report, or you get a “cannot connect on socket”
error when trying to view it, verify again that the NetBackup Database Manager
service is running. Then, create a debug log directory for bpdbm, retry the
operation, and check the resulting debug log.
If you can view the report and have not found an entry related to this problem,
create debug log directories for the related processes that were running when the
error first appeared (this process will frequently be bpbrm). Then, retry the
operation and check the resulting debug logs.
2. Verify that the server list specifies the correct master server.
On Windows systems, the master server is designated as CURRENT on the
Servers tab in the Specify NetBackup Machines dialog. To display this dialog box,
start the Backup, Archive, and Restore interface and click Specify NetBackup
Machines on the Actions menu.
On Macintosh systems, the master server is the first SERVER entry in the
bp.conf file.
On NetWare target and OS/2 clients, the master server name is the first SERVER
entry in the bp.ini file.
If you change the server list on a master server, stop and restart the NetBackup
Database Manager and NetBackup Request Manager services.
Make sure all recommended NetBackup patches have been installed. Check the
VERITAS support web site for current patch information. (Go to
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.
Thanks, comtec17!! I tried searching with several search engines and even on the Veritas website, but I couldn't find what I was looking for. For those of you who do not know the URL for the Veritas Product Support FTP site, it is:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.