Veritas NetBackup™ 8.0 Troubleshooting Guide

Last Published:
Product(s): NetBackup (8.0)
  1. Introduction
    1.  
      Recent changes to this guide
    2.  
      Troubleshooting a problem
    3.  
      Problem report for Technical Support
    4.  
      About gathering information for NetBackup-Java applications
  2. Troubleshooting procedures
    1.  
      About troubleshooting procedures
    2. Troubleshooting NetBackup problems
      1.  
        Verifying that all processes are running on UNIX servers
      2.  
        Verifying that all processes are running on Windows servers
    3.  
      Troubleshooting installation problems
    4.  
      Troubleshooting configuration problems
    5.  
      Device configuration problem resolution
    6.  
      Testing the master server and clients
    7.  
      Testing the media server and clients
    8.  
      Resolving network communication problems with UNIX clients
    9.  
      Resolving network communication problems with Windows clients
    10.  
      About troubleshooting networks and host names
    11. Verifying host name and service entries in NetBackup
      1.  
        Example of host name and service entries on UNIX master server and client
      2.  
        Example of host name and service entries on UNIX master server and media server
      3.  
        Example of host name and service entries on UNIX PC clients
      4.  
        Example of host name and service entries on UNIX server that connects to multiple networks
    12.  
      About the bpclntcmd utility
    13.  
      Using the Host Properties window to access configuration settings
    14.  
      Resolving full disk problems
    15. Frozen media troubleshooting considerations
      1.  
        Logs for troubleshooting frozen media
      2.  
        About the conditions that cause media to freeze
    16. Troubleshooting problems with the NetBackup web services
      1.  
        Viewing NetBackup web services logs
    17.  
      Troubleshooting problems with the NetBackup web server certificate
    18. Resolving PBX problems
      1.  
        Checking PBX installation
      2.  
        Checking that PBX is running
      3.  
        Checking that PBX is set correctly
      4.  
        Accessing the PBX logs
      5.  
        Troubleshooting PBX security
      6.  
        Determining if the PBX daemon or service is available
    19. About troubleshooting Auto Image Replication
      1.  
        Troubleshooting Auto Image Replication
      2.  
        About troubleshooting automatic import jobs
    20.  
      Troubleshooting network interface card performance
    21.  
      About SERVER entries in the bp.conf file
    22.  
      About unavailable storage unit problems
    23.  
      Resolving a NetBackup Administration operations failure on Windows
    24.  
      Resolving garbled text displayed in NetBackup Administration Console on a UNIX computer
  3. Using NetBackup utilities
    1.  
      About NetBackup troubleshooting utilities
    2.  
      About the analysis utilities for NetBackup debug logs
    3.  
      About network troubleshooting utilities
    4. About the NetBackup support utility (nbsu)
      1.  
        Output from the NetBackup support utility (nbsu)
      2.  
        Status code information gathered by the NetBackup support utility (nbsu)
      3.  
        Example of a progress display for the NetBackup support utility (nbsu)
    5. About the NetBackup consistency check utility (NBCC)
      1.  
        Output from the NetBackup consistency check utility (NBCC)
      2.  
        Example of an NBCC progress display
    6.  
      About the NetBackup consistency check repair (NBCCR) utility
    7.  
      About the nbcplogs utility
    8. About the robotic test utilities
      1.  
        Robotic tests on UNIX
      2.  
        Robotic tests on Windows
  4. Disaster recovery
    1.  
      About disaster recovery
    2.  
      Recommended backup practices
    3. About disk recovery procedures for UNIX and Linux
      1. About recovering the master server disk for UNIX and Linux
        1.  
          Recovering the master server when root is intact
        2.  
          Recovering the master server when the root partition is lost
      2.  
        About recovering the NetBackup media server disk for UNIX
      3.  
        Recovering the system disk on a UNIX client workstation
    4. About clustered NetBackup server recovery for UNIX and Linux
      1.  
        Replacing a failed node on a UNIX or Linux cluster
      2.  
        Recovering the entire UNIX or Linux cluster
    5. About disk recovery procedures for Windows
      1. About recovering the master server disk for Windows
        1.  
          Recovering the master server with Windows intact
        2.  
          Recovering the master server and Windows
      2.  
        About recovering the NetBackup media server disk for Windows
      3.  
        Recovering a Windows client disk
    6. About clustered NetBackup server recovery for Windows
      1.  
        Replacing a failed node on a Windows VCS cluster
      2.  
        Recovering the shared disk on a Windows VCS cluster
      3.  
        Recovering the entire Windows VCS cluster
    7. About recovering the NetBackup catalog
      1.  
        About NetBackup catalog recovery on Windows computers
      2.  
        About NetBackup catalog recovery from disk devices
      3.  
        About NetBackup catalog recovery and symbolic links
      4. About NetBackup catalog recovery and OpsCenter
        1.  
          Specifying the NetBackup job ID number after a catalog recovery
      5.  
        NetBackup disaster recovery email example
      6. About recovering the entire NetBackup catalog
        1.  
          Recovering the entire NetBackup catalog using the Catalog Recovery Wizard
        2.  
          Recovering the entire NetBackup catalog using bprecover -wizard
      7. About recovering the NetBackup catalog image files
        1.  
          Recovering the NetBackup catalog image files using the Catalog Recovery Wizard
        2.  
          Recovering the NetBackup catalog image files using bprecover -wizard
      8. About recovering the NetBackup relational database
        1.  
          Recovering NetBackup relational database files from a backup
        2.  
          Recovering the NetBackup relational database files from staging
        3.  
          About processing the relational database in staging
      9.  
        Recovering the NetBackup catalog when NetBackup Access Control is configured
      10.  
        Recovering the NetBackup catalog from a nonprimary copy of a catalog backup
      11.  
        Recovering the NetBackup catalog without the disaster recovery file
      12.  
        Recovering a NetBackup user-directed online catalog backup from the command line
      13.  
        Restoring files from a NetBackup online catalog backup
      14.  
        Unfreezing the NetBackup online catalog recovery media

About troubleshooting automatic import jobs

The automatic import jobs that the storage lifecycle policy (SLP) components manage are different from legacy import jobs. Automatic import jobs asynchronously notify NetBackup that an image needs to be imported. Also, Auto Image Replication jobs provide catalog entries to the storage device so that the job does not have to read the entire image. An automatic import job reads the catalog record off the storage device and adds it into its own catalog. This process is so fast that NetBackup batches images for import for efficiency. A pending import is the state where NetBackup has been notified, but the import has not yet occurred.

More information is available about automatic import and how to tune the batch interval of the import manager process.

See the NetBackup Administrator's Guide, Volume I.

The notify event from the storage server provides the following: the image name, the storage server location to read the catalog for this image, and the name of the SLP that processes the image. Images for automatic import jobs are batched by storage lifecycle policy name and disk volume. The import job consumes an input-output stream on the disk volume.

To view the images that are pending import, run the following command:

# nbstlutil pendimplist -U
Image:
 Master Server            : bayside.example.com
 Backup ID                : gdwinlin04_1280299412
 Client                   : gdwinlin04
 Backup Time              : 1280299412 (Wed Jul 28 01:43:32 2010)
 Policy                   : (none specified)
 Client Type              : 0
 Schedule Type            : 0
 Storage Lifecycle Policy : (none specified)
 Storage Lifecycle State  : 1 (NOT_STARTED) 
 Time In Process          : 0 (Wed Dec 31 18:00:00 1969)
 Data Classification ID   : (none specified)
 Version Number           : 0
 OriginMasterServer       : master_tlk
 OriginMasterServerID     : 00000000-0000-0000-0000-000000000000
 Import From Replica Time : 0 (Wed Dec 31 18:00:00 1969)
 Required Expiration Date : 0 (Wed Dec 31 18:00:00 1969)
 Created Date Time        : 1287678771 (Thu Oct 21 11:32:51 2010)

 Copy:
   Master Server       : bayside.example.com
   Backup ID           : gdwinlin04_1280299412
   Copy Number         : 1
   Copy Type           : 4
   Expire Time         : 0 (Wed Dec 31 18:00:00 1969)
   Expire LC Time      : 0 (Wed Dec 31 18:00:00 1969)
   Try To Keep Time    : 0 (Wed Dec 31 18:00:00 1969)
   Residence           : (none specified)
   Copy State          : 1 (NOT_STARTED) 
   Job ID              : 0
   Retention Type      : 0 (FIXED) 
   MPX State           : 0 (FALSE)
   Source              : 0
   Destination ID      : 
   Last Retry Time     : 0

   Fragment:
     Master Server     : bayside.example.com
     Backup ID         : gdwinlin04_1280299412
     Copy Number       : 1
     Fragment Number   : -2147482648
     Resume Count      : 0
     Media ID          : @aaaab
     Media Server      : bayside.example.com
     Storage Server    : bayside.example.com
     Media Type        : 0 (DISK) 
     Media Sub-Type    : 0 (DEFAULT) 
     Fragment State    : 1 (ACTIVE) 
     Fragment Size     : 0
     Delete Header     : 1
     Fragment ID       : gdwinlin04_1280299412_C1_IM

