15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

SET Maximum Concurrent Directory Cache Writes = 2000<br />

SET Maximum Physical Receive Packet Size = 1514<br />

Chapter 4, <strong>NetBackup</strong> Status Codes and Messages 75<br />

Status Codes<br />

<strong>NetBackup</strong> Status Code: 25<br />

Message: cannot connect on socket<br />

Explanation: A process timed out while connecting to another process <strong>for</strong> a particular<br />

operation. This problem can occur when a process tries to connect to the <strong>NetBackup</strong><br />

Request Manager service or the <strong>NetBackup</strong> Database Manager service and the service is<br />

not running. It can also occur if the network or server is heavily loaded and has slow<br />

response time, or if an evaluation license key <strong>for</strong> <strong>NetBackup</strong> BusinesServer or DataCenter<br />

has expired.<br />

Recommended Action:<br />

1. On the <strong>Windows</strong> master server, verify that the <strong>NetBackup</strong> Request Manager and<br />

<strong>NetBackup</strong> Database Manager services are running. If these services are not running,<br />

start them.<br />

If the above services are running, examine the All Log Entries report <strong>for</strong> the time of<br />

the failure to determine where the failure occurred.<br />

◆ If you cannot view the report, or you get a “cannot connect on socket”<br />

error when trying to view it, verify again that the <strong>NetBackup</strong> Database Manager<br />

service is running. Then, create a debug log directory <strong>for</strong> bpdbm, retry the<br />

operation, and check the resulting debug log.<br />

◆ If you can view the report and have not found an entry related to this problem,<br />

create debug log directories <strong>for</strong> the related processes that were running when the<br />

error first appeared (this process will frequently be bpbrm). Then, retry the<br />

operation and check the resulting debug logs.<br />

2. Verify that the server list specifies the correct master server.<br />

◆ On <strong>Windows</strong> systems, the master server is designated as CURRENT on the<br />

Servers tab in the Specify <strong>NetBackup</strong> Machines dialog. To display this dialog box,<br />

start the Backup, Archive, and Restore interface and click Specify <strong>NetBackup</strong><br />

Machines on the Actions menu.<br />

◆ On Macintosh systems, the master server is the first SERVER entry in the<br />

bp.conf file.<br />

◆ On NetWare target and OS/2 clients, the master server name is the first SERVER<br />

entry in the bp.ini file.<br />

If you change the server list on a master server, stop and restart the <strong>NetBackup</strong><br />

Database Manager and <strong>NetBackup</strong> Request Manager services.<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!