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 />

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

Status Codes<br />

◆ On <strong>Windows</strong>, the master server is designated on the Servers tab in the Master<br />

Server Properties dialog. To display this dialog, see “Using the Host Properties<br />

Window” on page 40.<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 />

3. Status code 40 can also be due to the operator denying a mount request.<br />

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

Message: network connection timed out<br />

Explanation: The server did not receive any in<strong>for</strong>mation from the client <strong>for</strong> too long a<br />

period of time.<br />

Recommended Action:<br />

1. On<strong>Windows</strong> clients, check <strong>for</strong> the following problems with the bpbkar client<br />

process.<br />

The bpbkar client process is not hung, but due to the files and directories it is<br />

scanning, it has not replied to the server within the Client read timeout or Client<br />

connect timeout period. This has been seen to occur during incremental backups<br />

when directories have thousands of unmodified files.<br />

For this case, use Host Properties on the <strong>NetBackup</strong> server to change Client connect<br />

timeout or Client read timeout. These settings are on the Timeouts and Universal<br />

Settings tabs, respectively, in the Master Server Properties dialog (see “Using the Host<br />

Properties Window” on page 40). The default <strong>for</strong> these timeouts is 300 seconds.<br />

You can also monitor CPU utilization to determine if this condition exists.<br />

2. On <strong>Windows</strong> systems, try the following:<br />

◆ Disable the following file:<br />

install_path\Veritas\<strong>NetBackup</strong>\bin\admincmd\tracker.exe<br />

◆ Repair hard drive fragmentation. You could try an application called Diskeeper<br />

Lite, which is part of the <strong>Windows</strong> NT Resource Kit.<br />

◆ Make sure there is enough space available in \temp.<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!