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.

Status Codes<br />

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

CLIENT_CONNECT_TIMEOUT = 3000<br />

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

Message: socket write failed<br />

Explanation: A write operation to a socket failed.<br />

Recommended Action:<br />

1. Check the <strong>NetBackup</strong> Problems report <strong>for</strong> clues on where and why the failure<br />

occurred. If you cannot determine the cause from the Problems report, create debug<br />

log directories <strong>for</strong> the processes that could have returned this status code. Then retry<br />

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

2. A possible cause could be a high network load. For example, this has been seen in<br />

conjunction with Cannot write to STDOUT when a <strong>Windows</strong> system that is<br />

monitoring network load has detected a high load and sent an ICMP packet to other<br />

systems that says the route being used by those systems was disconnected. The log<br />

messages were similar to the following:<br />

01/31/96 14:05:23 ruble crabtree.null.com from client<br />

crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No route<br />

to host<br />

01/31/96 14:05:48 ruble crabtree.null.com successfully wrote backup<br />

id crabtree.null.com_0823125016, copy 1, fragment 1, 440864 Kbytes at<br />

628.538 Kbytes/sec<br />

01/31/96 14:05:51 netbackup crabtree.null.com CLIENT<br />

crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT STATUS 24<br />

(socket write failed)<br />

3. On <strong>Windows</strong>, verify that the recommended service packs are installed.<br />

4. This error may occur during a restore to a Novell client. Note the following possible<br />

actions:<br />

◆ By default, the value <strong>for</strong> Novell “Maximum Packet Receive Buffers” may be too<br />

low (such as 100). The restore per<strong>for</strong>mance may be improved by changing this<br />

value to 2000. To change it, issue “SET Maximum Packet Receive<br />

Buffers=” at the console, or enter the value in either of the following<br />

Novell files: sys:system\startup.ncf or sys:system\autoexec.ncf.<br />

◆ Change to or add the following settings in the Novell<br />

sys:system\autoexec.ncf file:<br />

SET Maximum Packet Receive Buffers = 4000<br />

SET Maximum Directory Cache Buffers = 4000<br />

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

74 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> - <strong>Windows</strong> NT/2000<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!