Veritas NetBackup™ Logging Reference Guide

Last Published:
Product(s): NetBackup (9.0.0.1, 9.0)
  1. Using logs
    1.  
      About logging
    2.  
      Logging levels
    3.  
      Log retention and log size
    4. Changing the logging levels
      1.  
        Set the Media Manager debug logging to a higher level
      2.  
        Changing the logging level on Windows clients
    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.  
        Examples of using vxlogview to view unified logs
      10.  
        Examples of using vxlogmgr to manage unified logs
      11.  
        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.  
      Setting retention limits for logs on clients
    8.  
      UNIX logging with syslogd
    9.  
      Logging options with the Windows Event Viewer
  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 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 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.  
        Logs to accompany problem reports for synthetic backups
      2.  
        Creating legacy log directories to accompany problem reports for synthetic backup
  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. Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
    1.  
      About storage lifecycle policies (SLPs) and Auto Image Replication (A.I.R.)
    2.  
      Storage lifecycle policy (SLP) duplication process flow
    3.  
      Automatic Image Replication (A.I.R.) process flow logging
    4.  
      Import process flow
    5.  
      SLP and A.I.R. logging
    6.  
      SLP configuration and management
  10. NetBackup secure communication logging
    1.  
      About NetBackup secure communication logging
    2.  
      Tomcat logging
    3.  
      NetBackup web services logging
    4.  
      Command-line logging
    5.  
      NetBackup cURL logging
    6.  
      Java logging
    7.  
      Embeddable Authentication Client (EAT) logging
    8.  
      Authentication Services (AT) logging
    9.  
      vssat logging
    10. NetBackup proxy helper logging
      1.  
        Originator ID 486
    11. NetBackup proxy tunnel logging
      1.  
        Originator ID 490
    12.  
      PBX logging
    13.  
      Sending secure communication logs to Veritas Technical Support
  11. Snapshot technologies
    1.  
      Snapshot Client backup
    2.  
      VMware backup
    3.  
      Snapshot backup and Windows open file backups
  12. Locating logs
    1.  
      Overview of NetBackup log locations and processes
    2.  
      acsssi logging
    3.  
      bpbackup logging
    4.  
      bpbkar logging
    5.  
      bpbrm logging
    6.  
      bpcd logging
    7.  
      bpcompatd logging
    8.  
      bpdbm logging
    9.  
      bpjobd logging
    10.  
      bprd logging
    11.  
      bprestore logging
    12.  
      bptestnetconn logging
    13.  
      bptm logging
    14.  
      daemon logging
    15.  
      ltid logging
    16.  
      nbemm logging
    17.  
      nbjm logging
    18.  
      nbpem logging
    19.  
      nbproxy logging
    20.  
      nbrb logging
    21.  
      NetBackup Vault logging
    22.  
      NetBackup web services logging
    23.  
      NetBackup web server certificate logging
    24.  
      PBX logging
    25.  
      reqlib logging
    26.  
      Robots logging
    27.  
      tar logging
    28.  
      txxd and txxcd logging
    29.  
      vnetd logging
  13. NetBackup Administration Console logging
    1.  
      NetBackup Administration Console logging process flow
    2.  
      Enabling detailed debug logging for the NetBackup Administration Console
    3.  
      Setting up a secure channel between the NetBackup Administration Console and bpjava-*
    4.  
      Setting up a secure channel between the NetBackup Administration Console and either nbsl or nbvault
    5.  
      NetBackup Administration Console logging configuration on NetBackup servers and clients
    6.  
      Logging Java operations for the NetBackup Remote Administration Console
    7.  
      Configuring and gathering logs when troubleshooting NetBackup Administration Console issues
    8.  
      Undo logging
  14. Using the Logging Assistant
    1.  
      About the Logging Assistant
    2.  
      Logging Assistant sequence of operation
    3.  
      Viewing the Logging Assistant records
    4.  
      Adding or deleting a Logging Assistant record
    5.  
      Setting up debug logging
    6.  
      Set minimum debug logging
    7.  
      Disabling debug logging

Originator ID 486

The NetBackup proxy helper log files are useful when there are issues with communication due to SSL/TSL errors or other secure communication issues. You can start the processes by using the vnetd - standalone command. If there are startup and shutdown issues, examine the vnetd log file.

The following are examples of the expected minimum number of vnetd processes:

/usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0
/usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0
/usr/openv/netbackup/bin/vnetd  - standalone

The inbound and outbound proxy processes send logs to the nbpxyhelper log files. The communication between them can be followed through the job details; it locates the :INBOUND or :OUTBOUND connection ID and searches for them in the nbpxyhelper log files. The :INBOUND and :OUTBOUND connections are only displayed if there is an error. See the following example:

Aug 5, 2018 5:13:14 PM - Info nbjm (pid=3442) starting backup job (jobid=268) for 
  client nbclient1, policy ANY_nbclient1, schedule Full-EXPIRE_IMMEDIATELY
Aug 5, 2018 5:13:14 PM - Info nbjm (pid=3442) requesting STANDARD_RESOURCE resources from RB
  for backup job (jobid=268, request id:{5DD92BD0-98F4-11E8-AEE4-55B66A58DDB2})
Aug 5, 2018 5:13:14 PM - requesting resource  __ANY__
Aug 5, 2018 5:13:14 PM - requesting resource  nbmaster2.NBU_CLIENT.MAXJOBS.nbclient1
Aug 5, 2018 5:13:14 PM - requesting resource  nbmaster2.NBU_POLICY.MAXJOBS.ANY_nbclient1
Aug 5, 2018 5:13:15 PM - Error bpbrm (pid=21177) [PROXY] Connecting host: nbmaster2
Aug 5, 2018 5:13:15 PM - Error bpbrm (pid=21177) [PROXY] ConnectionId: 
  {5E0FBBD2-98F4-11E8-804A-EC7198374CC6}:OUTBOUND

By default, OID 486 is set to DebugLevel=0 due to the potential to create many log files. Do not leave the logging enabled for long periods of time at DebugLevel=6.

The logging level can be changed by using the vxlogcfg command. See the following examples:

To add logging, use the following command:

vxlogcfg -a -p NB -o 486 -s DebugLevel=6

To remove logging, use the following command:

vxlogcfg -a -p NB -o 486 -s DebugLevel=0

Note:

In this case, the logging level is being explicitly set to 0 after the troubleshooting is finished.