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

SAN Client Fiber Transport restore

Figure: SAN client restore with Fibre Transport

SAN client restore with Fibre Transport

The process flow for a SAN client restore is as follows (in the order presented).

  • When the user starts a restore, NetBackup invokes the client's bprestore program that sends a request to the request daemon, bprd. This request identifies the files and client. The request daemon then uses bpcd (client daemon) to start the backup and restore manager (bpbrm).

    Note:

    To restore Backup Exec images, bpbrm invokes mtfrd.exe instead of tar32.exe on the clients. The server processes are the same as those used for NetBackup restores.

  • If the disk or tape where the data resides attaches to the master server, then bprd starts the backup and restore manager on the master server. If the disk unit or tape unit connects to a media server, bprd starts the backup and restore manager on the media server.

  • bpbrm starts bptm and provides bptm with the backup ID and the shmfat (shared memory) flag.

  • bptm does the following:

    • Requests the SAN client information from the Job Manager service (nbjm).

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

    • Sends a restore request to the FT client process on the client (nbftclnt). nbftclnt 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.

  • bpbrm starts tar by means of bpcd and provides tar with the backup ID, socket information, and the shmfat (shared memory) flag.

  • bptm does the following:

    • Reads the image from the storage device.

    • Creates a bptm child process. This process filters the backup image so that only the files that are selected for the restore are sent to the client.

    • Writes the image data to the shared buffer on the server.

    • When the buffer is full or the job is done, it sets the buffer flag (partial buffers may be sent to the client).

  • tar does the following:

    • Sends the status and control information to bpbrm.

    • Reads the shared memory information from the local backup ID file (waits for the file to exist and become valid).

    • Waits for the buffer flag that indicates the data is ready to be read.

    • Reads the data from the buffer, extracts files, and restores them. When the shmfat (shared memory) flag is provided, tar considers the data to be already filtered.

  • The FT Server process nbftsrvr waits for the shared memory buffer flag to be set. nbftsrvr then transfers the image data to the FT client (nbftclnt) shared memory buffer, and clears the buffer flag.

  • The FT client (nbftclnt) waits for the data from nbftsrvr and writes the data to the shared memory buffer on the client. nbftclnt then sets the buffer flag.

  • At the end of the job:

    • bptm informs tar and bpbrm that the job is complete.

    • bptm directs nbftclnt to close the Fibre Channel connection.

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