Veritas NetBackup™ Logging Reference Guide
- Using logs
- About logs
- About UNIX system logs
- About log retention in NetBackup
- About limiting the size of unified and legacy logs
- About unified logging
- Gathering unified logs for NetBackup
- Types of unified logging messages
- File name format for unified logging
- Originator IDs for the entities that use unified logging
- About changing the location of unified log files
- About rolling over unified log files
- About recycling unified log files
- About using the vxlogview command to view unified logs
- About query strings used with the vxlogview command
- Examples of using vxlogview to view unified logs
- Examples of using vxlogmgr to manage unified logs
- Examples of using vxlogcfg to configure unified logs
- About legacy logging
- UNIX client processes that use legacy logging
- PC client processes that use legacy logging
- File name format for legacy logging
- Directory names for legacy debug logs for servers
- Directory names for legacy debug logs for media and device management
- How to control the amount of information written to legacy logging files
- About limiting the size and the retention of legacy logs
- Configuring the legacy log rotation
- About global logging levels
- Setting retention limits for logs on clients
- Logging options with the Windows Event Viewer
- Troubleshooting error messages in the NetBackup Administration Console
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced Backup and Restore Features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- NetBackup secure communication logging
- About NetBackup secure communication logging
- Tomcat logging
- NetBackup web services logging
- Command-line logging
- NetBackup cURL logging
- Java logging
- Embeddable Authentication Client (EAT) logging
- Authentication Services (AT) logging
- vssat logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- PBX logging
- Sending secure communication logs to Veritas Technical Support
- Snapshot technologies
- Locating logs
- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprestore logging
- bptestnetconn logging
- bptm logging
- daemon logging
- ltid logging
- nbemm logging
- nbjm logging
- nbpem logging
- nbproxy logging
- nbrb logging
- NetBackup web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
- Java-based administration console logging
- About the Java-based administration console logging
- Java-based administration console logging process flow
- Setting up a secure channel between the Java-based administration console and bpjava-*
- Setting up a secure channel between the Java-based administration console and either nbsl or nbvault
- Java-based administration console logging configuration on NetBackup servers and clients
- Java-based remote administration console logging on a Windows computer where NetBackup is not installed
- Configuring and gathering logs when troubleshooting Java GUI issues
- Undo logging
About query strings used with the vxlogview command
Use the vxlogview command to display the logs that unified logging generates. The vxlogview command includes the following option: -w (- -where) QueryString.
QueryString represents a text expression similar to a database WHERE clause. The query string expression is used to retrieve log entries from the unified logging system. The expression is a combination of relational operators, constant integers, constant strings, and names of log fields that evaluate to a single value. Expressions are grouped by logical operators such as AND and OR.
The supported relational operators are as follows:
< | less than |
> | greater than |
<= | less than and equal to |
>= | greater than and equal to |
= | equal to |
!= | not equal to |
The supported logical operators are as follows:
&& | logical AND |
|| | logical OR |
Table: Data types for fields shows data types for specific fields as well as description and an example. When more than one example is listed, both examples produce the same results.
Table: Data types for fields
Field name | Type | Description | Example |
|---|---|---|---|
PRODID | Integer or string | Provide the product ID or the abbreviated name of product. | PRODID = 51216 PRODID = 'NBU' |
ORGID | Integer or string | Provide the originator ID or the abbreviated name of the component. | ORGID = 116 ORGID = 'nbpem' |
PID | Long Integer | Provide the process ID | PID = 1234567 |
TID | Long Integer | Provide the thread ID | TID = 2874950 |
STDATE | Long Integer or string | Provide the start date in seconds or in the locale-specific short date and time format. For example, a locale can have the format 'mm/dd/yy hh:mm:ss AM/PM' | STDATE = 98736352 STDATE = '4/26/11 11:01:00 AM' |
ENDATE | Long Integer or string | Provide the end date in seconds or in the locale-specific short date and time format. For example, a locale can have the format 'mm/dd/yy hh:mm:ss AM/PM' | ENDATE = 99736352 ENDATE = '04/27/11 10:01:00 AM' |
PREVTIME | String | Provide the hours in 'hh:mm:ss' format. This field should be used only with operators =, <, >, >=, and <= | PREVTIME = '2:34:00' |
SEV | Integer | Provide one of the following possible severity types: 0 = INFO 1 = WARNING 2 = ERR 3 = CRIT 4 = EMERG | SEV = 0 SEV = INFO |
MSGTYPE | Integer | Provide one of the following possible message types: 0 = DEBUG (debug messages) 1 = DIAG (diagnostic messages) 2 = APP (application messages) 3 = CTX (context messages) 4 = AUDIT (audit messages) | MSGTYPE = 1 MSGTYPE = DIAG |
CTX | Integer or string | Provide the context token as string identifier or 'ALL' to get all the context instances to be displayed. This field should be used only with the operators = and !=. | CTX = 78 CTX = 'ALL' |
Consider the following when writing a query string.
Case sensitivity | Field names, severity types, and message types are not case-sensitive. For example, the following are valid entries:
|
String constants | String constants should be given in single quotes. For example, PRODID = 'NBU' |
Dates | Start and end dates can be provided in the following formats:
|
Table: Examples of query strings provides examples of query strings.
Table: Examples of query strings
Example | Description |
|---|---|
(PRODID == 51216) && ((PID == 178964) || ((STDATE == '2/5/15 09:00:00 AM') && (ENDATE == '2/5/15 12:00:00 PM')) | Retrieves the log file message for the NetBackup product ID 51216 between 9AM and 12PM on 2015-05-02. |
((prodid = 'NBU') && ((stdate >= '11/18/14 00:00:00 AM') && (endate <= '12/13/14 12:00:00 PM'))) || ((prodid = 'BENT') && ((stdate >= '12/12/14 00:00:00 AM') && (endate <= '12/25/14 12:00:00 PM'))) | Retrieves the log messages for the NetBackup product NBU between 2014-18-11 and 2014-13-12 and the log messages for the NetBackup product BENT between 2014-12-12 and 2014-25-12. |
(STDATE <= '04/05/15 0:0:0 AM') | Retrieves the log messages that were logged on or before 2015-05-04 for all of the installed Veritas products. |