Troubleshooting guide

General Test and Troubleshooting Procedures

22 NetBackup Troubleshooting Guide - UNIX

1. Enable appropriate activity and debug logs on the servers (see Chapter 3). If you are

uncertain which logs apply, enable them all until you solve the problem. Delete the

activity log directories when you have resolved the problem.

2. Configure a test class with a user schedule (set the backup window to be open while

you are testing).

◆ Name the media server as the client and a storage unit that is on the media server

(preferably a nonrobotic drive).

◆ Add a volume on the volume database host for the devices in the storage unit

(master server is recommended for the volume database host). Ensure the volume

is in the NetBackup volume pool.

◆ Insert the volume in the drive. If you do not prelabel the volume by using the

bplabel command, NetBackup automatically assigns a previously unused

media ID.

3. Verify that all NetBackup daemons are running on the master server and Media

Manager daemons are running on the media server.

◆ To perform this check on a UNIX system, execute:

/usr/openv/netbackup/bin/bpps -a

◆ To perform this check on a Windows NT/2000 system, use the Services

application in the Windows NT/2000 Control Panel.

4. Perform a user backup and then a restore of a file. Perform these operations from a

client that has been verified to work with the master server.

This test verifies:

◆ NetBackup media server software

◆ Media Manager on the media server can mount the media and use the drive that

you configured

◆ Communications between the master server process bpsched and media server

processes bpcd and bpbrm

◆ Communications between media server process bpbrm and client processes bpcd

and bpbkar

For failures relating to drives or media, ensure that the drive is in an UP state and the

hardware is functioning.

If you suspect a communications problem between the master and media servers,

check the activity logs for the involved processes. If the activity logs don’t help you,

check the following:

◆ UNIX System log