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

Resolving network communication problems with Windows clients

The following procedure is for resolving NetBackup communications problems, such as those associated with NetBackup status codes 54, 57, and 58. This procedure consists of two variations: one for UNIX clients and another for Windows clients.

Note:

In all cases, ensure that your network configuration works correctly outside of NetBackup before trying to resolve NetBackup problems.

This procedure helps you resolve network communication problems with PC clients.

To resolve network communication problems

  1. Before you retry the failed operation, do the following:

    • Increase the logging level on the client (see the NetBackup Administrator's Guide, Volume I, under "Client Settings properties").

    • On the NetBackup master server, create a bprd debug log directory and on the clients create a bpcd debug log.

    • On the NetBackup server, set the Verbose level to 1.

      See the NetBackup Logging Reference Guide for help changing the logging level.

  2. If this client is new, verify the client and the server names in your NetBackup configuration.

    See Verifying host name and service entries in NetBackup.

  3. Verify network connectivity between client and server by pinging from the server to the client and vice versa. Use the following command:
    # ping hostname

    Where hostname is the name of the host as configured in the following:

    • NetBackup policy configuration

    • WINS

    • DNS (if applicable).

    • hosts file in system directory %SystemRoot%\system32\drivers \etc\hosts (Windows 2003 or 2008)

    If ping succeeds in all instances, it verifies connectivity between the server and client.

    If ping fails, you have a network problem outside of NetBackup that must be resolved before you proceed. As a first step, verify that the workstation is turned on. A workstation that is not turned on is a common source of connection problems with workstations.

  4. On Microsoft Windows clients, ensure that the NetBackup Client service is active by checking the logs. Use the Services application in the Control Panel to verify that the NetBackup Client service is running. Start it if necessary.

    • Check the bpcd debug logs for problems or errors. See the NetBackup Logging Reference Guide on how to enable and use these logs.

    • Verify that the same NetBackup client service (bpcd) port number is specified on both the NetBackup client and server (by default, 13782). Do one of the following:

      Windows

      Check the NetBackup client service port number.

      Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box on the Network tab, check the NetBackup client service port number.

      Verify that the setting on the Network tab matches the one in the services file. The services file is located in:

      %SystemRoot%\system32\drivers\etc\services (Windows)

      The values on the Network tab are written to the services file when the NetBackup client service starts.

      UNIX NetBackup servers

      The bpcd port number is in the /etc/services file. On Windows NetBackup servers, see the Client Properties dialog box in the Host Properties window.

      See Using the Host Properties window to access configuration settings.

      Correct the port number if necessary. Then, on Windows clients and servers, stop and restart the NetBackup Client service.

      Do not change NetBackup port assignments unless it is necessary to resolve conflicts with other applications. If you do change them, do so on all NetBackup clients and servers. These numbers must be the same throughout your NetBackup configuration.

  5. Verify that the NetBackup Request Service (bprd) port number on Microsoft Windows is the same as on the server (by default, 13720). Do one of the following:

    Windows clients

    Check the NetBackup client service port number.

    Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box on the Network tab, check the NetBackup client service port number.

    Verify that the setting on the Network tab matches the one in the services file. The services file is located in:

    %SystemRoot%\system32\drivers\etc\services (Windows)

    The values on the Network tab are written to the services file when the NetBackup client service starts.

    UNIX NetBackup servers

    The bprd port number is in the /etc/services file.

    See Using the Host Properties window to access configuration settings.

    Windows NetBackup servers

    Set these numbers in the Client Properties dialog box in the Host Properties window.

    See Using the Host Properties window to access configuration settings.

  6. Verify that the hosts file or its equivalent contains the NetBackup server name. The hosts files are the following:

    Windows 2003

    %SystemRoot%\system32\drivers\etc\hosts

    UNIX

    /etc/hosts

  7. Verify client-to-server connectability by means of ping or its equivalent from the client (step 3 verified the server-to-client connection).
  8. If the client's TCP/IP transport allows telnet and ftp from the server, try these services as additional connectivity checks.
  9. Use the bpclntcmd utility to verify client to master server communications. When the -pn and -sv options run on a client, they initiate inquiries to the master server (configured in the server list on the client). The master server then returns information to the requesting client.

    See About the bpclntcmd utility.

  10. Use the bptestbpcd utility to try to establish a connection from a NetBackup server to the bpcd daemon on another NetBackup system. If successful, it reports information about the sockets that are established.
  11. Verify that the client operating system is one of those supported by the client software.