Veritas NetBackup™ Logging Reference Guide

Last Published:
Product(s): NetBackup (8.0)
  1. Using logs
    1.  
      About logs
    2.  
      About UNIX system logs
    3.  
      About log retention in NetBackup
    4.  
      About limiting the size of unified and legacy logs
    5. About unified logging
      1.  
        Gathering unified logs for NetBackup
      2.  
        Types of unified logging messages
      3.  
        File name format for unified logging
      4.  
        Originator IDs for the entities that use unified logging
      5.  
        About changing the location of unified log files
      6.  
        About rolling over unified log files
      7.  
        About recycling unified log files
      8.  
        About using the vxlogview command to view unified logs
      9.  
        About query strings used with the vxlogview command
      10.  
        Examples of using vxlogview to view unified logs
      11.  
        Examples of using vxlogmgr to manage unified logs
      12.  
        Examples of using vxlogcfg to configure unified logs
    6. About legacy logging
      1.  
        UNIX client processes that use legacy logging
      2.  
        PC client processes that use legacy logging
      3.  
        File name format for legacy logging
      4.  
        Directory names for legacy debug logs for servers
      5.  
        Directory names for legacy debug logs for media and device management
      6.  
        How to control the amount of information written to legacy logging files
      7.  
        About limiting the size and the retention of legacy logs
      8.  
        Configuring the legacy log rotation
    7. About global logging levels
      1.  
        Changing the logging level
      2.  
        Changing the logging level on Windows clients
      3.  
        Setting Media Manager debug logging to a higher level
    8.  
      Setting retention limits for logs on clients
    9.  
      Logging options with the Windows Event Viewer
    10. Troubleshooting error messages in the NetBackup Administration Console
      1.  
        About extra disk space required for logs and temporary files
      2.  
        Enabling detailed debug logging
  2. Backup process and logging
    1.  
      Backup process
    2. NetBackup process descriptions
      1.  
        Backup and restore startup process
      2.  
        Backup and archive processes
      3.  
        Backups and archives - UNIX clients
      4.  
        Multiplexed backup process
    3.  
      About backup logging
    4.  
      Sending backup logs to Veritas Technical Support
  3. Media and device processes and logging
    1.  
      Media and device management startup process
    2.  
      Media and device management process
    3.  
      Shared Storage Option management process
    4.  
      Barcode operations
    5.  
      Media and device management components
  4. Restore process and logging
    1.  
      Restore process
    2.  
      UNIX client restore
    3.  
      Windows client restore
    4.  
      About restore logging
    5.  
      Sending restore logs to Veritas Technical Support
  5. Advanced Backup and Restore Features
    1.  
      SAN Client Fiber Transport backup
    2.  
      SAN Client Fiber Transport restore
    3.  
      Hot catalog backup
    4.  
      Hot catalog restore
    5. Synthetic backups
      1.  
        Creating legacy log directories to accompany problem reports for synthetic backup
      2.  
        Logs to accompany problem reports for synthetic backups
  6. Storage logging
    1.  
      NDMP backup logging
    2.  
      NDMP restore logging
  7. NetBackup Deduplication logging
    1.  
      Deduplication backup process to the Media Server Deduplication Pool (MSDP)
    2.  
      Client deduplication logging
    3.  
      Deduplication configuration logs
    4.  
      Media server deduplication/pdplugin logging
    5.  
      Disk monitoring logging
    6.  
      Logging keywords
  8. OpenStorage Technology (OST) logging
    1.  
      OpenStorage Technology (OST) backup logging
    2.  
      OpenStorage Technology (OST) configuration and management
  9. Snapshot technologies
    1.  
      Snapshot Client backup
    2.  
      VMware backup
    3.  
      Snapshot backup and Windows open file backups
  10. Locating logs
    1.  
      acsssi logging
    2.  
      bpbackup logging
    3.  
      bpbkar logging
    4.  
      bpbrm logging
    5.  
      bpcd logging
    6.  
      bpcompatd logging
    7.  
      bpdbm logging
    8.  
      bpjobd logging
    9.  
      bprd logging
    10.  
      bprestore logging
    11.  
      bptm logging
    12.  
      daemon logging
    13.  
      ltid logging
    14.  
      nbemm logging
    15.  
      nbjm logging
    16.  
      nbpem logging
    17.  
      nbproxy logging
    18.  
      nbrb logging
    19.  
      NetBackup web services logging
    20.  
      NetBackup web server certificate logging
    21.  
      PBX logging
    22.  
      reqlib logging
    23.  
      robots logging
    24.  
      tar logging
    25.  
      txxd and txxcd logging
    26.  
      vnetd logging
  11. Java-based administration console logging
    1.  
      About the Java-based administration console logging
    2.  
      Java-based administration console logging process flow
    3.  
      Setting up a secure channel between the Java-based administration console and bpjava-*
    4.  
      Setting up a secure channel between the Java-based administration console and either nbsl or nbvault
    5.  
      Java-based administration console logging configuration on NetBackup servers and clients
    6.  
      Java-based remote administration console logging on a Windows computer where NetBackup is not installed
    7.  
      Configuring and gathering logs when troubleshooting Java GUI issues
    8.  
      Undo logging

