Troubleshooting guide

Status Codes
128 NetBackup Troubleshooting Guide - UNIX
This script lists all volumes in the Media Manager volume configuration, and
augments that list with information on the volumes currently assigned to
NetBackup.
2. If the storage unit and volume pool appear to have media, verify the following:
◆ Volume is not FROZEN or SUSPENDED.
Check for this condition by using the NetBackup Media List report. If the volume
is frozen or suspended, use the bpmedia command to unfreeze or unsuspend it
(if that is desired).
◆ Volume has not expired or exceeded its maximum number of mounts.
◆ Volume Database Host name for the device is correct.
If you change the Volume Database Host name, stop and restart the Media
Manager device daemon, ltid, (if the server is UNIX) or the NetBackup Device
Manager service (if the server is a Windows NT/2000 system).
◆ The correct host is specified for the storage unit in the NetBackup configuration.
The host connection should be the server (master or media) that has drives
connected to it.
◆ The Media Manager volume configuration has media in the correct volume pool
and unassigned or active media is available at the required retention level.
Use the NetBackup Media List report to show the retention levels, volume pools,
and status (active and so on) for all volumes. Use the NetBackup Media Summary
report to check for active volumes at the correct retention levels.
3. In some configurations, the NetBackup bptm process is rejected when requesting
media from the vmd process (NetBackup Volume Manager service on Windows
NT/2000) because that process cannot determine the name of the host that is making
the request.
This can be due to incorrect network configuration involving:
◆ Multiple network interfaces
◆ /etc/resolv.conf on those UNIX systems that use it
◆ Running DNS and not having reverse addressing configured
4. Create bptm and vmd activity log directories and retry the operation.
5. Examine the bptm activity log to verify that bptm is connecting to the correct system.
If an error is logged, examine the vmd log.
On UNIX, the vmd log is: