On the NetBackup Configuration dialog, select the
Troubleshooting tab to view and change the
amount of information that NetBackup saves in its debug or
troubleshooting logs. These options should only be changed if
directed to do so by technical support.
Options for the Troubleshooting tab follow:
Table 3-11 Troubleshooting tab
options
Item
Description
Debug Flush Level
NetBackup periodically flushes the progress
reports on NetBackup operations. This setting specifies the
frequency of the flushes or how often the internal buffer gets
written to the progress report. The higher the flush level, the
more often the buffer is written to the file. Supported values are
0, 1, or 2. The default is 0. Changing the level takes affect
during the next backup or restore. BPCD.NLM does not need to
be unloaded and loaded for changes to take affect.
Debug Heap Level
This parameter is not used in NetBackup 5.0.
Debug General Level
Controls the amount of information that NetBackup
writes to the troubleshooting logs. Supported values are 0, 1, or
2. The higher the level, the more information is written. The
default is 0.
Changing the level takes affect during the next
backup or restore. BPCD.NLM does
not need to be unloaded and loaded for
changes to take affect.
Debug TCP Level
Used for debug purposes and enables TCP debugging.
Supported values are as follows:
0 No extra logging. This is the default.
1 Log basic TCP/IP functions.
2 Log all TCP/IP functions, including all read and
write requests.
3 Log contents of each read/write buffer.
Note: Setting Debug TCP
Level to 2 or 3 can cause the troubleshooting logs to be very
large. It can also slow performance of a backup or restore
operation. Changing the TCP debug value does not take affect until
the bpcd.nlm is unloaded and
loaded.
More Information
500 Internal Server Error
Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred,
and the actions you performed just before this error.
More information about this error may be available
in the server error log.
Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.