STATUS CODE: 98, Backups fail with a status 98 "error requesting media (tpreq)".

  • Article ID:100016676
  • Modified Date:
  • Product(s):


STATUS CODE: 98, Backups fail with a status 98 "error requesting media (tpreq)".

Error Message

mount_open_media: Waiting for mount of media id DB0/21 (copy 1) on server


The bptm daemon will look in the /usr/openv/netbackup/db/media/tpreq directory for information on the media ID being used for the backup.  If this directory is inaccessible or the disk is full the backup will fail with a status 98 "error requesting media (tpreq)".  This can also occur when the media ID has an invalid character in the name.  

Other situations may exist that can trigger a Status 98.  This article will deal with situations where a disk full condition or an illegal character in a media ID are causing the problem.

I. Check the available disk space
A disk full condition will cause the media manager to receive an error when requesting a media mount from the device manager.  The df -h command can be used to check for full file systems.  The following example shows a file system with available space.
# df -h
Filesystem         size used avail capacity  Mounted on
/dev/dsk/c0t0d0s0   28G  14G   13G    53%    /

II. Check the media ID being used for illegal characters
The bpmedialist command can be used to show the details for the media ID.  The specific media ID can be found by looking in the Detailed Status tab of the Activity monitor for the job that failed with a status 98.  This will also show if any invalid characters such as "/" are in the filename.

# /usr/openv/netbackup/bin/admincmd/bpmedialist -m "DB0/21"
 id   rl images  allocated    density kbytes restores
         vimages expiration   <------- STATUS ------>
DB0/21  3   0  12/02/2004 11:22 hcart2     0      0

Log Files:
The /usr/openv/netbackup/logs/bptm/log.<date> file on the media server will show which tape cannot be found.  Verify the media ID listed in the log matches the media ID that should be used for the backups.  The following example shows the media ID is being seen as "DB0" which is not valid.  
<2> mount_open_media: Waiting for mount of media id DB0/21 (copy 1) on server nbmedia01.
<16> tapelib: chdir() to /usr/openv/netbackup/db/media/tpreq/DB0 failed, No such file or directory
<16> mount_open_media: error requesting media, errno = No such file or directory
<2> send_brm_msg: ERROR 98
<2> mpx_terminate_exit: EXITING with status 98

If a disk full condition is in place on the media server then:
Remove any unnecessary troubleshooting logs found in the directories within /usr/openv/netbackup/logs, /usr/openv/volmgr/debug or /usr/openv/java/logs.  Also check for any unnecessary files in the file system in which NetBackup is installed.  After clearing up enough disk space it is recommended to restart NetBackup.

If the media ID requested for a backup contains illegal characters such as a "/" then:
The tpreq command will be unable to build the correct symbolic link to the drive due to the slash in the media ID. Remove the tape from the library and delete the media ID from the database.
# /usr/openv/volmgr/bin/vmdelete -m "DB0/21"

One the media ID is removed, then re-add it to the Media server using a valid name.  If a label has already been written to the tape use the bplabel command to re-label the tape with a valid media ID.   Note:  This will erase any data that is on the tape, however there should be no valid images on the tape since backups cannot use a media ID with a "/" in the name.
# cd /usr/openv/netbackup/bin/admincmd
# ./bplabel -m DB0021 -d <density> -n <drive_name>

These are two possible causes for a Status 98.  If neither of these situations apply and a Status 98 still occurs for the backup contact Veritas Technical Services for further assistance in troubleshooting the issue.

Was this content helpful?

Get Support