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

SAN Client Fiber Transport backup

The following shows a SAN client backup process.

For backups to disk, the SAN client feature provides high-speed data movement between NetBackup media servers and NetBackup SAN-attached clients. SAN-attached clients send backup data to the media server by means of Fibre Channel connections.

As part of SAN client, the FT Service Manager (FSM) is a domain layer service that resides on the master server. The FSM provides discovery, configuration, and event monitoring of SAN client resources. The FSM collects Fibre Channel information from the client and from the media server; FSM then populates the NetBackup relational database (NBDB) with the information. FSM runs as a sub-process of NBDB and writes log messages to the NBDB log. FSM interacts with the nbftclnt process on NetBackup clients and with the nbftsrvr process on media servers.

Figure: SAN client backup process flow

SAN client backup process flowSAN client backup process flow

The processing steps for a SAN client backup operation are the following:

SAN client backup procedure

  1. The NetBackup master server or primary client initiates the backup. The NetBackup request daemon (bprd) submits a backup request to the Policy Execution Manager (nbpem). nbpem processes the policy configurations.

    All other daemons and programs are started as necessary including nbpem, nbjm, nbrb, and nbemm.

  2. The Policy Execution Manager service (nbpem) does the following:
    • Gets the policy list from bpdbm.

    • Builds a work list of all scheduled jobs.

    • Computes the due time for each job.

    • Sorts the work list in order of due time.

    • Submits to nbjm all jobs that are currently due.

    • Sets a wake-up timer for the next due job.

    • When the job finishes, it recomputes the due time of the next job and submits to nbjm all of the jobs that are currently due.

  3. The Job Manager service (nbjm) requests backup resources from the Resource Broker (nbrb), that returns information on the use of shared memory for the SAN client.
  4. The nbjm service starts the backup by means of the client daemon bpcd, which starts the backup and restore manager bpbrm.
  5. The bpbrm service starts bptm, which does the following:
    • Requests the SAN client information from nbjm.

    • Sends a backup request to the FT server process (nbftsrvr).

    • Sends a backup request to the FT client process on the client (nbftclnt), that does the following: Opens a Fibre Channel connection to nbftsrvr on the media server, allocates the shared memory, and writes the shared memory information to the backup ID file.

  6. The bpbrm service uses bpcd to start bpbkar, that does the following:
    • Reads the shared memory information from the BID file (waits for the file to exist and become valid).

    • Sends the information about files in the image to bpbrm.

    • Writes the file data to bpbkar, optionally compresses it, then writes the data to the shared buffer.

    • Sets the buffer flag when the buffer is full or the job is done.

  7. The FT client process (nbftclnt) waits for the shared memory buffer flag to be set. It then transfers the image data to the FT Server (nbftsrvr) shared memory buffer, and clears the buffer flag.
  8. The nbftsrvr service waits for data from nbftclnt; and writes the data is written to the shared memory buffer. When the transfer completes, nbftsrvr sets the buffer flag.
  9. bptm waits for the shared memory buffer flag to be set, writes data from the buffer to the storage device, and clears the buffer flag.
  10. At the end of the job:
    • bpbkar informs bpbrm and bptm that the job is complete.

    • bptm sends bpbrm the final status of the data write.

    • bptm directs nbftclnt to close the Fibre Channel connection.

    • nbftclnt closes the Fibre Channel connection and deletes the BID file.