Logging options with the Windows Event Viewer

The NetBackup Windows master servers can be configured to write messages from NetBackup processes to the Application Event log as well as their normal location. These messages can be reviewed in the Windows Event Viewer and also use third-party tools to monitor the Application Event log for these messages.

Two logging options can be used to write messages to the Application Event log. These can be used separately or together and are specific to the type of process that you want to log, as follows:

  • To monitor unified processes (process names that start with nb; for example, nbrb), use the vxlogview command.

  • To monitor legacy processes (process names that start with bp; for example, bpdbm), configure the eventlog file.

Note:

For the settings in the vxlogcfg command or the eventlog file to take effect, you must restart the NetBackup services.

To route unified logging application and diagnostic messages for an originator to the Windows Event Viewer Application log, use the vxlogcfg command and set the LogToOslog value to true for that originator.

The following example routes the application and diagnostic messages for nbrb to the Windows Event Viewer Application log:

# vxlogcfg -a -o nbrb -p NB -s "LogToOslog=true"

and the following example message is written in the Windows Event Viewer Application log when the operating system logging is enabled for nbrb:

from nbrb - request ID {1C7FF863-4BCB-46EA-8B35-629A43A4FF1F} failed with status 0
  (Not Enough Valid Resources); releasing 2 allocated resources

Note:

For this setting to take effect, you must restart the NetBackup services.

When you change this option, the ignorable error messages are also written to the Windows Event Viewer Application log. For example, if you specify the following command:

# vxlogcfg -a -o nbpem -p NB -s "LogToOslog=true"

the following example of an ignorable message is written in the Windows Event Viewer Application log when a storage lifecycle policy does not exist:

call NBProxy::getClientList failed to nbproxy with status 227

A complete description of vxlogcfg is in the NetBackup Commands Reference Guide.

To use the eventlog file, do the following:

  • Create the following file on the NetBackup master server.

    install_path\NetBackup\db\config\eventlog
  • Optionally, add an entry to the eventlog file. The following is an example:

    56 255

Note:

For this setting to take effect, you must restart the NetBackup services.

The parameters in the eventlog represent severity and type. The parameters have the following characteristics:

Severity

  • Listed as the first parameter.

  • Controls the messages that NetBackup writes to the Application log.

  • If the file is empty, the default severity is Error (16).

  • If the file has only one parameter, it is used for the severity level.

Type

  • Listed as the second parameter.

  • Controls the type of messages that NetBackup writes to the Application log.

  • If the file is empty, the default type is Backup Status (64).

Both parameters are specified as decimal numbers and equate to a bitmap that expresses the following values:

Severity

1 = Unknown

2 = Debug

4 = Info

8 = Warning

16 = Error

32 = Critical

Type

1 = Unknown

2 = General

4 = Backup

8 = Archive

16 = Retrieve

32 = Security

64 = Backup Status

128 = Media Device

You can configure the eventlog file to log the messages that include several different severities and types. If you specify an entry of 56 255 in the eventlog file, the results are as follows:

Entry 56

Produces a log with the messages that have a severity of warning, error, and critical. (56 = 8 + 16 + 32)

Entry 255

Produces a log with messages for all types. (255 = 1 + 2 + 4 + 8 + 16 + 32 + 64 +128)

The following example message is written in the Windows Event Viewer Application log:

16 4 10797 1 cacao bush nbpem backup of client bush exited with status 71

The definition of each value is as follows (left to right):

  • Severity = 16 (Error)

  • Type = 4 (Backup)

  • Job ID = 10797

  • Job group ID = 1

  • Server = cacao

  • Client = bush

  • Process = nbpem

  • Text = backup of client bush exited with status 71