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

Recovering a Windows client disk

The following procedure explains how to perform a total recovery of a Windows NetBackup client in the event of a system disk failure.

NetBackup Bare Metal Restore (BMR) protects client systems by backing them up with a policy configured for BMR protection. A complete description of BMR backup and recovery procedures is available.

See the Bare Metal Restore System Administrator's Guide:

http://www.veritas.com/docs/DOC5332

This procedure assumes that the Windows operating system and NetBackup are reinstalled to boot the system and perform a restore.

The following are additional assumptions:

  • The NetBackup client was running a supported Microsoft Windows version.

  • The NetBackup client was backed up with a supported version of NetBackup client and server software.

  • The NetBackup master server to which the client sent its backups is operational. You request the restore from this server.

  • The backups included the directory where the operating system and its registry resided.

    If the backups excluded any files that resided in the directory, you may not be able to restore the system identically to the previous configuration.

  • Defective hardware has been replaced.

Before starting, verify that you have the following:

  • Windows system software to reinstall on the NetBackup client that being restored. Reinstall the same type and version of software that was previously used.

  • NetBackup client software to install on the client that being restored.

  • Special drivers or other software that is required to make the hardware operational (for example, a special driver for the disk drive).

  • IP address and host name of the NetBackup client.

  • IP address and host name of the NetBackup master server.

  • The partitioning and the formatting scheme that was used on the system to be restored. You must duplicate that scheme during Windows installation.

To recover a Windows client disk

  1. Install a minimal Windows operating system (perform the Express install).

    During the installation, do the following tasks:

    • Partition the disk as it was before the failure (if partitioning is necessary). Then, reformat each partition as it was before the failure.

    • Install the operating system in the same partition that was used before the failure.

    • Specify the default workgroup. Do not restore to the domain.

    • Follow any hardware manufacturers' instructions that apply.

  2. Reboot the system when the installation is complete.
  3. Configure the NetBackup client system to re-establish network connectivity to the NetBackup master server.

    For example, if your network uses DNS, the configuration on the client must use the same IP address that was used before the failure. Also, it must specify the same name server (or another name server that recognizes both the NetBackup client and master server). On the client, configure DNS in the Network dialog, accessible from the Windows Control Panel.

  4. Install NetBackup client software.

    Ensure that you specify the correct names for the client server and master server.

    • To specify the client name, start the Backup, Archive, and Restore interface on the client and click NetBackup Client Properties on the File menu. Enter the client name on the General tab of the NetBackup Client Properties dialog.

    • To specify the server name, click Specify NetBackup Machines and Policy Type on the File menu.

    Refer to the NetBackup Installation Guide for instructions:

    http://www.veritas.com/docs/DOC5332

  5. Install any NetBackup patches that had previously been installed.
  6. Enable debug logging by creating the following debug log directories on the client:
        install_path\NetBackup\Logs\tar
        install_path\NetBackup\Logs\bpinetd

    NetBackup creates logs in these directories.

  7. Stop and restart the NetBackup Client service.

    This action enables NetBackup to start logging to the bpinetd debug log.

  8. Use the NetBackup Backup, Archive, and Restore interface to restore the system files and user files to the client system.

    For example, if all files are on the C drive, restoring that drive restores the entire system.

    To restore files, you do not need to be the administrator, but you must have restore privileges. For instructions, refer to the online Help or refer to the following:

    See the NetBackup Backup, Archive, and Restore Getting Started Guide:

    http://www.veritas.com/docs/DOC5332

    NetBackup restores the registry when it restores the Windows system files. For example, if the system files are in the C:\Winnt directory, NetBackup restores the registry when it restores that directory and its subordinate subdirectories and files.

  9. Check for ERR or WRN messages in the log files that are in the directories you created in step 6.

    If the logs indicate problems with the restore of Windows system files, resolve those problems before proceeding.

  10. Stop the NetBackup Client service and verify that the bpinetd program is no longer running.
  11. Restart the NetBackup client system.

    When the boot process is complete, the system is restored to the state it was in at the time of the last backup.