Veritas NetBackup™ for Informix Administrator's Guide
- Introduction to NetBackup for Informix
- Installing NetBackup for Informix
- Configuring NetBackup for Informix
- About configuring a backup policy for Informix
- About schedule properties
- About NetBackup for Informix scripts
- Performing backups and restores of Informix
- About the NetBackup for Informix log files
- Appendix A. Register authorized locations
Verifying NetBackup for Informix log files
Use the following procedure to verify that the log files are configured correctly. You can also refer to Informix ON-Bar utility error logging and tracing. See About Informix ON-Bar utility logs.
To verify the NetBackup for Informix log files
- Check the Informix instance log specified by MSGPATH in the Informix configuration file $ONCONFIG.
- Verify the existence of the following log directories:
infxbsadirectories and any subdirectories should have 777 permissions. They must exist and be accessible for the applications to operate correctly.
Examine the client logs in the following order:
The Informix server log. This path is specified in ONCONFIG.
The NetBackup for Informix debug log directory, /usr/openv/netbackup/logs/infxbsa.If this directory was created properly and no log is present, then stop. The absence of a file in a properly created directory indicates a problem with the communication from ON-Bar to NetBackup for Informix. This file is the starting point of communication with NetBackup. Its absence indicates there are no further NetBackup activities on either the server or client.
- Examine other log files.
The following log files reside in the /usr/openv/netbackup/logs directories on the servers indicated:
bpcd, bpdbm, bprd
bpbrm, bpcd, bpdm, bptm
/user_ops/dbext/logs, bpcd, bphdb, infxbsa
NetBackup writes a log file to /usr/openv/netbackup/logs/user_ops/dbext/logs for each backup and restore session. NetBackup writes the other log files on a daily basis. Log files in the log directories have the naming convention of log.mmddyy. or mmddyy_nnnnn.log (if robust logging is enabled). These files may offer additional debug information.
For example, the bprd log file shows if a backup or restore request from bpbackup or bprestore was received. Examine the request's details such as client name, policy type, client type, and backup file name.
- Examine the communication progress file.
The communication progress file logs communication between the NetBackup server and the NetBackup client during backups and restores. This file is the key file in the debugging process.
The following is an example of a progress file name:
Perform the following steps to determine the communication progress file's name:
Use the cd(1) command to change to the /usr/openv/netbackup/logs/infxbsa directory.
Use an editor to open the file in that directory.The following are examples of file names: log.103105, 103105.00001.log.
Use an editor to open the log file and search for the communication progress file's name.
For example, search for the string openProgressFile.
The search flags the following lines in the file:
13:56:42.905  <4> openProgressFile: entering openProgressFile. 13:56:42.905  <4> openProgressFile: commFull = </usr/openv/ netbackup/logs/user_ops/dbext/logs/6749.0.1115233002>
This output tells you that the communication progress file's name is 6749.0.1115233002.
The Informix ON-Bar utility performs its own error logging and tracing in the file specified by BAR_ACT_LOG in the $INFORMIXDIR/etc/ONCONFIG file. Database administrators can use this log file to determine what happened during ON-Bar execution.