DOCUMENTATION: How to enable logging to troubleshoot NetBackup ... http://seer.entsupport.symantec.com/docs/267963.

htm

Support Home | Supported Products A to Z

Document ID: 267963 E-Mail this document to a colleague Knowledge Base X

http://support.veritas.com/docs/267963 Search
DOCUMENTATION: How to enable logging to troubleshoot NetBackup Oracle backups on
Unix/Windows Advanced Search Options

Details: Other Support Resources

Manual: Support Forums
NetBackup 5.0 for Oracle System Administrator's Guide for Unix/Windows Ask an expert. Join collaborative
NetBackup 5.1 for Oracle System Administrator's Guide for Unix/Windows product discussions within our
NetBackup 6.0 for Oracle System Administrator's Guide for Unix/Windows Forum community.
NetBackup 6.5 for Oracle System Administrator's Guide for Unix/Windows Manage Cases Online
NetBackup 7.0 for Oracle System Administrator's Guide for Unix/Windows Submit and manage your support
cases using MySupport.
Contact Technical Support
Page: N/A Find the support phone number for
your region.
Modification Type: Supplement

Modification: Was this article helpful to you?

The majority of cases at Symantec require the collection of log files in order to determine the nature of the Yes No
backup or restore problem. Given the comprehensive nature of NetBackup (tm), knowing which logs to collect
and which logs are unnecessary can present a daunting task. This TechNote is designed to assist a user in If any information was unclear, or the
information you were seeking was not
determining what logs a Support Engineer needs to see in order to expedite the troubleshooting of an Oracle provided, please let us know. Your
case. While there are cases where logs other than the ones documented are required for resolution, this feedback will help us improve this
TechNote should cover the requirements for nearly all cases. service.

By default, log files are placed in the <install_path>\veritas\netbackup\logs (Windows) and /usr/openv
/netbackup/logs (UNIX/Linux) directories on a NetBackup server. NetBackup logs can grow quite large, and
it may be necessary to move the log location. To do this, please refer to TechNote 239186 ( (Optional Email Address)
http://support.veritas.com/docs/239186 ). This TechNote covers the way in which Symantec log files are relocated on
a Windows server. For information on how to relocate logs on a UNIX master or media ser r, please refer to
TechNote 266619 ( http://support.veritas.com/docs/266619 ).
NOTE: Comments entered here will NOT
To enable logging on any of the NetBackup processes, a subdirectory must be created in the NetBackup logs receive support services. If you need
Symantec Enterprise product support,
directory on the NetBackup host. please click here.

Unix: /usr/openv/netbackup/logs
Windows: <install_path>\Veritas\NetBackup\logs

The following log folders should be created on the Oracle client server:

dbclient: This log contains debugging information and execution status for the NetBackup Oracle client
processes. Ensure Oracle user has permissions to read/write to the directory.

bpdbsbora: This log contains debugging information and execution status for the bpdbsbora utility.

bphdb: This log contains debugging information for the process that executes the backup/restore script or
template. The obk_stdout and obk_stderr logs contain the stdout and stderr from the script if it does not
redirect those outputs elsewhere.

user_ops: This directory is created automatically and must remain readable and writeable by the Oracle
user. The comm and progress files therein are updated by the NetBackup server processes as the backup or
restore progresses.

bpcd: This log contains debugging information for the connection attempts to update the comm and progress
files.

Create the following directories on the media server:

bpbrm: The bpbrm process handles backup and restore requests.

bptm: The bptm process handles interactions with the tape device. If backing up to a disk storage unit, the
bpdm folder should be created. At NetBackup 6.5 and above, both bptm and bpdm are used for disk
storage units.

Create the following directory on the master server:

bprd: The bprd process handles the inbound backup and restore requests from the client server.

In order to ensure logs are sufficiently verbose, it is usually necessary to change the debug levels on all
involved machines and then stop and restart all the NetBackup services to pick up the change. To set the
debugging level, go into the Backup, Archive and Restore GUI, and select File | NetBackup Client

1 of 3 7/28/2010 3:54 PM
DOCUMENTATION: How to enable logging to troubleshoot NetBackup ... http://seer.entsupport.symantec.com/docs/267963.htm

Properties, and click on the Troubleshooting tab. Increase the General, Verbose, and Database levels to
5. On Unix, the debug level can be changed by editing the bp.conf file and adding the following line:
VERBOSE = 5

If the problem is a performance issue, use VERBOSE = 6 to display delays between dbclient and Oracle.
(This applies only to 5.x and 6.5.4 and above).

Once logging is enabled, run the backup or restore, and collect and send the following information for the
Support Engineer to review:

1. Collect the logs from the above directories, making sure to rename the files to reflect the folder from which
the log comes, and forward to the Support Engineer
2. In addition, on the Oracle client, send the script file (rename it to .txt so it isn't stripped off by anti-virus
software), the Recovery Manager (RMAN) output file, the initSID.ora file, and the zipped contents of the
user_ops directory.
3. In the bphdb directory, there should be two additional sets of files, oracle_stdout.<date> and
oracle_stderr.<date>. Send these files from the date of the backup or restore attempt.
4. Note the names each of the machines

Additionally, it is extremely helpful to have basic system and configuration information from each of the
servers involved in the backup or restore. For NetBackup 6.x and above, run nbsu on the servers. nbsu
should also be run on clients at the 6.5.4 and above versions/release updates. If nbsu is not available, run
the older support program on UNIX servers or download and run the nbsupport utility on Windows servers.

To obtain the nbsupport program:

1. Connect to ftp.nbu.support.veritas.com as anonymous (using your email address as the password).

2. Change to the /pub/support/outgoing directory
3. Find the latest nbsupport file and download it. The file name begins with nbsupport and is a compressed
file. Find the one corresponding to the correct operating system and download it.

After downloading the file, uncompress it to the folder of your choice on the hard drive of the SQL server, as
well as the master and media servers, if they are also Windows servers. After it finishes uncompressing, go
to a command prompt, and change to the directory where the software was placed. Once at the correct
directory, run the nbsupport command, which will generate a .cab file and place it in an output folder in the
directory with the nbsupport file. Send the resulting .cab file(s) to the Support Engineer.

Related Documents:

239186: DOCUMENTATION: How to manually change the path where NetBackup log files are located.
http://support.veritas.com/docs/239186

266619: DOCUMENTATION: Best Practice recommendations for enabling and gathering VERITAS
NetBackup (tm) 4.5 and 5.x logging.
http://support.veritas.com/docs/266619

278388: DOCUMENTATION: How to troubleshoot Oracle backup problems in NetBackup 4.5 and 5.x
http://support.veritas.com/docs/278388

Products Applied: Last Updated: June 16 2010 06:23 PM GMT

NetBackup Enterprise Server 5.0, 6.0, 7.0 Expires on: 06-13-2020
Subscribe to receive critical updates about this
Subjects: document
NetBackup Enterprise Server
Database: Best Practice, How To
Nbu Database Agents: Oracle

Languages:
English (US)

Operating Systems:
Windows Server 2003
Standard Server

Symantec World Headquarters:

20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,

2 of 3 7/28/2010 3:54 PM
DOCUMENTATION: How to enable logging to troubleshoot NetBackup ... http://seer.entsupport.symantec.com/docs/267963.htm

FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES
WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF
SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

3 of 3 7/28/2010 3:54 PM