Veritas NetBackup™ Logging Reference Guide

Last Published:
Product(s): NetBackup (8.1.1, 8.1)
  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. 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. Snapshot technologies
    1.  
      Snapshot Client backup
    2.  
      VMware backup
    3.  
      Snapshot backup and Windows open file backups
  11. 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
  12. 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

Deduplication backup process to the Media Server Deduplication Pool (MSDP)

The deduplication backup process to the Media Server Deduplication Pool (MSDP) is as follows:

  • The client bpbkar sends data to the NetBackup backup tape manager - the bptm process

  • pdvfs (using bptm as a proxy) connects to the NetBackup Deduplication Manager (spad) to record metadata (image records) in the spadb mini-catalog and connects to the NetBackup Deduplication Engine (spoold) to store the image data in the .bhd/.bin files in the data directory (dedup_path\data)

  • spoold writes tlogs to the .tlog files in the queue (dedupe_path\queue) directory and to the processed directory. The tlog data from the queue directory is processed into the crdb later when the next content router queue processing job runs. Beginning with NetBackup 7.6, .tlog files do not contain additions to the database.

The functional overview is as follows:

Figure: Deduplication configuration for MSDP

Deduplication configuration for MSDP

In this scenario, the client backs up data directly to the media server and the media server deduplicates the data before it stores it locally. Ensure that this is on the correct media server which is not always the same as the MSDP storage server (due to load balancing).

For deduplication-specific logging, enable the following on the media server:

  1. Verbose 5 bptm logging:

    • Create a log directory named bptm in /usr/openv/netbackup/logs (Windows: install_path\NetBackup\logs)

    • Set the bptm log verbosity to 5 in the NetBackup Administration Console. To do this, click on Host Properties > Logging for the media server. If you use UNIX/Linux, set the bptm log verbosity to 5 in the /usr/openv/netbackup/bp.conf file by appending the following line:

      BPTM_VERBOSE = 5
    • Edit the pd.conf configuration file that is located at:

      Windows:

      install_path\NetBackup\bin\ost-plugins\pd.conf

      UNIX/Linux:

      /usr/openv/lib/ost-plugins/pd.conf

      and uncomment and/or modify the following line:

      LOGLEVEL = 10

      Note:

      You can also modify DEBUGLOG in the pd.conf file to specify a path to which to log; however, we recommend leaving the DEBUGLOG entry commented out. The logging information (PDVFS debug logging) then logs to the bptm and bpdm logs.

  2. Enable verbose spad/spoold logging (optional).

    • Edit the dedup_path\etc\puredisk\spa.cfg and dedup_path\etc\puredisk\contentrouter.cfg files so that the following line:

      Logging=long,thread is changed to Logging=full,thread

    • Ensure that you are on the correct media server and restart the MSDP storage server services.

    Caution:

    If you enable verbose logging, it can impact the performance on MSDP.

  3. Reproduce the backup failure.

  4. Within the NetBackup Administration Console, click on Activity Monitor > Jobs, open the job details and click the Detailed Status tab. It displays the media server host name that ran the backup and the bptm process ID number (PID).

    • Find a line similar to bptm(pid=value); this value is the bptm PID to locate in the bptm log.

  5. Extract the bptm PID found in step 3 from the bptm log on the media server. This step only gathers the single-line entries; review the raw logs to see the multi-line log entries. In the following examples, 3144 is the bptm PID:

    • Windows command line:

      findstr "\[3144." 092611.log > bptmpid3144.txt
      
    • UNIX/Linux command line:

      grep "\[3144\]" log.092611 > bptmpid3144.txt
      
  6. Gather the spoold session logs that cover the dates from when the backup started and when it failed from the following logs:

    Windows:

    <dedup_path>\log\spoold\<mediasvr_IP_or_hostname>\bptm\Receive\MMDDYY.log
    <dedup_path>\log\spoold\<mediasvr_IP_or_hostname>\bptm\Store\MMDDYY.log

    UNIX/Linux:

    <dedup_path>/log/spoold/<mediasvr_IP_or_hostname>/bptm/Receive/MMDDYY.log
    <dedup_path>/log/spoold/<mediasvr_IP_or_hostname>/bptm/Store/MMDDYY.log