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

Restore process

Understanding how the restore process works is a helpful first step in deciding which logs to gather for a particular issue. The restore process differs depending on whether you restore an image from tape or from disk.

Figure: Restore from tape process flow illustrates a restore from tape.

Figure: Restore from tape process flow

Restore from tape process flow

Restore procedure from tape

  1. The (1) NetBackup request daemon (bprd) receives a restore request. This request can be initiated from the Backup, Archive, and Restore user interface or from the (2) command line (bprestore).
  2. The bprd process launches two child processes: MAIN bprd and MPX-MAIN-bprd. The MAIN bprd process is used to identify images and media, while the MPX-MAIN-bprd process manages the restore operation. For simplicity's sake, these three processes are all referred to here as bprd.
  3. The bprd service communicates with the (3) NetBackup Database Manager program (bpdbm) to get the information that is required to restore the files that have been requested.
  4. Once it has the information it needs, bprd communicates with (4) bpjobd, and the job is added to the job list in the jobs database. The job is now visible in the Activity Monitor. It may show as "Active" even before resources are acquired.
  5. The bprd service goes through Private Branch Exchange (PBX) and the NetBackup Legacy Network (vnetd) to start the (5) NetBackup backup and restore manager (bpbrm).
  6. The bpbrm service starts the (6) tape management process (bptm) and provides the media information that is required for the restore. It also starts the (7) Tape Archive program (tar) on the client (through PBX and vnetd) and creates a connection between tar and bptm.
  7. The bptm process sends a resource request to the (8) NetBackup Job Manager (nbjm) through PBX and vnetd.
  8. The nbjm process sends the resource request to the (9) NetBackup Resource Broker (nbrb), which queries the (10) Enterprise Media Manager (nbemm). Once the resources have been allocated, nbrb notifies nbjm, which notifies bptm.
  9. The bptm process makes a mount request to the (11) logical tape interface daemon (ltid). The ltid service calls on the (12) robotic drive daemon (txxd, where xx varies based on the type of robot being used). The txxd daemon communicates the mount request to the (13) robotic control daemon (txxcd), which mounts the media.
  10. The bptm process reads the data to be restored from the media and delivers it to tar.
  11. The tar process writes the data to the client disk.
  12. When the restore is completed, bptm unmounts the media and notifies nbjm. The job now appears as "Done" in the Activity Monitor.

Some additional logs that are not included in the restore process flows but that may be of use in resolving restore problems include: reqlib, daemon, robots, and acsssi.

Figure: Restore from disk process flow illustrates a restore from disk.

Figure: Restore from disk process flow

Restore from disk process flow

Restore procedure from disk

  1. The (1) NetBackup request daemon (bprd) receives a restore request. This request can be initiated from the Backup, Archive, and Restore user interface or from the (2) command line (bprestore).
  2. The bprd process contacts the (3) NetBackup Database Manager program (bpdbm) to identify the files, the client, and the media information for the restore.
  3. The bprd process initiates a (4) child bprd process. The child bprd process makes a call to the (5) Enterprise Media Manager (nbemm) to verify that the disk storage unit is available.
  4. The child bprd process communicates with (6) bpjobd to allocate a jobid. The restore job is now visible in the Activity Monitor.
  5. The bprd process starts the (7) NetBackup backup and restore manager (bpbrm) on the media server, through Private Branch Exchange (PBX) and the NetBackup Legacy Network Service (vnetd).
  6. The bpbrm service uses PBX and vnetd to establish a connection with the (8) Tape Archive program (tar) on the client system. It also starts the (9) tape management process (bptm).
  7. The bptm process makes a call to bpdbm (through PBX and vnetd) to get the fragment information and then mounts the disk.
  8. The bptm process reads the backup image from the disk and streams the requested data to tar.
  9. The tar process commits the data to the storage destination.

Each of the processes that is involved in a restore has an accompanying log file. These logs can be consulted to diagnose any issues that you encounter with your restore.