Step 1

Enable legacy debug logs.

Enable appropriate legacy debug logs on the servers, by entering the following:

UNIX/Linux: /usr/openv/netbackup/logs/mklogdir

Windows: install_path\NetBackup\logs\mklogdir.bat

See the NetBackup Logging Reference Guide.

If you are uncertain which logs apply, enable them all until you solve the problem. Delete the legacy debug log directories when you have resolved the problem.

Step 2

Configure a test policy.

Step 3

Verify the daemons and services.

Verify that all NetBackup daemons or services are running on the master server. Also, verify that all Media and Device Management daemons or services are running on the media server.

Step 4

Backup and restore a file.

Perform a user backup and then a restore of a file from a client that has been verified to work with the master server.

For the failures that relate to drives or media, ensure that the drive is in an UP state and that the hardware functions.

Step 5

Verify communication between the master server and the media servers.

If you suspect a communications problem between the master server and the media servers, check the debug logs for the pertinent processes.

Step 6

Ensure that the hardware runs correctly.

For the failures that relate to drives or media, ensure that the drive is running and that the hardware functions correctly.

See the vendor manuals for information on hardware failures.

If you use a robot in an initial configuration condition, verify that the robotic drive is configured correctly.

On a UNIX server, you can verify only the Media and Device Management part of the configuration. To verify, use the tpreq command to request a media mount. Verify that the mount completes and check the drive on which the media was mounted. Repeat the process until the media is mounted and unmounted on each drive from the host where the problem occurred. Perform these steps from the media server. If this works, the problem is probably with the policy or the storage unit configuration on the media server. When you are done, use tpunmount to unmount the media.

Step 7

Include a robotic device in the test policy.

If you previously configured a non-robotic drive and a robot was attached to your media server, change the test policy to name the robot. Also, add a volume for the robot to the EMM server. Verify that the volume is in the NetBackup volume pool and in the robot.

Start with step 3 to repeat this procedure for a robot. This procedure verifies that NetBackup can find the volume, mount it, and use the robotic drive.

If a failure occurs, check the NetBackup All Log Entries report. Look for any errors that relate to devices or media.

See the NetBackup Administrator's Guide, Volume I.

In an initial configuration, verify that the robotic drive is configured correctly. Do not use a robot number that is already configured on another server.

Try the test utilities.

Do not use the Robotic Test Utilities when backups or restores are active. These utilities prevent the corresponding robotic processes from performing robotic actions, such as loading and unloading media. The result is that it can cause media mount timeouts and prevent other robotic operations like robotic inventory and inject or eject from working.

Step 8

Test other clients or storage units.

When the test policy operates satisfactorily, repeat specific steps as necessary to verify other clients and storage units.

Step 9

Test the remaining policies and schedules.

When all clients and storage units are in operation, test the remaining policies and schedules that use storage units on the media server. If a scheduled backup fails, check the All Log Entries report for errors. Then follow the suggested actions for the appropriate status code.