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

Verifying host name and service entries in NetBackup

This procedure is useful if you encounter problems with host names or network connections and want to verify that the NetBackup configuration is correct. Several examples follow the procedure.

For more information on host names, see the NetBackup Administrator's Guide, Volume II.

See About troubleshooting networks and host names.

To verify the host name and service entries in NetBackup

  1. Verify that the correct client and server host names are configured in NetBackup. The action you take depends on the computer that you check.

    On Windows servers and Windows clients

    Do the following:

    • On the Server to use for backups and restores drop-down list, ensure that a server entry exists for the master server and each media server.

      Start the Backup, Archive, and Restore interface on the client. On the File menu, click Specify NetBackup Machines and Policy Type. In the Specify NetBackup Machines and Policy Type dialog box, click the Server to use for backups and restores drop-down list.

      On Windows computers, the correct server must be designated as the current master server in the list. If you add or modify server entries on the master server, stop and restart the NetBackup Request service and NetBackup Database Manager services.

    • On the General tab, verify that the client name setting is correct and matches what is in the policy client list on the master server.

      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, click the General tab.

    • On a master or a media server, ensure that a server entry exists for each Windows administrative client to use to administer that server.

    • Ensure that host names are spelled correctly in the bp.conf file (UNIX) or in the servers list (Windows) on the master server. If a host name is misspelled or cannot be resolved with gethostbyname, the following error messages are logged on the NetBackup error log:

      Gethostbyname failed for 
      <host_name>:<h_errno_string> (<h_errno>)
      One or more servers was excluded from the server 
      list because gethostby name() failed.

    You can also make these changes on the appropriate tabs in the properties dialog boxes on a Windows NetBackup server

    See Using the Host Properties window to access configuration settings.

    On UNIX NetBackup servers and clients

    Check the server and the client name entries in the bp.conf file by doing the following:

    • Ensure that a SERVER entry exists for the master server and each media server in the configuration. The master server must be the first name in the list.

      If you add or modify SERVER entries on the master server, stop and restart bprd and bpdbm before the changes take effect.

    • The bp.conf of the master server does not require the addition of other clients, other than the master server as CLIENT_NAME = master server name. The name is added by default.

    The bp.conf file is in the /usr/openv/netbackup directory on UNIX clients.

    UNIX client users can also have a personal bp.conf file in their home directory. A CLIENT_NAME option in $HOME/bp.conf overrides the option in /usr/openv/netbackup/bp.conf.

    On the master server

    Verify that you have created any of the following required files:

    • install_path\NetBackup\db\altnames files (Windows)

    • /usr/openv/netbackup/db/altnames files (UNIX)

    Pay particular attention to requirements for host.xlate file entries.

  2. Verify that each server and client have the required entries for NetBackup reserved port numbers.

    The following examples show the default port numbers.

    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.

  3. On NetBackup servers, check the services files to ensure that they have entries for the following:

    Verify the NetBackup client daemon or service number, and the request daemon or service port number. The action you take depends on whether the client is UNIX or Microsoft Windows.

    On UNIX clients

    Check the bprd and the bpcd entries in the /etc/services file.

    On Microsoft Windows clients

    Verify that the NetBackup Client Service Port number and NetBackup Request Service Port number match settings in the services file by doing the following:

    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, select the following: The NetBackup Client Service Port number and NetBackup Request Service Port number.

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

    The services file is in the following location:

    %SystemRoot%\system32\drivers\etc\services

  4. On UNIX servers and clients, ensure that the bpcd -standalone process is running.

  5. On Windows servers and clients, verify that the NetBackup Client service is running.
  6. If you use NIS in your network, update those services to include the NetBackup information that is added to the /etc/services file.
  7. NIS, WINS, or DNS host name information must correspond to what is in the policy configuration and the name entries. On Windows NetBackup servers and Microsoft Windows clients, do the following:

    • Check the General tab:

      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, click the General tab.

    • Check the Server to use for backups and restores drop-down list:

      Start the Backup, Archive, and Restore interface on the client. On the File menu, click Specify NetBackup Machines and Policy Type. In the Specify NetBackup Machines and Policy Type dialog box, click the Server to use for backups and restores drop-down list.

    • Check the bp.conf file on UNIX servers and clients.

    • Verify that reverse DNS addressing is configured.

  8. Use the bpclntcmd utility to confirm the setup of the IP addresses and host names in DNS, NIS, and local hosts files on each NetBackup node.

    Note:

    FT (Fibre Transport) target devices are named based on the host name or domain name response from the device. If any alternate computer names for different VLAN network interface names appear in the SERVER/MEDIA_SERVER entries of the DNS (Domain Name System) or the host files, the primary name must appear first.

    See About the bpclntcmd utility.