Description
This article defines the logs needed in order to expedite the troubleshooting of an SQL Case. While there are cases where logs other than the ones documented are required for resolution, this article should cover the requirements for most cases.
By default, log files are placed in the <install_path>\veritas\netbackup\logs directory on a NetBackup server.
To enable logging on any of the NetBackup processes, a directory must be created in the <install_path>\veritas\netbackup\logs directory on the NetBackup server or client. The following log folders should be created on the affected NetBackup client.
- bphdb: Contains process information for the hot database backup binary used to start scheduled backups and restores
- dbclient: Contains process information from the SQL server agent and the VERITAS client interface program
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 instead of the bptm folder.
Create the following directory on the master server:
- bprd: The bprd process is the main NetBackup process, and handles all requests for backups and restores
In order to ensure logs are sufficiently verbose, it is usually necessary to change the debug levels on all involved machines. To do that, go into the Backup, Archive and Restore program, and select File | NetBackup Client Properties, and click on the Troubleshooting tab. Increase the General, Verbose, and Database levels to 2, 5 and 9, respectively. Then stop and start all the NetBackup services, as this enables NetBackup to recognize the new logging directories.
On UNIX master or media servers, the directories are created in the /usr/openv/netbackup/logs directory. To change the debug levels, edit the bp.conf file to include the line "VERBOSE = 5," and then stop and start all the NetBackup daemons, so NetBackup can recognize the new logging directories.
Once logging is enabled, run the backup or restore, and collect and send the following information for the Support Engineer to review:
- 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
- On the SQL server, find and run the sqldiag.exe command. This creates an SQLdiag.txt file in the log folder of the SQL Server installation. Gather the SQLdiag.txt, VDI.log, and ERRORLOG from the SQL log directory and forward them to the Support Engineer.
- Zip the contents of the <install_path>\veritas\netbackup\logs\user_ops\mssql\logs directory on the SQL server, and forward to the Support Engineer
- Note the names of each of the machines
Additionally, it is helpful to have the output of the nbsu utility from the affected client, as well as the NetBackup master server and media server.
Related Knowledge Base Articles
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.