The action to take on the automatic import job and the automatic import event depends on several conditions as shown in the following table.

Action

Condition

Automatic import jobs queue

No media server or I/O stream is available for this disk volume.

Automatic import jobs never start (copy stays at storage lifecycle state 1)

  • The storage lifecycle policy is inactive.

  • The storage lifecycle policy import destination is inactive.

  • The storage lifecycle policy is between sessions.

  • The image has exceeded the extended retry count and the extended retry time has not passed.

Automatic import event is discarded and the image is ignored

  • The event specifies a backup ID that already exists in this master server catalog.

  • The event specifies a disk volume that is not configured in NetBackup for this storage server.

Automatic import job is started but the image is expired and deleted to clean up disk space in some cases. The event logs an error in the Problems Report or bperror output. An import job runs, but the import for this image fails showing a status code in the range 1532 - 1535.

  • The storage lifecycle policy that is specified in the event does not contain an import destination.

  • The storage lifecycle policy that is specified in the event has an import destination with a residence that does not include the disk volume that is specified by the event.

  • The storage lifecycle policy that is specified does not exist. By default, the Storage Lifecycle Policies utility automatically creates a storage lifecycle policy with the correct name. Ensure that a storage lifecycle policy with the same case-sensitive name exists in the target master server.

    More information is available for the storage lifecycle policy configuration options.

    See the NetBackup Administrator's Guide, Volume I.

Look at the Problems Report or the bperror list for these cases.

For troubleshooting job flow for automatic import jobs, use the same command lines as you would for other storage lifecycle policy managed jobs. To list images for which NetBackup has received notification from storage but not yet initiated import (either pending or failed), use the commands that were previously noted or run the following command:

# nbstlutil list -copy_type import -U -copy_incomplete

To list the images that have been automatically imported, run the following command:

# nbstlutil list -copy_type import -U -copy_state 3 -U
Master Server             : bayside.example.com
 Backup ID                : woodridge_1287610477
 Client                   : woodridge
 Backup Time              : 1287610477 (Wed Oct 20 16:34:37 2010)
 Policy                   : two-hop-with-dup
 Client Type              : 0
 Schedule Type            : 0
 Storage Lifecycle Policy : woodridge2bayside2pearl_withdup
 Storage Lifecycle State  : 3 (COMPLETE) 
 Time In Process          : 1287610714 (Wed Oct 20 16:38:34 2010)
 Data Classification ID   : (none specified)
 Version Number           : 0
 OriginMasterServer       : woodridge.example.com
 OriginMasterServerID     : f5cec09a-da74-11df-8000-f5b3612d8988
 Import From Replica Time : 1287610672 (Wed Oct 20 16:37:52 2010)
 Required Expiration Date : 1290288877 (Sat Nov 20 15:34:37 2010)
 Created Date Time        : 1287610652 (Wed Oct 20 16:37:32 2010)

The OriginMasterServer, OriginMasterServerID, Import From Replica Time, and Required Expiration Date are not known until after the image is imported so a pending record may look like the following:

Image:
 Master Server            : bayside.example.com
 Backup ID                : gdwinlin04_1280299412
 Client                   : gdwinlin04
 Backup Time              : 1280299412 (Wed Jul 28 01:43:32 2010)
 Policy                   : (none specified)
 Client Type              : 0
 Schedule Type            : 0
 Storage Lifecycle Policy : (none specified)
 Storage Lifecycle State  : 1 (NOT_STARTED) 
 Time In Process          : 0 (Wed Dec 31 18:00:00 1969)
 Data Classification ID   : (none specified)
 Version Number           : 0
 OriginMasterServer       : master_tlk
 OriginMasterServerID     : 00000000-0000-0000-0000-000000000000
 Import From Replica Time : 0 (Wed Dec 31 18:00:00 1969)
 Required Expiration Date : 0 (Wed Dec 31 18:00:00 1969)
 Created Date Time        : 1287680533 (Thu Oct 21 12:02:13 2010)

The OriginMasterServer here is not empty, although it may be in some cases. In cascading Auto Image Replication, the master server sends the notification.